On Fri, 30 Aug 2019, Simon McVittie wrote: > 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.
Hrm; it appears that the original bug report itself wasn't saved properly either. I have a collection of these failures from that mass bug filing (though apparently I'm missing the failure from tap.py) I have the suspicion that this was partially caused by buxtehude being restarted/upgraded around then. I'll try to clean up this mess as I have a chance. -- Don Armstrong https://www.donarmstrong.com A Bill of Rights that means what the majority wants it to mean is worthless. -- U.S. Supreme Court Justice Antonin Scalia
