Bug#817263: [debian-mysql] Bug#817263: Removed package(s) from unstable
Hello! 2016-03-10 10:22 GMT+02:00 Adam D. Barratt: >> Oh crap. Now all of our build logs (very important to debug various >> build/testsuite failures and their occurences on different platforms) >> have been lost, > > > https://buildd.debian.org/status/logs.php?pkg=mariadb-10.0 doesn't look very > lost (one click away from > https://buildd.debian.org/status/package.php?p=mariadb-10.0) Thanks for pointing that out. I only looked at https://buildd.debian.org/status/package.php?p=mariadb-10.0 which was empty. >> also all bugs have been lost etc.. > > > No, they're not. Worst case you need to re-open them. Please be less > melodramatic. Yes, it seems they are still there but in closed state: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=mariadb-10.0 There is still quite a lot of extra work to do here to recover, as I need to check everything that is stored externally from the package (bugs, debtags etc) and asses what needs to be recovered and then execute the recovery. Some melodramatism is surely justified :)
Bug#817263: [debian-mysql] Bug#817263: Removed package(s) from unstable
On 2016-03-10 7:02, Otto Kekäläinen wrote: 2016-03-10 0:13 GMT+02:00 Debian FTP Masters: We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: mariadb-10.0 Oh crap. Now all of our build logs (very important to debug various build/testsuite failures and their occurences on different platforms) have been lost, https://buildd.debian.org/status/logs.php?pkg=mariadb-10.0 doesn't look very lost (one click away from https://buildd.debian.org/status/package.php?p=mariadb-10.0) also all bugs have been lost etc.. No, they're not. Worst case you need to re-open them. Please be less melodramatic. Regards, Adam
Bug#817263: [debian-mysql] Bug#817263: Removed package(s) from unstable
2016-03-10 0:13 GMT+02:00 Debian FTP Masters: > We believe that the bug you reported is now fixed; the following > package(s) have been removed from unstable: mariadb-10.0 Oh crap. Now all of our build logs (very important to debug various build/testsuite failures and their occurences on different platforms) have been lost, also all bugs have been lost etc.. I can re-upload so I don't mind the binaries themselves being lost, but all the QA tooling is lost and really hurts a lot. Is there some way to undo this? Any backups? Also the process of syncing to Ubuntu got disrupted now at a very bad time, because we needed to get a few bugfixes in before the release of 16.04. Please, is there any way to undo this and get back the situation we had 9 hours ago?