Your message dated Thu, 12 Dec 2019 03:39:23 +0000
with message-id <[email protected]>
and subject line Bug#946585: Removed package(s) from unstable
has caused the Debian Bug report #946585,
regarding RM: octave-ocs -- RoQA; uninstallable, indirectly depends on gcc-7
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.)
--
946585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946585
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: block 932051 by -1
Please consider removing octave-ocs from unstable.
octave-ocs was removed from testing more than a year ago, and is
uninstallable in unstable (it depends on liboctave6, but octave now
provides liboctave7). It is one of a few remaining packages blocking
the removal of gcc-7, which was first requested back in March.
Maintainers in CC to check for objections; if you object to this removal,
please fix #902198 in octave-odepkg and get both packages uploaded or
binNMU'd with the current gcc version.
ftp team: if octave-ocs is removed, please revisit #932051, which will
be unblocked at that point as far as I can see.
smcv
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
octave-ocs | 0.1.5-7 | source
octave-ocs | 0.1.5-7+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel,
ppc64el, s390x
------------------- Reason -------------------
RoQA; uninstallable, indirectly depends on gcc-7
----------------------------------------------
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.
Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.
We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected].
The full log for this bug can be viewed at https://bugs.debian.org/946585
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
