bug#66754: closed (No guix locate lock error handling)

[GNU bug Tracking System]

Your message dated Thu, 30 Nov 2023 12:55:57 +0100
with message-id <87a5qv5ub6.fsf@gmail.com>
and subject line Re: bug#66754: [PATCH] add guix locate database is locked 
error message
has caused the debbugs.gnu.org bug report #66754,
regarding No guix locate lock error handling
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
66754: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66754
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> No guix locate lock error handling
>
>
>
>
> Date: 
>
> Thu, 26 Oct 2023 03:04:41 +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
>
> guix describe:
>   guix e0b94a4
>     repository URL: https://git.savannah.gnu.org/git/guix.git
>     branch: master
>     commit: e0b94a4d27e6edbc7a87eafdf6fd0e163e0646db
>   nonguix 182ce51
>     repository URL: https://gitlab.com/nonguix/nonguix
>     branch: master
>     commit: 182ce510b5355163fd286553a6fec40bd7935069
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#66754: [PATCH] add guix locate database is locked error message
>
>
>
>
> Date: 
>
> Thu, 30 Nov 2023 12:55:57 +0100
>
>
>
>
> Hi,
>
> Thanks for the contribution.
>
> On sam., 28 oct. 2023 at 19:11, Maciej Kalandyk <m.kalandyk@outlook.com> wrote:
>
> > Change-Id: Iebe76c75d45e70317bd18d2c176dcdeaf9d6964c
>
> It seems it is duplicated and merged with
> ce74e02078b4d2753bf0205fae205a1b704b15d4.  So closing!
>
> Let me know if I am missing something.
>
> Cheers,
> simon
>
>
> --- End Message ---