emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#51535: closed ([core-updates-frozen] --dry-run option stopped workin


From: GNU bug Tracking System
Subject: bug#51535: closed ([core-updates-frozen] --dry-run option stopped working)
Date: Tue, 09 Nov 2021 23:47:03 +0000

Your message dated Wed, 10 Nov 2021 00:46:26 +0100
with message-id <87czn8hoz1.fsf@gnu.org>
and subject line Re: bug#51535: [core-updates-frozen] --dry-run option stopped 
working
has caused the debbugs.gnu.org bug report #51535,
regarding [core-updates-frozen] --dry-run option stopped working
to be marked as done.

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


-- 
51535: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=51535
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [core-updates-frozen] --dry-run option stopped working Date: Mon, 01 Nov 2021 01:59:31 +0000
On a fresh pull of core-updates-frozen it seems the --dry-run option has 
stopped doing anything.

My test case is guix build --dry-run qtwebkit (no subs currently), but guix 
immediately starts compiling qtwebkit. I can't be sure when it started, but my 
most recent pull was from a41f93c39d03143ce9007ad278a04fa30498bc0b to        
7e8e07033d2a6b0ecef566a05084c534c774cd4a It may have started before that though.



--- End Message ---
--- Begin Message --- Subject: Re: bug#51535: [core-updates-frozen] --dry-run option stopped working Date: Wed, 10 Nov 2021 00:46:26 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Hi John,

John Kehayias <john.kehayias@protonmail.com> skribis:

> On a fresh pull of core-updates-frozen it seems the --dry-run option has 
> stopped doing anything.
>
> My test case is guix build --dry-run qtwebkit (no subs currently), but guix 
> immediately starts compiling qtwebkit. I can't be sure when it started, but 
> my most recent pull was from a41f93c39d03143ce9007ad278a04fa30498bc0b to      
> 7e8e07033d2a6b0ecef566a05084c534c774cd4a It may have started before that 
> though.

Indeed.  I discovered it independently and filed a different bug, now fixed:

  https://issues.guix.gnu.org/51732

Thanks!

Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]