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

Bug#976386: marked as done (transition: octave)

Your message dated Wed, 23 Dec 2020 23:51:38 +0100
with message-id <X+PJ+rI1yBCI2x57@ramacher.at>
and subject line Re: Bug#976386: transition: octave
has caused the Debian Bug report #976386,
regarding transition: octave
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 owner@bugs.debian.org
immediately.)


-- 
976386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976386
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Control: block -1 by 976200 976199 976198 976201 976202 976203 976204 976205 976206 976207 976210 976212 976381 976382 976385

Dear Release Team,

Please schedule a transition for octave 6, which currently sits in
experimental.

A rebuild of all affected packages has been done. Several problems have been
identified, most of them already fixed in experimental. A few ones remain, but
we (the Debian Octave Group) are confident that we can deal with them swiftly
(if needed by NMU for those that we don’t maintain).

We therefore think that this transition could take place before the bullseye
transition freeze.

Ben file:

title = "octave";
is_affected = .depends ~ /liboctave7|octave-abi-53/ | .depends ~ /liboctave8|octave-abi-55/;
is_good = .depends ~ /liboctave8|octave-abi-55/;
is_bad = .depends ~ /liboctave7|octave-abi-53/;

Cheers,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org

--- End Message ---
--- Begin Message --- 
On 2020-12-22 13:04:16 +0100, Rafael Laboissière wrote:
> * Sébastien Villemot <sebastien@debian.org> [2020-12-21 10:41]:
> 
> > Le lundi 21 décembre 2020 à 10:35 +0100, Sebastian Ramacher a écrit :
> > > 
> > > The blocking issues is indeed plplot. The version in unstable
> > > dropped the octave package, but the version in testing still has it.
> > > So it's part of the octave transition. libplplotada3-dev in unstable
> > > depends on gnat and gnat-10, so is unsable to migrate because gnat
> > > in testing still depends on gnat-9 but gnat-9 and gnat-10 are
> > > conflicting with each other.
> > > 
> > > To unblock the situation, I currently see the following options: *
> > > Upload plplot 5.15.0+dfsg-16 together with the change to drop
> > > octave-plplot to testing-pu [1]. Then plplot would no longer be
> > > involved   in the octave transition and octave would be able to
> > > migrate. * Remove plplot and reverse dependencies from testing.
> > 
> > > [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#t-p-u
> > 
> > Thanks for your analysis. I’m putting Rafael Laboissière (plplot
> > maintainer and member of the Debian Octave Group) in CC, so that he can
> > decide what is the best course of action. My impression is that an
> > upload to testing-proposed-updates would be the least disrupting
> > solution.
> 
> Indeed, the testing-pu solution would be less disruptive, but I prefer to
> temporarily remove plplot from testing.  At any rate, I will not be able to
> upload a new version of plplot until next week, at earliest.

This wasn't necessary after all. octave 61.0-2 and all reverse
dependencies that successfully built migrated to testing. The others
were removed from testing.

Cheers

> 
> Best,
> 
> Rafael
> 

-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: