On Sat, Jan 27, 2018 at 12:37:46AM +0100, Emilio Pozuelo Monfort wrote: > Control: forwarded -1 https://release.debian.org/transitions/html/ruby2.5.html > > On 26/01/18 20:36, Antonio Terceiro wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian.org@packages.debian.org > > Usertags: transition > > > > Hi, > > > > I would like to start the transition to ruby2.5 in unstable. General > > information about Ruby transitions can be found in: > > https://wiki.debian.org/Teams/Ruby/InterpreterTransitions > > > > ruby2.5 has been in testing for a while. > > > > Building against ruby2.5 has been enabled in experimental, and we > > already did a test rebuild against it, with pretty good results: > > https://hackmd.io/EYBghgHA7AjFDMBaCZgE5EBYYCYAmiaEAxhjgKzFQCmAZtGHtTkA > > > > So I would like to enable building against ruby2.5 in unstable, and to > > effectively start the transition. Soon after we have a transition page, > > I will have a first round of binNMUs to request. > > You mention 315 build failures in your report, but I only see 46 bugs > in [1] and [2] looks empty. Where are the rest of the bugs? Also, > there are on ~150 packages affected in [3]. How many of those fail to > build? The test rebuild was not made in lavels, so a bunch of packages fail to build because they are missing ruby2.5 support in a dependency (ruby-nokogiri being the most common case), so those didn't get a bug report. I checked a sample of the packages listed in the transition page, and those that failed did it either for unrelated reasons, or due to missing ruby2.5 support in dependencies. Anyway, before I enable ruby2.5 in sid I will do a new rebuild with the dependency level n available for level n+1, to make sure.
Attachment:
signature.asc
Description: PGP signature