Your message dated Mon, 15 Aug 2022 17:11:29 +0000
with message-id <[email protected]>
and subject line Bug#1011239: Removed package(s) from unstable
has caused the Debian Bug report #1011239,
regarding RM: ruby2.7 -- ROM; obsolete, superseded by ruby3.0
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.)
--
1011239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011239
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: [email protected]
Please remove ruby2.7 from unstable, as we have completed the switch to
ruby3.0.
As of today there will be 2 dependencies broken by this, but that's
because the failed the transition are currently broken. When they get
fixed they will pick up dependencies on ruby3.0, so it's ok to leave
them broken at the moment.
Checking reverse dependencies...
# Broken Depends:
ruby-ferret: ruby-ferret
ruby-gitlab-pg-query: ruby-gitlab-pg-query [i386 mips64el mipsel s390x]
Thanks.
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
libruby2.7 | 2.7.4-1+deb11u1 | ppc64el
libruby2.7 | 2.7.5-1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel,
s390x
ruby2.7 | 2.7.4-1+deb11u1 | source, ppc64el
ruby2.7 | 2.7.5-1 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, s390x
ruby2.7-dev | 2.7.4-1+deb11u1 | ppc64el
ruby2.7-dev | 2.7.5-1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel,
s390x
ruby2.7-doc | 2.7.5-1 | all
------------------- Reason -------------------
ROM; obsolete, superseded by ruby3.0
----------------------------------------------
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/1011239
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.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
