Your message dated Sun, 08 Sep 2024 05:08:39 +0000
with message-id <e1snaab-007ze2...@fasolo.debian.org>
and subject line Bug#1081051: Removed package(s) from unstable
has caused the Debian Bug report #1081051,
regarding RM: mozjs102 -- RoM; unmaintained, use mozjs128 instead
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 ow...@bugs.debian.org
immediately.)
--
1081051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
User: ftp.debian....@packages.debian.org
Usertags: remove
Control: affects -1 src:mozjs102
X-Debbugs-Cc: mozjs...@packages.debian.org
Please remove mozjs102
mozjs is the SpiderMonkey JavaScript engine for Firefox. mozjs102 is
from Firefox ESR 102 which is no longer supported. It has no remaining
reverse dependencies in Unstable.
The supported alternative is mozjs128. mozjs115 is also in Debian
Unstable and Testing and was originally expected to reach End of Life
this month, but it will apparently be supported until March for old
Windows and macOS. https://bugs.debian.org/1081040
On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
libmozjs-102-0t64 | 102.15.1-5 | amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, riscv64, s390x
libmozjs-102-dev | 102.15.1-5 | amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, riscv64, s390x
mozjs102 | 102.15.1-5 | source
------------------- Reason -------------------
RoM; unmaintained, use mozjs128 instead
----------------------------------------------
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 1081...@bugs.debian.org.
The full log for this bug can be viewed at https://bugs.debian.org/1081051
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
