Your message dated Fri, 02 Dec 2022 17:51:27 +0000 with message-id <e1p1ac7-009n09...@fasolo.debian.org> and subject line Bug#1025199: Removed package(s) from unstable has caused the Debian Bug report #1025199, regarding RM: kraken [armel armhf i386 s390x] -- ROM; dependency jellifish1 doesn't support 32-bit archs 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.) -- 1025199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: ftp.debian.org Severity: normal Control: tag 1016005 - moreinfo Hi ftpmaster, I noticed a couple of Debian Med packages stuck out of testing due to jellyfish1 lack of proper 32-bits support (and probably lack of big endian support too, given s390x presence in the list). To be honest, since plain jellyfish moved on with later versions, I wouldn't expect any change on the 32-bit front for the time being, for it or reverse dependencies. Please kindly remove kraken from the listed architectures. Have a nice day, :) -- .''`. Étienne Mollier <emoll...@debian.org> : :' : gpg: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/3, please excuse my verbosity `- on air: IQ - Until The End
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: kraken | 1.1.1-4 | armel, armhf, i386, s390x ------------------- Reason ------------------- ROM; dependency jellifish1 doesn't support 32-bit archs ---------------------------------------------- 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 http://snapshot.debian.org/. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1025...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1025199 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 ---
