On Sun, 2012-01-08 at 13:29 +0100, Philipp Kern wrote: > On Sun, Jan 08, 2012 at 12:20:34PM +0000, Roger Leigh wrote: > > libpam-mount depends on Linux-only libraries (libpam-mount), and > > additionally dropped support for BSD mount upstream, so should > > no longer be considered buildable or usable on kfreebsd for the > > time being at least. > > It still needs its obsolete binaries removed.
Indeed. Someone needs to file an appropriate removal bug against ftp.d.o. > > libhx also appears to be blocking libpam-mount, but it's claiming > > libhx27 is out of date (but it's no longer present, replaced by > > libhx28). It *is* still present, as checking packages files or something like the below will show: $ dak ls libhx27 libhx27 | 3.11-1 | testing | amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc libhx27 | 3.11-1 | unstable | amd64, armel, armhf, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc > Same here. Can't check at the moment if there are still rdeps. Checking reverse dependencies... # Broken Depends: libpam-mount: libpam-mount [kfreebsd-amd64 kfreebsd-i386] So fixing the first issue should allow libhx27 to be auto-crufted; it's already on the cruft report. > britney is usually correct about the reasons. Indeed. That doesn't stop people arguing that's she wrong on a regularish basis, though. :-/ Regards, Adam -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
