[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1116026: transition: octave-10



On 27/09/2025 13:22, Adrian Bunk wrote:
On Sat, Sep 27, 2025 at 07:11:22AM -0400, Sébastien Villemot wrote:
Le samedi 27 septembre 2025 à 09:31 +0200, Rafael Laboissière a écrit :
* Sébastien Villemot <sebastien@debian.org> [2025-09-23 12:30]:

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: debian-octave@lists.debian.org
User: release.debian.org@packages.debian.org
Usertags: transition

Dear Release Team,

Please schedule a transition for the latest major upstream version of Octave,
version 10. All the arch:any Octave addons need to be rebuild.

Octave 10 has already been uploaded to experimental.

A rebuild of all the packages affected by the transition has been performed.
Bugs were filed, see:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=octave-10;users=debian-octave@lists.debian.org

All issues but one have fixes ready or even applied. For octave-stk, no
solution is ready yet, so it will have to temporarily go out of testing.

We stand ready to upload and NMU as needed if other issues arise.

Thanks,

Ben file:

  title = "octave-10";
  is_affected = .depends ~ "octave-abi-59" | .depends ~ "octave-abi-60";
  is_good = .depends ~ "octave-abi-60";
  is_bad = .depends ~ "octave-abi-59";

Thanks for this work, Sébastien.

It seems that the transition is finished [*], besides the known issue
with octave-stk.

Is it time to request the biNMUs?

The binNMU have precisely been performed by the Release Team. This is
why the table is all green, except for octave-stk.

Besides octave-stk, it seems that there is problem with octave-
statistics autopkgtests, see:
https://tracker.debian.org/pkg/octave

And a piuparts problem:
∙ ∙ Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/octave.html

   0m19.3s ERROR: FAIL: debsums reports modifications inside the chroot:
     /usr/share/octave/site/api-v60/octave_packages

Sebastien, Rafael: have you seen the above piuparts failure? Most other issues have been addressed, but this remains and it is blocking the transition.

Cheers,
Emilio


Reply to: