Package: ftp.debian.org
Severity: important
I just noticed that my piuparts instance was testing the "removal" of
many libreoffice-* arch:all packages on testing->sid upgrades, which
seemed weird ... but they are actually gone from the sid/amd64 Packages
file right now:
in a sid/amd64 chroot: (has newer arch:any binary packages)
# apt-cache policy libreoffice libreoffice-l10n-bn
libreoffice:
Installed: (none)
Candidate: 1:5.0.3~rc2-1
Version table:
1:5.0.3~rc2-1 0
500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
libreoffice-l10n-bn:
Installed: (none)
Candidate: (none)
Version table:
in a sid/armhf chroot: (has older arch:any binary packages)
# apt-cache policy libreoffice libreoffice-l10n-bn
libreoffice:
Installed: (none)
Candidate: 1:5.0.3~rc1-2
Version table:
1:5.0.3~rc1-2 0
500 http://ftp.de.debian.org/debian/ unstable/main armhf Packages
libreoffice-l10n-bn:
Installed: (none)
Candidate: 1:5.0.3~rc1-2
Version table:
1:5.0.3~rc1-2 0
500 http://ftp.de.debian.org/debian/ unstable/main armhf Packages
This is caused by source-only uploads which break the assumption that
the arch:all packages "appear" at the same time as a new source package,
and therefore the conclusion 'if a new source package "appears"
without arch:all packages these obviously have been dropped' no longer
holds.
* source-only upload of a package building arch:all packages
* the arch:any packages are built and accepted (on some architectures at
least) before the arch:all packages got built
* if there are arch:$ARCH packages from a newer source package this will
cause the arch:all packages of the old version to be omitted from the
Packages file even if there is no replacement, yet. This does not
happen the other way around.
Maybe arch:any builds should not be accepted (but put on hold) before
the arch:all packages become available by being
* an empty list
* included in the maintainer upload (source+all+binary or source+all)
* built by the buildd (source-only uploads)
Andreas
