Your message dated Mon, 25 Jun 2018 12:43:26 +0200 with message-id <b8e09749-6205-818a-8c72-a57db4a07...@debian.org> and subject line Re: Bug#901155: transition: octave-4.4 has caused the Debian Bug report #901155, regarding transition: octave-4.4 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 901155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition Control: forwarded -1 https://release.debian.org/transitions/html/auto-octave.html Dear Release Team, Please schedule a transition for octave 4.4. The new package is already in experimental. Few reverse dependencies will need sourceful NMUs. In any case, we stand ready to NMU. Thanks! -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---On 24/06/18 10:53, Rafael Laboissière wrote: > * Sébastien Villemot <sebast...@debian.org> [2018-06-21 09:29]: >> >> We have fixed most build failures related to the octave 4.4 transition. We >> think the four remaining packages should be removed from testing: >> >> - libsbml: FTBFS for reasons not related to the transition (#901455), has >> another RC bug (#896531), scheduled for removal on July 4th; >> >> - octave-{odepkg,tisean,ltfat}: these packages are maintained by the Debian >> Octave Group, and we currently don't have a patch to fix them. They're all >> leaf packages, except octave-odepkg, whose reverse dependency octave-ocs >> will >> therefore needs to be removed too. > > I am just curious: will the removals of the octave-* packages cited above > happen > automatically or should we do some specific action on our side? I have added removal hints for them and octave has just migrated to testing. Cheers, Emilio
--- End Message ---
