Your message dated Sat, 28 Dec 2024 03:35:03 +0000 with message-id <[email protected]> and subject line Bug#1090783: Removed package(s) from unstable has caused the Debian Bug report #1090783, regarding RM: bird -- ROM; BIRD 1.x is EOL upstream 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.) -- 1090783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090783 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ftp.debian.org Severity: normal User: [email protected] Usertags: remove X-Debbugs-Cc: [email protected] Control: affects -1 + src:bird Legacy BIRD 1.x EOL since 2023, quoting https://bird.network.cz/pipermail/bird-users/2023-April/016874.html > Last version of BIRD 1 was 1.6.8 released in September 2019. We have > already declared that we wouldn't release any other version of legacy > BIRD 1 unless a serious security bug is found. It's time to say that > BIRD 1 is reaching its end of life at the end of the year 2023. bird2 (2.x) package has been available for a long time and now bird3 (3.0.0) waits in NEW queue to enter experimental so I see no good reason to keep dead BIRD (Norwegian Blue?) in Trixie and behind.
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: bird | 1.6.8-2.1 | source bird | 1.6.8-2.1+b3 | amd64, armel, armhf, i386, mips64el, ppc64el, s390x bird | 1.6.8-2.1+b4 | arm64, riscv64 bird-bgp | 1.6.8-2.1 | all bird-doc | 1.6.8-2.1 | all ------------------- Reason ------------------- ROM; replaces with src:bird2 and src:bird3 ---------------------------------------------- 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 [email protected]. The full log for this bug can be viewed at https://bugs.debian.org/1090783 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. Paul Richards Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
