From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: 25095@debbugs.gnu.org
Subject: bug#25095: Multiple output packages causes noop profile generations
Date: Sun, 04 Dec 2016 00:58:08 +0100 [thread overview]
Message-ID: <87eg1o8t0v.fsf@gnu.org> (raw)
In-Reply-To: <8760n2cjl1.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (Marius Bakke's message of "Fri, 02 Dec 2016 18:43:54 +0100")
Marius Bakke <mbakke@fastmail.com> skribis:
> Sorry for the non-descriptive title. It appears that having non-default
> outputs in the profile always causes a new profile generation even if
> the package derivations themselves don't change. Here is an example:
>
> $ guix package -u
> The following packages will be upgraded:
> bind:utils 9.10.4-P4 → 9.10.4-P4 /gnu/store/ypv8jppwn3dvhnkrmibw3p2h35cm30ij-bind-9.10.4-P4-utils
> git:send-email 2.11.0 → 2.11.0 /gnu/store/xnm8msrlh4ac9bxzvf9pgai8xnjjkvwj-git-2.11.0-send-email
> transmission:gui 2.92 → 2.92 /gnu/store/x2q22mfakkkf7nr68nfsxcvci4psz0vi-transmission-2.92-gui
[...]
> $ guix package -u
> The following packages will be upgraded:
> transmission:gui 2.92 → 2.92 /gnu/store/x2q22mfakkkf7nr68nfsxcvci4psz0vi-transmission-2.92-gui
> git:send-email 2.11.0 → 2.11.0 /gnu/store/xnm8msrlh4ac9bxzvf9pgai8xnjjkvwj-git-2.11.0-send-email
> bind:utils 9.10.4-P4 → 9.10.4-P4 /gnu/store/ypv8jppwn3dvhnkrmibw3p2h35cm30ij-bind-9.10.4-P4-utils
Notice how the order was reversed. :-)
This is enough to create a new generation (the order of packages in the
manifest matters because it changes the way collisions are resolved, if
any.)
The reverse is unintended, but I suspect it has nothing to do with
multiple-output packages.
Thanks,
Ludo’.
prev parent reply other threads:[~2016-12-03 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 17:43 bug#25095: Multiple output packages causes noop profile generations Marius Bakke
2016-12-03 23:58 ` Ludovic Courtès [this message]
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=87eg1o8t0v.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25095@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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).