On Sun, Aug 24, 2003 at 05:27:26PM +0100, Colin Watson wrote:
On Sun, Aug 24, 2003 at 08:51:06AM -0700, Kenward Vaughan wrote:
Silly question, perhaps, but I'm very unfamiliar with how one monitors
whether a known problem still exists.
If it's filed in the bug tracking system, at the moment you just have to
look at the bug every so often, although there's some work outstanding
on letting you subscribe to bugs.
If it's not, then you just have to look every so often. In the case of
GNOME, reading the debian-gtk-gnome mailing list would probably be your
best bet, if you aren't prepared to keep a very close eye on the state
of testing (which I try to do for other reasons).
Thanks, Colin.
I just played a bit with apt-listbugs, and it seems to be the quickest way
to update myself on this particular package. Trying 'apt-listbugs list
libc6' gave the same output as I see in an apt-get operation.
I've now also discovered [EMAIL PROTECTED] ... good, fuller source to
follow apt-listbugs.
Another trivia question for someone out there--
I noted the following bug types. Is the pending upload essentially a
fixed bug not in the dist yet? Is resolved one which is fixed? Or is it
different than closed ?
grave bugs of libc6 (2.3.1-17 - ) outstanding
...
grave bugs of libc6 (2.3.1-17 - ) pending upload
...
critical bugs of libc6 (2.3.1-17 - ) resolved
...
TIA,
Kenward
--
In a completely rational society, the best of us would aspire to be
_teachers_ and the rest of us would have to settle for something less,
because passing civilization along from one generation to the next
ought to be the highest honor and the highest responsibility anyone
could have. - Lee Iacocca
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]