severity 476532 serious thanks Hello, On Thu, 17 Apr 2008 18:52:06 +0200, Luk Claes <luk@debian.org> wrote:
Package: debian-archive-keyringIt's apt that is failing not debian-archive-keyring... and debian-archive-keyring does recommend gnupg ...
That's not entirely correct: see O: dpkg: error processing debian-archive-keyring (--install): O: subprocess post-installation script returned error exit status 127 BTW recommends are totally irrelevant when we talk about configurability.
debian-archive-keyring is now unconfigurable if gnupg is not installed.You mean apt-key from the apt package... so I'm reassigning the bug.
The situation is: apt-key needs gpg to work, apt-key needs d-a-k, apt calls apt-key in postinst, d-a-k calls apt-key in postins.
The only solutions I see are:1) apt Dep: d-a-k, d-a-k Dep: gnupg (this was the situation before you dropped the dependency on gnupg)
2) apt Dep: d-a-k, apt Pre-Dep: gnupg (this is really awkward)3) Drop one of the premises. For eg. the first one (the others are undesirable to drop, IMHO), this would need apt-key suceed when gpg is not installed (see patch) and add a postinst file to gnupg (basically the same script as d-a-k has) st. the last configured package of { d-a-k, gnupg, apt } would call apt-key update and gpg. Also, it would need to ensure only (fixed apt, fixed gnupg) are installed together.
4) Triggers ??? (I don't know much about this)I changed the severity back to serious, as this is a policy violation and causes bootstrap failures. However, I'm not really sure which package this bug belongs to. It's sure d-a-k introduced this bug by dropping the dependency, but more packages can fix that. But whichever solution will be taken, d-a-k really should have thought this through before dropping the dependency.
Regards
Jiri PalecekAttachment:
apt-key.diff
Description: Binary data