GNU bug report logs - #66745
No guix locate database lock handling

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 66745 in the body.
You can then email your comments to 66745 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Maciej Kalandyk <m.kalandyk <at> outlook.com>
To: guix-patches <at> gnu.org
Subject: No guix locate database lock handling
Date: Wed, 25 Oct 2023 12:09:15 +0200

If you run guix locate when another guix locate that is generating
database is running the former is going to crash with database is locked
"raw" error

It should either wait for lock to be released or display an "formatted"
error

Message #10 received at 66745-done <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <othacehe <at> gnu.org>
To: Maciej Kalandyk <m.kalandyk <at> outlook.com>
Cc: 66745-done <at> debbugs.gnu.org
Subject: Re: bug#66745: No guix locate database lock handling
Date: Wed, 25 Oct 2023 13:38:09 +0200

Hello,

> If you run guix locate when another guix locate that is generating
> database is running the former is going to crash with database is locked
> "raw" error
>
> It should either wait for lock to be released or display an "formatted"
> error

Would you mind sending the same report to bug-guix <at> gnu.org which is the
mailing list for bug reports?

Thanks,

Mathieu

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.