[core-updates-frozen] ‘--dry-run’ is ineffective

  • Done
  • quality assurance status badge
Details
One participant
  • Ludovic Courtès
Owner
unassigned
Submitted by
Ludovic Courtès
Severity
normal
Merged with
L
L
Ludovic Courtès wrote on 10 Nov 2021 00:34
(address . bug-guix@gnu.org)
87o86shpj3.fsf@inria.fr
I just noticed that ‘-n’ is ineffective:

Toggle snippet (12 lines)
$ ./pre-inst-env guix build elogind -n --no-grafts -v1
The following derivation would be built:
/gnu/store/d20fvmyywlavvbbda101k2906nxfn4l0-elogind-243.7.drv

20.6 MB would be downloaded
$ ./pre-inst-env guix build elogind -n -v1
guile-3.0.7 6.9MiB 4.5MiB/s 00:02 [##################] 100.0%
^C
$ git log |head -1
commit d855119eceb838ce56d45157a3f45f97dc7a1749

Ludo’.
L
L
Ludovic Courtès wrote on 10 Nov 2021 00:44
Re: bug#51732: [core-updates-frozen] ‘--dry-run ’ is ineffective
(address . 51732-done@debbugs.gnu.org)
87k0hghp1i.fsf@gnu.org
Ludovic Courtès <ludo@gnu.org> skribis:

Toggle quote (13 lines)
> I just noticed that ‘-n’ is ineffective:
>
> $ ./pre-inst-env guix build elogind -n --no-grafts -v1
> The following derivation would be built:
> /gnu/store/d20fvmyywlavvbbda101k2906nxfn4l0-elogind-243.7.drv
>
> 20.6 MB would be downloaded
> $ ./pre-inst-env guix build elogind -n -v1
> guile-3.0.7 6.9MiB 4.5MiB/s 00:02 [##################] 100.0%
> ^C
> $ git log |head -1
> commit d855119eceb838ce56d45157a3f45f97dc7a1749

Fixed in 745d3a9b44f93af6fa84468b4b846d1104a73007.

This regression that made it in the recent merge of ‘master’, in commit
1c94392a13cbdf87e03a644633eb775bf45694a1. (There’s no such problem on
‘master’ because there the store’s object identity is preserved.)

Ludo’.
Closed
L
L
Ludovic Courtès wrote on 10 Nov 2021 12:49
control message for bug #51732
(address . control@debbugs.gnu.org)
875yt0grid.fsf@gnu.org
merge 51732 51535
quit
?
Your comment

This issue is archived.

To comment on this conversation send an email to 51732@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 51732
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch