Your message dated Fri, 10 Oct 2025 12:57:31 +0200
with message-id <[email protected]>
and subject line Re: done? Re: Bug#1116026: transition: octave-10
has caused the Debian Bug report #1116026,
regarding transition: octave-10
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 [email protected]
immediately.)
--
1116026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116026
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
User: [email protected]
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;[email protected]
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";
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
--- End Message ---
--- Begin Message ---
Hi,
Thank you for the reminder. I am hereby closing this bug report.
Best,
Rafael Laboissière
* Rebecca N. Palmer <[email protected]> [2025-10-08 17:40]:
octave 10 is now in testing: should this bug now be closed?
--- End Message ---
