Bug#754992: transition: libtrio 1.16
Hi Bálint!
On 16/07/14 19:15, Bálint Réczey wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
>
> Dear Release Team,
>
> I'm ready to upload new 1.16 upstream release of libtrio to unstable which fixes
> build failures on some architectures (#747012).
> The following source packages need to be rebuilt:
>
> ghostscript
> mednafen
Why ghostscript? It doesn't depend on libtrio AFAICS.
Have you tested that those build fine against the new library?
> In terms of 'ben' lingo, the transition has the following parameters:
>
> Affected: .build-depends ~ /libtrio-dev/
> Good: .depends ~ /libtrio2/
> Bad: .depends ~ /libtrio1/
That's generated automatically now when you upload to sid or experimental.
Uploading to experimental has the benefits that you don't have to ask us, you
get a tracker and you go through NEW and don't have to go through it again when
the transition is ACKed.
> Please schedule binNMUs for the above mentioned packages on all
> architectures and tell me when I can upload 1.16 to unstable.
Things work the other way :) Once the new library is in unstable, we schedule
the binNMUs so that the reverse dependencies get built against the new SONAME
and the old library package can be removed (decrufted). I see no conflicts at
the moment so please go ahead and upload to sid.
Regards,
Emilio
Reply to: