Your message dated Sat, 27 Apr 2024 18:16:05 +0000
with message-id <e1s0maj-00ctra...@fasolo.debian.org>
and subject line Bug#1069931: Removed package(s) from experimental
has caused the Debian Bug report #1069931,
regarding RM: jellyfish/experimental -- RoQA; NVIU; t64 transition reverted
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.)
--
1069931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
after restricting jellyfish to 64-bit architectures the t64 transition
has been reverted and the corresponding packages can be removed again
from experimental.
jellyfish | 2.3.1-2.1~exp1 | experimental | source
jellyfish | 2.3.1-3 | unstable | source
Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:
jellyfish | 2.3.1-2.1~exp1 | source, amd64, arm64, armel, armhf, i386,
mips64el, ppc64el, riscv64
jellyfish-examples | 2.3.1-2.1~exp1 | all
libjellyfish-2.0-2t64 | 2.3.1-2.1~exp1 | amd64, arm64, armel, armhf, i386,
mips64el, ppc64el, riscv64
libjellyfish-2.0-dev | 2.3.1-2.1~exp1 | amd64, arm64, armel, armhf, i386,
mips64el, ppc64el, riscv64
libjellyfish-perl | 2.3.1-2.1~exp1 | amd64, arm64, armel, armhf, i386,
mips64el, ppc64el, riscv64
python3-dna-jellyfish | 2.3.1-2.1~exp1 | amd64, arm64, armel, armhf, i386,
mips64el, ppc64el, riscv64
------------------- Reason -------------------
RoQA; NVIU; t64 transition reverted
----------------------------------------------
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.
Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System. Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1069...@bugs.debian.org.
The full log for this bug can be viewed at https://bugs.debian.org/1069931
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 ---
