From: ludo@gnu.org (Ludovic Courtès)
To: Benjamin Andresen <benny@in-ulm.de>
Cc: 29244@debbugs.gnu.org
Subject: bug#29244: guix update -u always wants to update: python-wrapper & python-ipython
Date: Mon, 20 Nov 2017 22:50:07 +0100 [thread overview]
Message-ID: <87vai4zkkw.fsf@gnu.org> (raw)
In-Reply-To: <87o9oafd6g.fsf@in-ulm.de> (Benjamin Andresen's message of "Fri, 10 Nov 2017 14:58:31 +0100")
Hello,
Benjamin Andresen <benny@in-ulm.de> skribis:
> this is with an empty user account that has no packages installed before this:
>> guixsd% guix package -u
>> The following packages will be upgraded:
>> python-wrapper 3.5.3 → 3.5.3 /gnu/store/xnb9bn2vgr3ch8zznsv23w65bb5psshh-python-wrapper-3.5.3
>> python-ipython 5.3.0 → 5.3.0 /gnu/store/7lg8s2kc6k8fxbdx80ykz39kz2lwj08g-python-ipython-5.3.0
>>
>> nothing to be done
>
> The problem exists with both installed and with them individually.
This is because ‘transaction-upgrade-entry’ in (guix profiles)
conservatively assumes that any package with propagated inputs, like
‘python-wrapper’, always has to be upgraded:
(case (version-compare candidate-version version)
((>)
(manifest-transaction-install-entry
(package->manifest-entry pkg output)
transaction))
((<)
transaction)
((=)
(let ((candidate-path (derivation->output-path
(package-derivation (%store) pkg))))
;; XXX: When there are propagated inputs, assume we need to
;; upgrade the whole entry.
(if (and (string=? path candidate-path)
(null? (package-propagated-inputs pkg)))
transaction
(manifest-transaction-install-entry
(package->manifest-entry pkg output)
transaction)))))
I think we can refine this code.
Thanks for your report,
Ludo’.
next prev parent reply other threads:[~2017-11-20 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 13:58 bug#29244: guix update -u always wants to update: python-wrapper & python-ipython Benjamin Andresen
2017-11-20 21:50 ` Ludovic Courtès [this message]
2021-09-16 7:28 ` zimoun
2021-10-12 21:55 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vai4zkkw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29244@debbugs.gnu.org \
--cc=benny@in-ulm.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).