Re: Some upcoming dpkg changes, test and feedback welcome
* Raphael Hertzog [110921 22:52]: >>> [...] DEB_DISTRIBUTION [...] > But this is all wishful thinking at this point given that I have no use > case where some analysis of the distributions returned needs to be > portable across several derivatives and Debian itself. Sorry for again joining in late in the distribution, but what is the use case of this field exactly? Currently I can only see possible abuses but no proper uses for it, so unless there is something I miss, I'd rather request that variable to be removed, as it can only harm. Bernhard R. Link -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110922091432.ga23...@server.brlink.eu
Re: Some upcoming dpkg changes, test and feedback welcome
On Thu, 22 Sep 2011, Bernhard R. Link wrote: > Sorry for again joining in late in the distribution, but what is the use > case of this field exactly? ifeq($(DEB_DISTRIBUTION),unstable) $(error GNOME 3 packages should be uploaded to experimental) endif Or rather: ifneq(,$(filter unstable,$(DEB_DISTRIBUTION))) $(error GNOME 3 packages should be uploaded to experimental) endif That's the main use case I referred to. We can imagine more use cases in the context of other distributions than Debian. Ubuntu for example could want to adjust the behaviour when targetting a source packages for an older release (since they always use the codename in that field). > Currently I can only see possible abuses but no proper uses for it, so > unless there is something I miss, I'd rather request that variable to > be removed, as it can only harm. What kind of abuses do you see? Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110922115925.ga4...@rivendell.home.ouaza.com
Re: Some upcoming dpkg changes, test and feedback welcome
* Raphael Hertzog [110922 13:59]: > We can imagine more use cases in the context of other distributions than > Debian. Ubuntu for example could want to adjust the behaviour when > targetting a source packages for an older release (since they always use > the codename in that field). > > > Currently I can only see possible abuses but no proper uses for it, so > > unless there is something I miss, I'd rather request that variable to > > be removed, as it can only harm. > > What kind of abuses do you see? Anything that does not error out but changes behaviour. In your second example above for example, you get a package that would silently change behaviour if doing a locally modified version. Or imagine someone having the 'bright idea' to have something that behaves differently if that field is 'stable-proposed-updates', so that a following upload (once the package reached testing) of that package targeting a point release would not show differences but the changelog. Then if that package gets in there and someone later wants to do a security upload, the source package from stable will suddenly behave differently, because not the distribution field is different. Bernhard R. Link -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110922150745.ga26...@server.brlink.eu
Re: Proposal for a "Bits from dpkg developers"
On Thu, 2011-09-08 at 15:23:10 +0200, Raphael Hertzog wrote: > Given the number of disruptive changes, it's important to accompany > the upload with a d-d-a mail. I have thus prepared a draft here: > http://titanpad.com/wHeHZd9yrs Ok! Release tagged, pushed and uploaded. I reworded some things, and added the new stuff since 1.15.7 that I mentioned on my other mail. Hope to not have missed anything else important/user visible. Please take a look, and feel free to send. regards, guillem -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110923050329.ga18...@gaara.hadrons.org
Preparing stable release for squeeze (dpkg 1.15.8.12)
Hi! There's some changes in the squeeze branch, and there's a new point release approaching, but usually a package including the fixes is required to have been in sid for a while, so we might be too late already. I'll be preparing the release and a mail later today to request SRM approval anyway. If there's anything else you want to see included please say so soon, otherwise it will have to wait for the next version. thanks, guillem -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110923051147.gb18...@gaara.hadrons.org
Accepted dpkg 1.16.1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 23 Sep 2011 06:00:11 +0200 Source: dpkg Binary: libdpkg-dev dpkg dpkg-dev libdpkg-perl dselect Architecture: source amd64 all Version: 1.16.1 Distribution: unstable Urgency: low Maintainer: Dpkg Developers Changed-By: Guillem Jover Description: dpkg - Debian package management system dpkg-dev - Debian package development tools dselect- Debian package management front-end libdpkg-dev - Debian package management static library libdpkg-perl - Dpkg perl modules Closes: 147583 231089 245322 293280 308082 454694 489771 525160 526774 552123 560070 560251 603435 604241 606839 608260 610940 615899 616609 619131 620312 620490 620520 621066 622094 626684 627462 628055 628726 629582 630533 630996 631435 631439 631494 631547 631757 631808 632168 632937 633539 633627 634510 634961 635467 635683 636700 637096 637564 638291 639229 639997 640198 640298 641834 Changes: dpkg (1.16.1) unstable; urgency=low . [ Raphaël Hertzog ] * Dpkg::Deps: Implement new "reset" method and bump module version to 1.01 due to this. * Improved description of --search in dpkg-query(1). Closes: #621066 Thanks to Lars Buitinck for the patch. * Let update-alternatives fsync() its administrative files before moving them in place to avoid empty files with some filesystems. LP: #344019 * Tighten the regexp used by dpkg-source to ignore the .pc directory of quilt. Thanks to Mike Hommey for noticing the problem. * Change behaviour of dpkg-source's --extend-diff-ignore to also extend the current diff-ignore if it has already been set. * Fix dependency checking code to consider a dependency on a virtual package provided by a package in triggers-pending status as satisfied. * Do not fail when encountering a pre-dependency in triggers-awaited state, instead process the awaited triggers. Closes: #526774 * "any" no longer hides "all" in the Architecture field of a .dsc. * Fix dpkg --remove to really remove the triggers from the various internal files in /var/lib/dpkg/info/triggers/. Closes: #525160 * Avoid a perl warning in dpkg-gensymbols when no symbols file has been generated (because it would have been empty). Closes: #626684 * Re-enable the Package-List field but drop the Architecture column since we have no clear use case yet. It can always be added later on. Also drop the source line since it duplicates other fields. Closes: #619131 * Add the extraction part of Dpkg::Source::Package to the supported API. Useful to extract source packages without having to depend on dpkg-source (and hence dpkg-dev). * Add the Dpkg::Vendor module to the supported API. Useful for lintian when dpkg-dev is absent. * Check presence of required parameters in dpkg-vendor. Closes: #628726 Thanks to Niels Thykier for the patch. * Avoid a Perl warning in dpkg-buildflags when HOME is not set. Closes: #635467 * dpkg-source can now also use debian/source/local-patch-header (that is not included in the generated source package) instead of debian/source/patch-header. Closes: #629582 * Changed dpkg-source --after-build to automatically unapply patches that it has applied during --before-build. * Fix two possible causes for the assertion failure "pigp->trigpend_head". LP: #798793, #424358 Closes: #560251 * Use "special" instead of "particular" to qualify the "3.0 (custom)" format in dpkg-source(1). Closes: #631435 * Add some supplementary checks to ensure debian/control has the required fields. Closes: #631439 * dpkg-gensymbols(1): document syntax of comments. Closes: #630996 * Allow empty lines in symbols files to better delimit multiple libraries. Thanks to Cyril Brulebois for the patch. * dpkg: if "prerm upgrade" fails when downgrading, do not try to run "prerm failed-upgrade" with the prerm of the oldest prerm, it can't work around a bug of a newer prerm anyway. * dpkg: support new "interest-noawait" and "activate-noawait" trigger directives. * dpkg-buildflags(1): make it clear that DEB_*_(SET|APPEND) environment variables are meant for users and should not be used by packages. * update-alternatives: do not allow to reuse a slave link in another slave alternative. Closes: #631547 * Improve dpkg-source's logic to identify ignored files. Closes: #632168 * Fix a small typo in dpkg-source(1). Closes: #632937 * Reword the description of dpkg-source --before-build and --after-build to be clearer. Closes: #608260 * dpkg-buildpackage no longer exports the compiler flags. Closes: #560070 Packages must directly call dpkg-buildflags to retrieve them. * dpkg-buildflags supports a prepend command to modify the build flags. Particularly useful for package maintainers who don't want their supplementary flags to take precedence over user
Processing of dpkg_1.16.1_amd64.changes
dpkg_1.16.1_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: dpkg_1.16.1.dsc dpkg_1.16.1.tar.bz2 libdpkg-dev_1.16.1_amd64.deb dpkg_1.16.1_amd64.deb dselect_1.16.1_amd64.deb dpkg-dev_1.16.1_all.deb libdpkg-perl_1.16.1_all.deb Greetings, Your Debian queue daemon (running on host ravel.debian.org) -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1r6xtr-0007rn...@ravel.debian.org
Processing of dpkg_1.16.1_amd64.changes
dpkg_1.16.1_amd64.changes uploaded successfully to localhost along with the files: dpkg_1.16.1.dsc dpkg_1.16.1.tar.bz2 libdpkg-dev_1.16.1_amd64.deb dpkg_1.16.1_amd64.deb dselect_1.16.1_amd64.deb dpkg-dev_1.16.1_all.deb libdpkg-perl_1.16.1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1r6xw2-0001yz...@franck.debian.org
Re: Proposal for a "Bits from dpkg developers"
Guillem Jover wrote: > Ok! Release tagged, pushed and uploaded. > > I reworded some things, and added the new stuff since 1.15.7 that I > mentioned on my other mail. Hope to not have missed anything else > important/user visible. Please take a look, and feel free to send. Re the new triggers: | If the trigger processing is not critical for the activating package | to actually work, then you should consider using these new | directives. If you do so, you will have to add a | “Pre-Depends: dpkg (>= 1.16.1)” to ensure the new dpkg is | installed even before your package is unpacked. See deb-triggers(5) | for details. Has it been discussed on debian-devel whether such a Pre-Depends is worth it, and if so for which packages? I personally think that it really would be worth it in this case for any package of priority "standard" or lower (and maybe even packages of priority "important"), but if we're making this announcement without having had that discussion, then the email should say something like "Before doing so, please consult debian-devel so the impact on upgrades can be considered". Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110923052548.GB2873@elie
dpkg_1.16.1_amd64.changes ACCEPTED into unstable
Accepted: dpkg-dev_1.16.1_all.deb to main/d/dpkg/dpkg-dev_1.16.1_all.deb dpkg_1.16.1.dsc to main/d/dpkg/dpkg_1.16.1.dsc dpkg_1.16.1.tar.bz2 to main/d/dpkg/dpkg_1.16.1.tar.bz2 dpkg_1.16.1_amd64.deb to main/d/dpkg/dpkg_1.16.1_amd64.deb dselect_1.16.1_amd64.deb to main/d/dpkg/dselect_1.16.1_amd64.deb libdpkg-dev_1.16.1_amd64.deb to main/d/dpkg/libdpkg-dev_1.16.1_amd64.deb libdpkg-perl_1.16.1_all.deb to main/d/dpkg/libdpkg-perl_1.16.1_all.deb Override entries for your package: dpkg-dev_1.16.1_all.deb - optional utils dpkg_1.16.1.dsc - source admin dpkg_1.16.1_amd64.deb - required admin dselect_1.16.1_amd64.deb - optional admin libdpkg-dev_1.16.1_amd64.deb - optional libdevel libdpkg-perl_1.16.1_all.deb - optional perl Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 147583 231089 245322 293280 308082 454694 489771 525160 526774 552123 560070 560251 603435 604241 606839 608260 610940 615899 616609 619131 620312 620490 620520 621066 622094 626684 627462 628055 628726 629582 630533 630996 631435 631439 631494 631547 631757 631808 632168 632937 633539 633627 634510 634961 635467 635683 636700 637096 637564 638291 639229 639997 640198 640298 641834 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1r6y8w-0002zk...@franck.debian.org
Re: Proposal for a "Bits from dpkg developers"
Hi, On Fri, 23 Sep 2011, Guillem Jover wrote: > I reworded some things, and added the new stuff since 1.15.7 that I > mentioned on my other mail. Hope to not have missed anything else > important/user visible. Please take a look, and feel free to send. Thanks! It looks great, I made a few typo fixes, added a sentence wrt Jonathan's concern and sent it. On Fri, 23 Sep 2011, Jonathan Nieder wrote: > | If the trigger processing is not critical for the activating package > | to actually work, then you should consider using these new > | directives. If you do so, you will have to add a > | “Pre-Depends: dpkg (>= 1.16.1)” to ensure the new dpkg is > | installed even before your package is unpacked. See deb-triggers(5) > | for details. > > Has it been discussed on debian-devel whether such a Pre-Depends > is worth it, and if so for which packages? No, I expect each package maintainer to discuss it if they feel the need. I put a sentence for this in the final version I just sent. > I personally think that it really would be worth it in this case for > any package of priority "standard" or lower (and maybe even packages > of priority "important"). More than the priority of the package, it's the impact of the trigger that must be considered. IMO it's totally worth it for a package like man-db whose triggers is almost always activated. bash-completion is not priority standard but was intending to have a trigger on /bin /usr/bin and so on. This one should definitely need to use the new form too! Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110923062547.gb11...@rivendell.home.ouaza.com
Re: Proposal for a "Bits from dpkg developers"
Raphael Hertzog wrote: > It looks great, I made a few typo fixes, added a sentence wrt > Jonathan's concern and sent it. Thanks! (Just for the record, it was not really the maintainers that are unsure that I was worried about. ;-) And such a Pre-Depends is basically always safe, as long as the dpkg maintainers know about it and can avoid a Depends/Pre-Depends or Breaks/Pre-Depends cycle.) I hadn't realized it had been so long since the last release. This upload looks like a good one. -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110923063906.GA29036@elie
