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

Re: Bug#1116026: transition: octave-10



On 29/09/2025 07:19, Rafael Laboissière wrote:
* Rafael Laboissière <rafael@debian.org> [2025-09-28 14:12]:

* Rafael Laboissière <rafael@debian.org> [2025-09-27 18:03]:

* Sébastien Villemot <sebastien@debian.org> [2025-09-27 07:11]:

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

I think I have diagnosed this issue. The autopkgtest errors arise in
the BISTs for var.m and std.m, which should shadow the functions
with the same names that are present in the Octave core. This occurs
when the unit tests are run at build time. However, this does not
happen in the autopkgtest environment. There is probably a bug in
dh-octave-autopktest. I will take a look at it.

I hope I have fixed the issue in commit 72e3af46 [*]. I have uploaded
version 1.7.5-4 of the octave-statistics package to unstable. Let us
see what the autopkgtest run reveals.

It worked:
https://ci.debian.net/packages/o/octave-statistics/testing/amd64/64803536/

I think octave needs to add breaks on octave-statistics (<< 1.7.5-4). That looks to be the last blocker.

Cheers,
Emilio


Reply to: