Your message dated Sat, 29 Oct 2011 00:21:28 -0500
with message-id <[email protected]>
and subject line Re: debian-archive-keyring/experimental: removes all keys
has caused the Debian Bug report #646220,
regarding debian-archive-keyring/experimental: removes all keys
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.)
--
646220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646220
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cupt
Version: 2.2.1
Severity: important
Tags: experimental
Justification: broken, but only when using other package from experimental
After updating debian-archive-keyring to the version in experimental,
"cupt update" produces errors like
| W: gpg:
'//var/lib/cupt/lists/http___debian.uchicago.edu_debian_dists_sid_Release':
public key 'AED4B06F473041FA' not found
The changelog says:
* Put debian-archive-keyring.gpg into trusted.gpg.d.
* Remove old keys from trusted.gpg upon upgrade.
so I guess this is a missing feature in cupt.
(Philipp: by the way, debian-archive-keyring's postinst does not seem
to be idempotent in the presence of intermittent errors, as when the
impatient admin presses ^C and then runs "dpkg --configure -a" to
resume. Changing "ln -s" to "ln -sf" would partially fix it; please
let me know if you'd like a report for this.)
--- End Message ---
--- Begin Message ---
Version: 2011.10.23
Philipp Kern wrote:
> can you delete everything[1] in /etc/apt/trusted.gpg.d (downgrades are not
> supported) and re-try with 2011.10.23, please?
Sorry for the slow response. I tried an upgrade in a kfreebsd-amd64
experimental VM:
upgrade debian-archive-keyring 2010.08.28 2011.10.23
"apt-get update" works fine this time --- thanks!
Unfortunately, this still breaks "cupt update", but that's not your
problem. :)
--- End Message ---
