Bug#791112: #791112: libcrypto++: library transition may be needed when GCC 5 is the default
- To: 791112@bugs.debian.org
- Subject: Bug#791112: #791112: libcrypto++: library transition may be needed when GCC 5 is the default
- From: Andreas Beckmann <anbe@debian.org>
- Date: Sun, 13 Sep 2015 19:05:13 +0200
- Message-id: <[🔎] 55F5ACC9.4010505@debian.org>
- Reply-to: Andreas Beckmann <anbe@debian.org>, 791112@bugs.debian.org
- In-reply-to: <1439804122.1859.4.camel@adam-barratt.org.uk>
- References: <20150817091630.GA1009@sx.dc15.debconf.org> <1439804122.1859.4.camel@adam-barratt.org.uk> <1439804122.1859.4.camel@adam-barratt.org.uk>
I took a look at the libcrypto++9v5 transition and think that binNMUs
can now be scheduled for its rdepends:
* amule (only in sid due to a rc bug: needs wx 2.8 -> 3.0 migration,
verified that it still builds in sid without problems)
* armory (only in sid due to a do-not-migrate-to-testing rc bug)
* murasaki (needs to be rebuilt against boost 1.58, too)
* pycryptopp
* synergy
tegrarcm is in non-free and not autobuilt, so I uploaded a manual binNMU
to delayed/2 (only for amd64, the only architecture ever uploaded)
Andreas
Reply to: