From: Ricardo Wurmus <rekado@elephly.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: `guix package -u` upgrades packages to themselves
Date: Thu, 12 Apr 2018 11:00:54 +0200 [thread overview]
Message-ID: <87lgdsn6ih.fsf@elephly.net> (raw)
In-Reply-To: <87r2nkddmd.fsf@gmail.com>
Hi Chris,
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> That’s because the package version itself is insufficient. In Guix
>> we’re dealing with package “variants”.
>
> Where is the concept of a package "variant" defined? I briefly grepped
> in the source but only found some ad-hoc stuff for Python and OCaml,
> which actually do some kind of stuff with the package-properties.
What I meant is that the version string alone is insufficient. You can
have multiple variants of a package with the same nominal version, but
the differences are in the closure of the package. When Guix is
upgraded in between two invocations of “guix package -u” seeing the same
“version” of a package to be upgraded to is a common occurrence.
> How can the inputs have changed if Pierre is just running "guix package
> -u" repeatedly?
That bit of information was not available to me when I composed my
initial response. If Guix is not changed in between then this behaviour
seems to be a bug.
--
Ricardo
next prev parent reply other threads:[~2018-04-12 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 7:59 `guix package -u` upgrades packages to themselves Pierre Neidhardt
2018-04-11 8:24 ` Ricardo Wurmus
2018-04-11 9:40 ` Pierre Neidhardt
2018-04-11 12:24 ` Martin Castillo
2018-04-24 8:32 ` Ludovic Courtès
2018-04-12 8:37 ` Chris Marusich
2018-04-12 9:00 ` Ricardo Wurmus [this message]
2018-04-13 6:14 ` Chris Marusich
2018-04-13 6:19 ` Pierre Neidhardt
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=87lgdsn6ih.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
/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.
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).