On 02/07/17 11:16, Sébastien Villemot wrote: > Le vendredi 30 juin 2017 à 12:26 +0200, Emilio Pozuelo Monfort a écrit : >> On 30/06/17 12:03, Sébastien Villemot wrote: >>> Le jeudi 29 juin 2017 à 19:41 +0200, Emilio Pozuelo Monfort a écrit : >>>> On 29/06/17 14:10, Sébastien Villemot wrote: >>>>> Package: release.debian.org >>>>> Severity: normal >>>>> User: release.debian....@packages.debian.org >>>>> Usertags: transition >>>>> X-Debbugs-CC: pkg-octave-de...@lists.alioth.debian.org >>>>> Control: forwarded -1 >>>>> https://release.debian.org/transitions/html/auto-octave.html >>>>> >>>>> Dear Release Team, >>>>> >>>>> Please schedule a transition for octave 4.2. The new package is already in >>>>> experimental. >>>>> >>>>> Few reverse dependencies will need sourceful NMUs. In any case, we stand >>>>> ready to NMU. >>>> >>>> So how many rdeps (and which ones) fail to build atm? >>> >>> Sorry for not having been more specific. >>> >>> Of the 43 rdeps affected by the transition: >>> >>> - We tested the 10 that are not maintained by the Debian Octave Group. >>> They all rebuild correctly. >>> >>> - We did not test the other 33 that are maintained by us. But they >>> should be working fine with Octave 4.2 (according to upstream). And in >>> the unlikely case of a build failure and no available patch, we can >>> request temporary removals from testing, since these are leaf packages. >>> If you think this is necessary before starting the transition, we can >>> test them, even though we feel this is unnecessary work. >> >> No need to. You can go ahead. > > Thanks. Octave 4.2 is now uploaded and built on all release archs.
binNMUs scheduled earlier today. I see you have fixed the two broken packages, so things are looking pretty well. Cheers, Emilio
