Bug#791112: #791112: libcrypto++: library transition may be needed when GCC 5 is the default
On Mon, 2015-08-17 at 11:16 +0200, Christian Hofstaedtler wrote: Hi, I've noticed a new libcrypto++ has entered sid, but the transition tracker[1] doesn't seem to agree on the library names, or something (it still shows libcrypto++ as bad). What's going on there? [1] https://release.debian.org/transitions/html/auto-libcrypto++.html libcrypto9-dbg depends on libcrypto9. Until the transition's at a point where those packages can be decrufted from unstable, the tracker will see a package being built from src:libcrypto++ that depends on libcrypto9, and flag it as bad. Regards, Adam
Bug#791112: #791112: libcrypto++: library transition may be needed when GCC 5 is the default
Hi, I've noticed a new libcrypto++ has entered sid, but the transition tracker[1] doesn't seem to agree on the library names, or something (it still shows libcrypto++ as bad). What's going on there? [1] https://release.debian.org/transitions/html/auto-libcrypto++.html Thanks, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpWLCzGJGNYB.pgp Description: PGP signature
