Boyuan Yang wrote...

> Package ngircd depends on binary package libident, but this package has
> been renamed to libident0 due to time64 transition. Please fix the binary
> dependency relationship accordingly. You may need to rebuild the package.

Well, that is broken anyway at the moment:

(...)
|      dh_shlibdeps -a
|   dpkg-shlibdeps: warning: diversions involved - output may be incorrect
|    diversion by libpam0t64 from: /lib/x86_64-linux-gnu/libpam.so.0
|   dpkg-shlibdeps: warning: diversions involved - output may be incorrect
|    diversion by libpam0t64 to: /lib/x86_64-linux-gnu/libpam.so.0.usr-is-merged
|   dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libident.so.0 (used by debian/ngircd/usr/sbin/ngircd)
|   Hint: check if the library actually comes from a package.
|   dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/ngircd.substvars 
debian/ngircd/usr/sbin/ngircd returned exit code 2
|   dh_shlibdeps: error: Aborting due to earlier error
|   make: *** [debian/rules:8: binary] Error 25
|   dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2

So I guess the best thing to do right now is to wait until the dust around
this t64 story has settled.

    Christoph

Attachment: signature.asc
Description: PGP signature

Reply via email to