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 All source packages for a given binary package should be displayed
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
Severity: normal
There I was, thinking "should I install libgcc1 3.4.1-5 or should I wait for
it to make its way into sarge"...
Example: http://bugs.debian.org/libgcc1
Presently, the only source package listed here is gcc-3.5, which is only
present in experimental. Source packages for currently available versions
should be listed here: for this package, these are gcc-3.0, gcc-3.3, gcc-3.4
and gcc-3.5. (Mention of which version is in woody, sarge, sarge+1, sid,
experimental may also be of some use.)
Following the link for bug 188976, I see that the wrong source package is
listed: gcc-3.5 rather than gcc-3.0. bugreport.cgi should, I think, be able
to use certain tags (that bug is tagged 'woody') - or, preferably, the
version numbers - in order to determine which source package(s) should be
listed.
(FWIW, a similar problem occurs with packages.qa.debian.org's
redirect-to-source-package script (which is quite useful): it may redirect
you to the "wrong" source package.)
--
| Darren Salt | linux (or ds) at | nr. Ashington,
| woody, sarge, | youmustbejoking | Northumberland
| RISC OS | demon co uk | Toon Army
| I don't ask for much, just untold riches...
What's the difference between a duck?
--- 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 ---
