Bug#924814: grub-efi-amd64-signed: FTBFS: build-dependency not installable: grub-efi-amd64-bin (= 2.02+dfsg1-11)

[Colin Watson]

Control: tag -1 - sid

On Sun, Mar 17, 2019 at 07:03:42PM +0100, Lucas Nussbaum wrote:
> Source: grub-efi-amd64-signed
> Version: 1+2.02+dfsg1+11
> Severity: serious
> Tags: buster sid
> User: debian-qa at lists.debian.org
> Usertags: qa-ftbfs-20190315 qa-ftbfs
> Justification: FTBFS in buster on amd64
> 
> Hi,
> 
> During a rebuild of all packages in buster (in a buster chroot, not a
> sid chroot), your package failed to build on amd64.
[...]
> > The following packages have unmet dependencies:
> >  sbuild-build-depends-grub-efi-amd64-signed-dummy : Depends: grub-efi-amd64-bin (= 2.02+dfsg1-11) but it is not going to be installed

This is because grub2 2.02+dfsg1-12 migrated to testing without the
corresponding grub-efi-{amd64,arm64,ia32}-signed packages, thus
rendering the latter unbuildable and violating their Built-Using fields.
The version in unstable is fine when built against unstable;
grub-efi-amd64-signed 1+2.02+dfsg1+12 would have been fine if it had
migrated to testing before being superseded by 1+2.02+dfsg1+13; and once
the next grub2 + grub-efi-*-signed set migrates to testing then it will
be fine again there.

Release team: is there some way to make sure that this mismatched
migration doesn't happen in future?  It seems that the promotion
machinery ought to have prevented this, particularly due to the way it
caused Built-Using to be violated.

-- 
Colin Watson                                       [cjwatson at debian.org]