From: "Ludovic Courtès" <ludo@gnu.org>
To: 44737@debbugs.gnu.org
Subject: bug#44737: Packages grafted twice during system install
Date: Thu, 19 Nov 2020 15:10:35 +0100 [thread overview]
Message-ID: <87v9e1h1yc.fsf@inria.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Hello!
While installing 1.2.0rc2 (I selected GNOME), I noticed that different
derivations of the same packages are grafted (screenshot below).
I don’t think it should block 1.2.0 but we should definitely find out
why this happens as this increases installation time and possible disk
usage.
Looking at the first two ungrafted .drvs for libcanberra shown in the
screenshot, both depend on two gdk-pixbuf+svg derivations (!), and one
of them differs. It appears that one of them depends on
libx11-1.6.9.drv while the other depends on libx11-1.6.A.drv.
What I observe here seems different:
--8<---------------cut here---------------start------------->8---
$ guix gc -R $(guix system build ~/src/guix/gnu/system/examples/desktop.tmpl -d)|grep libcanberra-0.30.drv
/gnu/store/qbgfsgmlrnq8gklv8v924j1brqvxk6fl-libcanberra-0.30.drv
/gnu/store/l7413kkgxs04jflafah895034a5rd1kx-libcanberra-0.30.drv
/gnu/store/cpgv7xkv2fzr4vj2wqlcbjrwslshq78y-libcanberra-0.30.drv
$ guix describe
Generacio 166 Nov 16 2020 11:22:04 (nuna)
guix 74eeb11
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 74eeb11daee906cb012f10b6bb3afd254f9ea5c2
--8<---------------cut here---------------end--------------->8---
There are two grafting derivations and one non-grafting. The two
grafting derivations differ in their GTK+ input, presumably because of
multiple outputs.
Ludo’.
[-- Attachment #2: the screenshot --]
[-- Type: image/png, Size: 62578 bytes --]
reply other threads:[~2020-11-19 14:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87v9e1h1yc.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=44737@debbugs.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.
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).