From: "Mike Jones" <mike@mjones.io>
To: "Hartmut Goebel" <h.goebel@crazy-compilers.com>,
"guix.rc7ys--- via" <help-guix@gnu.org>
Subject: Re: Two copies of same library in store after cleaning generations and gc
Date: Thu, 18 Aug 2022 20:30:17 +0000 [thread overview]
Message-ID: <bb1f9688-3773-439f-b485-3aa07272343c@www.fastmail.com> (raw)
In-Reply-To: <faa0d97c-d837-0818-fe0a-c0dd7c46f429@crazy-compilers.com>
Hello,
Thanks for the hints.
> I assume you installed mesa into your profile — or some other package
> installed in your profile has mesa as „propagated input“.
>
> Try „guix package -l“ to see whether it is installed in your profile.
I haven't installed mesa explicitly, and it doesn't show up in `guix
package -l`, so I think you must be right that it's coming from a
propagated input.
I still wonder, though, why there are two different builds of mesa
appearing. I suspected it might be related to grafting, so I poked
around in /gnu/store and found the .drv files that produced these two
different copies. They both seem to be the result of a grafting process.
If I rebuild my profile with --no-grafts, the mesa used by programs and
the one in the profile are the same, so I'll just put this down to some
weirdness with grafting.
- Mike
next prev parent reply other threads:[~2022-08-18 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 11:31 Two copies of same library in store after cleaning generations and gc Mike Jones
2022-08-18 12:13 ` Hartmut Goebel
2022-08-18 20:30 ` Mike Jones [this message]
2022-08-19 6:13 ` Ricardo Wurmus
2022-08-19 9:06 ` zimoun
2022-08-19 11:37 ` Mike Jones
2022-08-22 15:49 ` 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=bb1f9688-3773-439f-b485-3aa07272343c@www.fastmail.com \
--to=mike@mjones.io \
--cc=h.goebel@crazy-compilers.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).