Your message dated Tue, 22 Feb 2022 17:24:09 +0100
with message-id <[email protected]>
and subject line closing these dangling bugreports
has caused the Debian Bug report #169034,
regarding libstdc++2.10-glibc2.2 bug page refers to gcc-2.96
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.)
--
169034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=169034
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bugs.debian.org
The page reached through http://bugs.debian.org/libstdc++2.10-glibc2.2 says
that the source package is gcc-2.96. The bug reports for today's libstdc++
failure can't be located this way since they have been reassigned to
gcc-2.95.
--- End Message ---
--- Begin Message ---
Hi,
This email closes three bugreports against bugs.debian.org
These dangling BRs scare people in both fixing bugs
and in reporting new bugs.
#169034 last update 2002-11-15
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=169034#15
(and spam on 2015-03-15)
#263852 reported 2004-08-06, no follow-up-email
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=263852
(merged with the other two on 2008-02-19)
#466432 last update 2008-02-18
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466432#10
with text:
We currently do not specially deal with bugs that have been filed
against a particular Source: package as opposed to a particular binary
Package:. In the future this will probably change, but for the time
being, that's how it works.
Don Armstrong
Regards
Geert Stappers
Debian Developer
--
Silence is hard to parse
signature.asc
Description: PGP signature
--- End Message ---
