Package: bugs.debian.org
Severity: normal

dbus-python has a bug listed in
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=dbus-python
where the original bug report is not accessible via the web.

When I first accessed
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936371
I got this:

> An error occurred. Error was: Bad bug log for Bug 936371. Unable to read
> records: state kill-init at end at /usr/local/lib/site_perl/Debbugs/Log.pm
> line 320.

and when I tried

$ bts show --mbox 936371

I initially got a 500 internal server error.

Now that I've marked the bug as blocking another bug (which I was able to
do from its subject line), the only thing in the mbox or bug record is the
information that I did so - the actual bug report seems to have been lost.

Please could someone check what has happened on the server? For a mass-bug
this isn't particularly bad, because I can extrapolate what the bug must
have said from its hundreds of friends, but for a unique bug this would
have been problematic.

Thanks,
    smcv

Reply via email to