On Mon, May 07, 2018 at 01:51:37PM +0200, Rafael Laboissière wrote: > * Sébastien Villemot <sebastien@debian.org> [2018-05-03 12:01]: > > > I have just uploaded Octave 4.4.0 to experimental, so we can start > > planning for the transition. > > > > [snip] > > > > Ensuring that all 'Forge packages are compatible with 4.4 could be > > another task (but can possibly be done as the transition unfolds). > > I launched a preliminary batch for building all the OF packages against > Octave 4.4. At least the following ones have failing builds: > > octave-general > octave-image > octave-interval > octave-linear-algebra > octave-miscellaneous > octave-mpi > octave-nan > octave-nurbs > octave-ocs > octave-odepkg > octave-parallel > octave-sparsersb > octave-tisean Wow, that's a lot. > It would be insane to fix those failures ourselves. I propose that we wait > until the upstream authors release new, 4.4-compliant versions of their > packages. > > That said, we can start the 4.4 transition as soon as appropriate, but there > will be perhaps some blockers like the ones in the above list. I'm not sure that the Release Team will be willing to run the transition with so many rdep failures. Or we must say to the Release Team that we're willing to have them (and their rdeps) removed from testing. If there are fixes in the mercurial upstream repositories (but no new release yet), maybe we could upload mercurial snapshots? (I did not verify how many packages are in such a situation). -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
Attachment:
signature.asc
Description: PGP signature