You are right that the way you say (upload to unstable / ask binNMUs) would be the fast track to success. But within the Crosswire packaging team, I was asked to do this one through an auto transition. https://wiki.debian.org/Teams/ReleaseTeam/Transitions And that route is a bit longer. But it plays by the book. And I already botched my DD application by not following the rules. So while I agree with you about the faster way to do this, I can't afford to not follow the book this time :)
On Tue, 6 Nov 2018 at 15:37 Jeremy Bicha <[email protected]> wrote: > On Tue, Nov 6, 2018 at 9:22 AM Teus Benschop <[email protected]> > wrote: > > Yes, this bug seems obsolete because once libsword is fixed it's a > matter of doing the uploads and rebuilds as you say. > > But libsword is going into auto transition due to a change in the soname. > > And I have now experience with how long such an automatic library > transition is going to take. > > In the mean time Xiphos is not yet running on the testing distribution > due to linking to an older libsword version. > > So I thought it more expedient and prudent to ensure Xiphos is right in > testing and works there. > > So yes, it's kind of two independent tracks that could lead to the same > solution. > > A slower one and a fast one. > > It doesn't have to be very slow. Just upload sword to unstable now and > then ask the Debian Release team to do the binNMUs. > > If you use the default urgency=medium, it might only take 5 days to > transition to testing, assuming that xiphos will build on ppc64el now. > > Thanks, > Jeremy Bicha > -- Teus Benschop [email protected] 0318 712046
