Re: Guix upgrade leads to different hashes

[Oleg Pykhalov]

Hello Ludovic,

address@hidden (Ludovic Courtès) writes:

> Oleg Pykhalov <address@hidden> skribis:
>
>> address@hidden (Ludovic Courtès) writes:
>>
>> [...]
>>
>>> Could you check if this patch helps:
>>>
>>> diff --git a/guix/scripts/package.scm b/guix/scripts/package.scm
>>> index 4adc70522..0e365018a 100644
>>> --- a/guix/scripts/package.scm
>>> +++ b/guix/scripts/package.scm
>>> @@ -604,12 +604,12 @@ and upgrades."
>>>      (options->upgrade-predicate opts))
>>>  
>>>    (define upgraded
>>> -    (fold (lambda (entry transaction)
>>> -            (if (upgrade? (manifest-entry-name entry))
>>> -                (transaction-upgrade-entry entry transaction)
>>> -                transaction))
>>> -          transaction
>>> -          (manifest-entries manifest)))
>>> +    (fold-right (lambda (entry transaction)
>>> +                  (if (upgrade? (manifest-entry-name entry))
>>> +                      (transaction-upgrade-entry entry transaction)
>>> +                      transaction))
>>> +                transaction
>>> +                (manifest-entries manifest)))
>>>  
>>>    (define to-install
>>>      (filter-map (match-lambda
>>
>> Nope, this didn't help :-(
>
> So what’s the diff between two consecutive manifests now?

I'm sorry, actually after patching no new generation created.  But
dry-run still shows available upgrades and that will be build some
derivations.

--8<---------------cut here---------------start------------->8---
$ guix package -p /home/natsu/.my-guix-profile/debug-upgrade -m 
/home/natsu/dotfiles/guix/user.scm
--8<---------------cut here---------------end--------------->8---

txtxi12j1eIqN.txt
Description: guix upgrade

txtlpMQ0MaCP2.txt
Description: guix dry-run upgrade