From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Installation and reinstallation of the same binary packages
Date: Thu, 13 Mar 2025 13:34:10 -0500 [thread overview]
Message-ID: <f7a9d8d7-cf9d-0650-98f4-f88bfe43de43@gmail.com> (raw)
In-Reply-To: <CAHVEG0CxAUYYJ7UoDYfGJxiBS6U4PzKEK9uiK4tgtGk51xRCnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
Jacques Montier wrote:
> Le jeu. 13 mars 2025 à 10:33, netfab <netbox253@netc.eu
> <mailto:netbox253@netc.eu>> a écrit :
>
>
> Hi,
>
> Le 12/03/25 à 11:49, Jacques Montier a tapoté :
> > Now, with every emerge world, [...]
>
> Please post the command your are using, and also the whole output from
> emerge. Adding the --tree option to the emerge command could also be
> useful.
>
>
>
>
> Thanks for your responses.
> All the commands and ouput in the attached file.
>
> Cheers,
>
> --
> Jacques
>
If I'm reading this right, sometimes my emerge output decryption tool
doesn't work well, I'd look into dev-util/spirv-headers and see what it
has going on. I'd run the following.
equery list -p dev-util/spirv-headers
That should list all versions of the package. See if something is
masked/keyworded either by the devs or by you. It could be that it
really needs a newer version that is masked or that a newer version is
unmasked and shouldn't be because of other packages it depends on. You
may be able to figure that out yourself but if not, post what it says.
Someone else with a better decryption thought process may have a better
idea.
Dale
:-) :-)
[-- Attachment #2: Type: text/html, Size: 2623 bytes --]
next prev parent reply other threads:[~2025-03-13 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 10:49 [gentoo-user] Installation and reinstallation of the same binary packages Jacques Montier
2025-03-13 9:31 ` Dale
2025-03-13 9:31 ` netfab
2025-03-13 17:24 ` Jacques Montier
2025-03-13 18:34 ` Dale [this message]
2025-03-15 13:53 ` Jacques Montier
2025-03-15 15:44 ` Peter Humphrey
2025-03-16 9:48 ` Jacques Montier
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=f7a9d8d7-cf9d-0650-98f4-f88bfe43de43@gmail.com \
--to=rdalek1967@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