On Fri, Sep 11, 2015 at 08:49:55PM +0100, Simon McVittie wrote: > Looking at the build-dependencies of wreport, the only C++ library > seems to be libwibble, which is static (and was already rebuilt). > So this sub-transition is ready to start. > > The package might be NMU'd if there is no maintainer response. The > release team have declared a 2 day NMU delay[2] for packages involved > in the libstdc++ transition, in order to get unstable back to a usable > state in a finite time.
Hello, I actually am pretty far in a big refactoring of the library, and all its reverse dependencies, that does not depend on wibble: https://github.com/ARPA-SIMC/wreport/tree/devel I am waiting for ARPA Emilia Romagna (the institution for which I am maintaining the code) to deploy the code into production and have it there for a week or two without big issues, before uploading the new toolchain to Debian. It could be anytime from two weeks to two months, but definitely well in time for stretch. Would it be possible to just remove wreport and dballe from testing, so that no transition will be blocked, and have them move in again when I upload the new ones? Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
