Bug#794736: libvigraimpex: library transition is needed when GCC 5 is the default

[Simon McVittie]

On Thu, 13 Aug 2015 at 13:47:04 +0200, Daniel Stender wrote:
> We have some other serious issues open for Vigra (with the Lenna image set [2] and test suite
> problems in Mips), so I suggest we do it that way: I'm going to prepare a "v5" 1.9.0+dfsg-11
> for unstable in the next days and check the reverse deps.

Did this ever happen? I believe the current policy is that maintainers
(and NMUers) should upload transitioning packages to unstable as soon as
each library build-dependency that needs a transition has started it.
If necessary, add versioned build-dependencies, to make sure that your
package will go into Dep-Wait state on the buildds until their
build-dependencies are at the transitioned version on the relevant
architecture.

The bug about the Lena sample/test images does not need to block this:
while it is a bug that should be fixed, it isn't a regression (the version
currently in testing is no better than the one in unstable in this respect),
and unlike the libstdc++ transition it can't block work elsewhere in Debian.
If the offending files are also present in stable/testing (which I suspect
they are), please mark the bug as "found" in those versions so that the BTS
knows what's going on.

1.10.0 in experimental seems to have built successfully on mips, hopefully
that's a good sign for that bit.

You shouldn't need to go through the NEW queue for a second time when
1.9.0+dfsg-11 is uploaded, because the new binary package name has
already been approved.

    S