Your message dated Sun, 25 Sep 2022 17:28:23 +0000 with message-id <[email protected]> and subject line Bug#1020638: Removed package(s) from unstable has caused the Debian Bug report #1020638, regarding RM: khmer [arm64] -- ROM; Cannot build on !amd64 due to asm in cqf 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.) -- 1020638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020638 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ftp.debian.org Severity: normal X-Debbugs-Cc: [email protected] Hi, khmer has assembly code in third_party/cqf and can't build on !amd64. The maintainer/uploader reflected that in 3.0.0~a3+dfsg-3 d/ch entry[1] but probably did not file a corresponding -rm bug for !amd64 archs. Before this new upstream release, khmer built on arm64 as well, as far as the list of supported archs is concerned and also as can be seen in the testing version d/control here[2] hence, please remove this package from arm64. [1]: https://tracker.debian.org/news/1359161/accepted-khmer-300a3dfsg-3-source-into-unstable/ [2]: https://sources.debian.org/src/khmer/2.1.2%2Bdfsg-11/debian/control/#L48 Best, Nilesh
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: khmer | 2.1.2+dfsg-11 | arm64 liboxli-dev | 2.1.2+dfsg-11 | arm64 liboxli1 | 2.1.2+dfsg-11 | arm64 ------------------- Reason ------------------- ROM; Cannot build on not amd64 due to asm in cqf ---------------------------------------------- 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 [email protected]. The full log for this bug can be viewed at https://bugs.debian.org/1020638 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 ---
