Bug#804246: transition: gsl
On 20-11-15 12:57, Dirk Eddelbuettel wrote:
>
> On 20 November 2015 at 11:45, Sebastiaan Couwenberg wrote:
> | On 09-11-15 18:21, Emilio Pozuelo Monfort wrote:
> | > On 06/11/15 15:06, Bas Couwenberg wrote:
> | >> Package: release.debian.org
> | >> Severity: normal
> | >> User: release.debian.org@packages.debian.org
> | >> Usertags: transition
> | >> Forwarded: https://release.debian.org/transitions/html/auto-gsl.html
> | >>
> | >> An uncoordinated transition to GSL 2.0 has started in unstable.
> | >>
> | >> It caused nco to FTBFS and I suspect other reverse dependencies will
> | >> likewise need to be updated to build successfully with gsl (2.0+dfsg-1).
> | >>
> | >> The automatically created transition tracker is already available.
> | >>
> | >> The maintainer is CC'ed.
> | >
> | > Any idea how many packages fail to build against the new version? Not speaking
> | > of how many need to change the build dependencies from libgsl0-dev (>= x.y) to
> | > libgsl-dev, but of build failures in all the rdeps due to API changes.
> |
> | I haven't tested any gsl rdeps other than those maintained by the Debian
> | GIS team, and those rebuilds are already available in unstable.
> |
> | Can we binNMU the remaining rdeps and see what breaks?
>
> Sounds good to me.
>
> | Or should Dirk or someone else first rebuild the rdeps themselves before
> | this transition can move on?
>
> Do you happen to have a list of what has / has not rebuilt?
All packages still marked as bad in the transition tracker still need to
be rebuilt with GSL 2:
https://release.debian.org/transitions/html/gsl.html
Ideally these rebuilds get done when the new package is in experimental
(before the transition starts with the upload to unstable), once you
know that which reverse dependencies still build successfully with the
new version you request a transition slot from the Release Team by
filing a transition bugreport like this one. When the Release Team is
ready to coordinate the transition from their end, they'll give the
go-ahead to start the transition with the upload of the new package to
unstable. This workflow is documented in the wiki:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions
You can either manually rebuild the reverse dependencies using a local
repository for the rebuilt packages to test all the dependency levels,
or try the new ratt package that automates this process (I've not tried
ratt myself yet, and still prepare transitions with manual rebuilds).
https://tracker.debian.org/pkg/ratt
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Reply to: