Your message dated Thu, 18 Sep 2008 17:42:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Singleton cloned bugs are now properly linked
has caused the Debian Bug report #495868,
regarding on cloning bugs the bug # of the cloned bug isn't shown
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.)
--
495868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495868
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: minor
Hello,
#477090 has been cloned as #483971.
Both bugreports show only `Bug 477090 cloned as bug .',
i.e. there's no link to 483971
-- System Information:
Debian Release: lenny/sid
APT prefers experimental
APT policy: (500, 'experimental'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Singleton clone bugs are now properly linked as they were before.
Don Armstrong
--
You could say she lived on the edge... Well, maybe not exactly on the edge,
just close enough to watch other people fall off.
-- hugh macleod http://www.gapingvoid.com/Moveable_Type/archives/000309.html
http://www.donarmstrong.com http://rzlab.ucr.edu
--- End Message ---
