tags 545086 moreinfo unreproducible thanks On Fri, Sep 04, 2009 at 01:32:51PM -0700, David Fox wrote: > Package: libpam-runtime > Source: pam > Version: 1.1.0-2
> In version 1.1.0, > libpam-modules pre-depends on libpam0g > libpam0g depends on libpam-runtime > libpam-runtime depends on libpam-modules > It is therefore impossible to install any of these No, it's not. - installing a clean system with debootstrap works correctly. - upgrading from lenny to sid works correctly (apt-get install libpam-runtime) - upgrading a sid or karmic system with 1.1.0-1 installed works correctly So where is the evidence that this breaks anything? If we need to break the dependency loop, I think the libpam0g -> libpam-runtime dependency is the one to break; there's no clear rationale for this one in the changelog, so it appears to be there just to ensure libpam-runtime gets installed, but the PAM mini-policy has required applications to depend on libpam-runtime since sarge and login (an Essential package) does this correctly, so we can probably get rid of this other dep if necessary. But I'm not seeing why it's necessary. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
signature.asc
Description: Digital signature
