guix package dry-run upgrade shows not required derivations (UI issue)

  • Done
  • quality assurance status badge
Details
2 participants
  • Oleg Pykhalov
  • zimoun
Owner
unassigned
Submitted by
Oleg Pykhalov
Severity
normal
O
O
Oleg Pykhalov wrote on 8 Oct 2017 09:06
(address . bug-guix@gnu.org)
87376u5dal.fsf_-_@gmail.com
Previous discussion thread and attached debugging files:


After patching no new generation created. But dry-run still shows
available upgrades and that will be build some derivations.

ludo@gnu.org (Ludovic Courtès) writes:

Toggle quote (2 lines)
> I’ve pushed the above patch as eca16a3d1d9e6b2c064e0105c1015258bf2755f2.
> Now we need to fix the UI side of things.
Z
Z
zimoun wrote on 16 Sep 2021 09:18
Re: bug#28743: guix package dry-run upgrade incorrect behaviour with verbosity
(name . Oleg Pykhalov)(address . go.wigust@gmail.com)
86a6kdrnsz.fsf_-_@gmail.com
Hi,

This old bug [1] is about dry-run. IIUC, it is not now fixed as shown
below. However, there is another annoying thing about the option
’--verbosity’.


On Sun, 08 Oct 2017 at 10:06, Oleg Pykhalov <go.wigust@gmail.com> wrote:
Toggle quote (12 lines)
> ludo@gnu.org (Ludovic Courtès) writes:

> Previous discussion thread and attached debugging files:
> https://lists.gnu.org/archive/html/help-guix/2017-10/msg00000.html
>
>
> After patching no new generation created. But dry-run still shows
> available upgrades and that will be build some derivations.
>
>> I’ve pushed the above patch as eca16a3d1d9e6b2c064e0105c1015258bf2755f2.
>> Now we need to fix the UI side of things.

Let create a profile with a package without the grafts, then check the
update with dry-run, make the upgrade, check the dry-run upgrade again.
All seem fine, right?

Toggle snippet (43 lines)
$ guix package -i r-shiny -p /tmp/foo --no-grafts 2>/dev/null
$ guix package -p /tmp/foo --upgrade --dry-run
The following package would be upgraded:
r-shiny (dependencies or package changed)

The following derivation would be built:
/gnu/store/bqsnn9k5jw3gklbzkzhknqpfikvl3bdy-profile.drv

$ guix package -p /tmp/foo --list-generations
Generation 1 Sep 16 2021 09:04:48 (current)
r-shiny 1.6.0 out /gnu/store/gq31n44a6b815xlrh0zph6vwc7wqqw8c-r-shiny-1.6.0

$ guix package -p /tmp/foo --upgrade --dry-run
The following package would be upgraded:
r-shiny (dependencies or package changed)

The following derivation would be built:
/gnu/store/bqsnn9k5jw3gklbzkzhknqpfikvl3bdy-profile.drv

$ guix package -p /tmp/foo --upgrade
The following package will be upgraded:
r-shiny (dependencies or package changed)

The following derivation will be built:
/gnu/store/bqsnn9k5jw3gklbzkzhknqpfikvl3bdy-profile.drv

building CA certificate bundle...
listing Emacs sub-directories...
building fonts directory...
building directory of Info manuals...
building database for manual pages...
building profile with 1 package...

$ guix package -p /tmp/foo --list-generations
Generation 1 Sep 16 2021 09:04:48
r-shiny 1.6.0 out /gnu/store/gq31n44a6b815xlrh0zph6vwc7wqqw8c-r-shiny-1.6.0

Generation 2 Sep 16 2021 09:06:05 (current)

$ guix package -p /tmp/foo --upgrade --dry-run
guix package: warning: nothing to do

However, let do the same thing with the option ’--verbosity=2’ (equal
deprecated ’--verbose’).

Toggle snippet (16 lines)
$ rm -fr /tmp/foo*
$ guix package -i r-shiny -p /tmp/foo --no-grafts 2>/dev/null
$ guix package -p /tmp/foo --upgrade --dry-run --verbosity=2
The following package would be upgraded:
r-shiny (dependencies or package changed)

$ guix package -p /tmp/foo --list-generations
Generation 1 Sep 16 2021 09:04:48
r-shiny 1.6.0 out /gnu/store/gq31n44a6b815xlrh0zph6vwc7wqqw8c-r-shiny-1.6.0

Generation 2 Sep 16 2021 09:06:05 (current)

$ guix package -p /tmp/foo --upgrade --verbosity=2
guix package: warning: nothing to do

Et voilà! Still a bug. Same with any other ’verbosity’ value.


All the best,
simon
Z
Z
zimoun wrote on 5 Jan 2022 00:06
Re: bug#28743: guix package dry-run upgrade shows not required derivations (UI issue)
(address . 28743-done@debbugs.gnu.org)
86tuejaynk.fsf_-_@gmail.com
Hi,

I cannot reproduce this old bug [1].


So, closing.


Cheers,
simon
Closed
?
Your comment

This issue is archived.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 28743
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