This is the mail archive of the
overseers@sourceware.org
mailing list for the Sourceware project.
Re: ongoing sourceware.org recovery from disk corruption
- From: Joseph Myers <joseph at codesourcery dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: Sourceware Overseers <overseers at sourceware dot org>
- Date: Tue, 15 Aug 2017 16:23:25 +0000
- Subject: Re: ongoing sourceware.org recovery from disk corruption
- Authentication-results: sourceware.org; auth=none
- References: <20170815133516.GH18258@redhat.com>
Is there any plan regarding Bugzilla (and anything else using databases, I
don't know what there might be beyond Bugzilla)? Inform all the affected
projects of the exact period for which data was lost (extends back to
Sunday afternoon at least according to
<https://gcc.gnu.org/ml/gcc/2017-08/msg00146.html>) and ask them to
systematically redo changes / refile bugs (possibly with new bug numbers)
based on -bugs list archives, or something else? For GCC Bugzilla that's
GCC and Classpath as affected projects; rather more projects for
Sourceware Bugzilla though probably much less activity to restore in
total.
For GCC Bugzilla, the change from
<https://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01289.html> appears to be
present, but not that from
<https://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01290.html> (i.e. a cut-off
early Sunday morning UTC). I don't know for sourceware Bugzilla but it's
at least consistent with that from checking glibc-bugs (but with a larger
gap in time between present and absent changes; there are lots of other
projects that might help narrow down the time).
--
Joseph S. Myers
joseph@codesourcery.com