Hi, Adam Heath wrote: > this is a bug in apt. dpkg correctly handles this case(it breaks the dep loop > randomly, which means postinsts of the affected packages need to be aware of > the issue. > > The apt developer has refused to fix apt to work around this non-problem in > the past, I suggest you take it up with him.
Well, it mutates into a problem if the new pam migrates to testing
in some days[1] in which case sarge would have that version and
therefore upgrades from woody to sarge would become problematic with
apt (yes, you could you it with deselect or do the install of libpam*
manually, but do not tell that newbies only trying that with
apt because they read it....)
Grüße/Regards,
René
[1] which is blocked by xdelta2 currently (besides being 6d old today)
but they are thoughts to remove xdelta2 in testing so that db3 and
therfore pam could go in (see #178525)
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
pgpauW4J8i4gD.pgp
Description: PGP signature
