Your message dated Sat, 13 Aug 2022 06:57:42 +0000 with message-id <e1oml5a-0037ez...@fasolo.debian.org> and subject line Bug#876908: Removed package(s) from unstable has caused the Debian Bug report #876908, regarding RM: blcr -- RoQA; unmaintained; broken for several releases 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.) -- 876908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: blcr Version: 0.8.5-2.1 Severity: serious Tags: buster sid As far as I can see: 1. blcr is dead upstream since 2013. 2. blcr requires both userspace and kernel parts. 3. The -dkms package is removed in unstable. 4. The beta version in experimental has an RC bug against the -dkms package that the module does not build with the jessie (sic) kernel. mpich is linked with the userspace library, but does that make any sense without the kernel part?
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: blcr | 0.8.5-2.3 | source blcr-testsuite | 0.8.5-2.3+b1 | amd64, armel, armhf, i386 blcr-util | 0.8.5-2.3+b1 | amd64, armel, armhf, i386 lib32cr0 | 0.8.5-2.3+b1 | amd64 libcr-dbg | 0.8.5-2.3+b1 | amd64, armel, armhf, i386 libcr-dev | 0.8.5-2.3+b1 | amd64, armel, armhf, i386 libcr0 | 0.8.5-2.3+b1 | amd64, armel, armhf, i386 ------------------- Reason ------------------- RoQA; unmaintained; broken for several releases ---------------------------------------------- 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 876...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/876908 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. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
