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
