Package: dpkg-dev Version: 1.18.4 Severity: normal Hello,
To properly express bootstrap stages, it is convenient to introduce packages which do not usually exist in the archive, to express that they provide only part of the expected support. The problem is that these packages end up in the Binary field of the .changes file of unstaged builds too, and thus trigger NEW processing, while we won't actually ever upload such binary package. A solution would be that dpkg-genchanges is added a -P parameter, and by default (unstaged) not include staged-only binary packages in Binary. For instance (this is a hurd-only example, but such examples will surely arise for linux packages too), the hurd package normally builds hurd-dev which contains all the usual hurd system libraries. The stage1 profile can only ship the headers, and not the libraries themselves, so we introduced a hurd-headers-dev binary package, built by stage1, which contains only headers, so that further bootstrap steps can depend on hurd-headers-dev instead of hurd-dev to get them (hurd-dev also Provides hurd-headers-dev). We then had to pass NEW due to this addition, because the .changes file had it in the Binary: field. And then we had to pass NEW again in the latest upload, for the same reason: apparently between the two uploads some cleaning process in ftp-master had dropped the knowledge of the package, probably because it's not actually uploaded in the archive. Perhaps ftp-master should be more cautious about this, but I'd say dpkg-genchanges should just not even mention this package, what do you think? Samuel -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dpkg-dev depends on: ii base-files 9.6 ii binutils 2.26-5 ii bzip2 1.0.6-8 ii libdpkg-perl 1.18.4 ii make 4.1-6 ii patch 2.7.5-1 ii xz-utils 5.1.1alpha+20120614-2.1 Versions of packages dpkg-dev recommends: ii build-essential 12.2 ii clang-3.5 [c-compiler] 1:3.5.2-3 ii clang-3.6 [c-compiler] 1:3.6.2-3 ii fakeroot 1.20.2-1 ii gcc [c-compiler] 4:5.3.1-1 ii gcc-4.8 [c-compiler] 4.8.5-4 ii gcc-4.9 [c-compiler] 4.9.3-12 ii gcc-5 [c-compiler] 5.3.1-11 ii gcc-6 [c-compiler] 6-20160109-1 ii gnupg 1.4.20-4 ii gnupg2 2.1.11-6 ii gpgv 1.4.20-4 ii libalgorithm-merge-perl 0.08-3 Versions of packages dpkg-dev suggests: ii debian-keyring 2016.01.20 -- no debconf information -- Samuel `When you say "I wrote a program that crashed Windows", people just stare at you blankly and say "Hey, I got those with the system, *for free*".' (By Linus Torvalds)
