Your message dated Sat, 15 Dec 2018 15:04:14 +0000
with message-id <[email protected]>
and subject line Re: Bug#916533: gnupg2 missing
has caused the Debian Bug report #916533,
regarding gnupg2 missing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
916533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916533
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gnupg2
Version: 2.2.12-1
Severity: serious
Hi,
The gnupg2 binary package is no longer available. I assume that this
is not intentional, as nothing has been announced in the ChangeLog.
Various packages depend on it, making the upgrade of gpg impossible.
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On Sat, 2018-12-15 at 15:50 +0100, Vincent Lefevre wrote:
> The gnupg2 binary package is no longer available. I assume that this
> is not intentional, as nothing has been announced in the ChangeLog.
> Various packages depend on it, making the upgrade of gpg impossible.
It is still available, it's just not currently listed in the Packages
file for unstable (no, those two are not exactly equivalent):
gnupg2 | 2.2.12-1 | unstable | source, all
What appears to have happened is that the arch:all buildd upload was
built a few hours after the arch:any builds were available, causing dak
to temporarily exclude it from the Packages files as it was outdated.
Unfortunately, a dinstall occurred between the two sets of uploads.
The arch:all upload was accepted before the 13:52 dinstall, so
everything should sort itself out with the next mirror push.
Regards,
Adam
--- End Message ---
