[arch-dev-public] Be careful when releasing packages
Hi all, we just had a couple of problems again with the repo-add dying in the middle of updating the db. There are still some differences, so please have a look and fix you packages: http://www.archlinux.org/packages/differences/ ATM I cannot recommend releasing new packages or moving them until the server is fixed. If you ignore this warning make sure you really know how to recover the repo manually (which is really annoying btw.) I also don't see an easy way to implement automatic recover on any error in dbscripts. (and even if I implement it, its very likely that this recovery would segfault itself in the middle of some action and screw things up even more) In some cases it might be possible to restore the db file by copying over the db.old file (make sure to make another backup of the original db file before). I have also disabled the cleanup script. Greetings, Pierre -- Pierre Schmitz, https://users.archlinux.de/~pierre
On 12/08/2010 09:19 PM, Pierre Schmitz wrote:
Hi all,
we just had a couple of problems again with the repo-add dying in the middle of updating the db. There are still some differences, so please have a look and fix you packages: http://www.archlinux.org/packages/differences/
ATM I cannot recommend releasing new packages or moving them until the server is fixed. If you ignore this warning make sure you really know how to recover the repo manually (which is really annoying btw.) I also don't see an easy way to implement automatic recover on any error in dbscripts. (and even if I implement it, its very likely that this recovery would segfault itself in the middle of some action and screw things up even more)
In some cases it might be possible to restore the db file by copying over the db.old file (make sure to make another backup of the original db file before). I have also disabled the cleanup script.
Greetings,
Pierre
all of them fixed -- Ionuț
On Wed, Dec 8, 2010 at 3:18 PM, Ionuț Bîru <ibiru@archlinux.org> wrote:
On 12/08/2010 09:19 PM, Pierre Schmitz wrote:
Hi all,
we just had a couple of problems again with the repo-add dying in the middle of updating the db. There are still some differences, so please have a look and fix you packages: http://www.archlinux.org/packages/differences/
ATM I cannot recommend releasing new packages or moving them until the server is fixed. If you ignore this warning make sure you really know how to recover the repo manually (which is really annoying btw.) I also don't see an easy way to implement automatic recover on any error in dbscripts. (and even if I implement it, its very likely that this recovery would segfault itself in the middle of some action and screw things up even more)
In some cases it might be possible to restore the db file by copying over the db.old file (make sure to make another backup of the original db file before). I have also disabled the cleanup script.
Greetings,
Pierre
all of them fixed
Since it's fixed, should the cleanup script be re-enabled?
-- Ionuț
On Thu, 9 Dec 2010 18:29:25 -0500, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Wed, Dec 8, 2010 at 3:18 PM, Ionuț Bîru <ibiru@archlinux.org> wrote:
On 12/08/2010 09:19 PM, Pierre Schmitz wrote:
Hi all,
we just had a couple of problems again with the repo-add dying in the middle of updating the db. There are still some differences, so please have a look and fix you packages: http://www.archlinux.org/packages/differences/
ATM I cannot recommend releasing new packages or moving them until the server is fixed. If you ignore this warning make sure you really know how to recover the repo manually (which is really annoying btw.) I also don't see an easy way to implement automatic recover on any error in dbscripts. (and even if I implement it, its very likely that this recovery would segfault itself in the middle of some action and screw things up even more)
In some cases it might be possible to restore the db file by copying over the db.old file (make sure to make another backup of the original db file before). I have also disabled the cleanup script.
Greetings,
Pierre
all of them fixed
Since it's fixed, should the cleanup script be re-enabled?
No, nothing has been fixed. The server is still broken. -- Pierre Schmitz, https://users.archlinux.de/~pierre
participants (3)
-
Eric Bélanger
-
Ionuț Bîru
-
Pierre Schmitz