From: Jacques Montier <jmontier@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] No binary llvm-19.1.4 package
Date: Sun, 8 Dec 2024 17:17:15 +0100 [thread overview]
Message-ID: <CAHVEG0Ch_Ct1H_e-_bpj394tchowL-hweJ+L1yqugdjEecvCTg@mail.gmail.com> (raw)
In-Reply-To: <fc7c9947-3ae1-438b-ac54-557daec02409@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]
Le dim. 8 déc. 2024 à 16:18, Eli Schwartz <eschwartz@gentoo.org> a écrit :
> On 12/8/24 6:14 AM, Jacques Montier wrote:
> > I have two Gentoo OS that are supposedly identical.
>
>
> If the entire contents of /etc/portage are identical, then in theory you
> should always get the same packages on both machines. Is it just the
> package list or the entire portage configuration that is identical?
>
>
> > My emerge world :
> > emerge -auvDN --with-bdeps=y --binpkg-respect-use=y --keep-going world
> >
> > emerge --info for the second OS in an attached file.
> >
> >
> > Where could this difference be coming from?
>
>
> Your use of --binpkg-respect-use=y deletes one form of diagnostic. The
> default behavior of portage without that flag specified is for portage to:
>
> - respect USE flags
> - verbosely log a warning if binaries were ineligible due to USE flags
>
> With that flag set to =y, the verbose warning log is disabled. That is all.
>
> Can you try running emerge without that flag? It should print a message
> that looks a bit like this:
>
>
> !!! The following binary packages have been ignored due to non matching
> USE:
>
> =dev-lang/python-3.13.1 llvm_slot_18 -verify-sig
> =dev-lang/python-3.13.1 llvm_slot_18 -pgo -verify-sig
>
> NOTE: The --binpkg-respect-use=n option will prevent emerge
> from ignoring these binary packages if possible.
> Using --binpkg-respect-use=y will silence this warning.
>
> If the issue is USE flags, then that will tell you. The lines printed
> are valid package.use lines which would cause you to start using that
> binary package.
>
>
> --
> Eli Schwartz
>
Thank you Eli for your response.
I saw that the two directories /etc/portage were different, particularly
the make.conf files.
So i copied the first one to replace the second, and everything went back
to normal.
I would have difficulty detecting where the differences between the two
directories came from.
Nevertheless, thank you again for helping me.
Cheers,
--
Jacques
[-- Attachment #2: Type: text/html, Size: 3019 bytes --]
next prev parent reply other threads:[~2024-12-08 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 11:14 [gentoo-user] No binary llvm-19.1.4 package Jacques Montier
2024-12-08 15:17 ` Eli Schwartz
2024-12-08 16:17 ` Jacques Montier [this message]
2024-12-08 22:22 ` Peter Humphrey
2024-12-09 9:42 ` Jacques Montier
2024-12-08 17:39 ` Dr Rainer Woitok
2024-12-08 17:47 ` Eli Schwartz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHVEG0Ch_Ct1H_e-_bpj394tchowL-hweJ+L1yqugdjEecvCTg@mail.gmail.com \
--to=jmontier@gmail.com \
--cc=gentoo-user@lists.gentoo.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