From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Issue with new hardened profiles 23.0
Date: Thu, 28 Mar 2024 12:04:04 +0100 [thread overview]
Message-ID: <1976037.PYKUYFuaPT@persephone> (raw)
In-Reply-To: <a79531d1-d0c9-5e0a-509e-a6f752b52a45@hanft.de>
On Thursday, 28 March 2024 11:23:29 CET Matthias Hanft wrote:
> J. Roeleveld wrote:
> > Do you use the binary packages supplied by Gentoo?
> > Or all local-compiled?
>
> All local-compiled, with the exemption of "monster-packages" which
> would take hours or even days to compile (e.g. rust - here I use
> "dev-lang/rust-bin" instead).
>
> I don't even have any of /etc/portage/binrepos.conf or /var/cache/binpkgs/
> (and "emerge --getbinpkg ..." displays a warning that it won't work).
>
> -Matt
Then I assume the issue is caused by the packages Gentoo supplies.
I'll work around it :)
--
Joost
prev parent reply other threads:[~2024-03-28 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 6:52 [gentoo-user] Issue with new hardened profiles 23.0 J. Roeleveld
2024-03-28 7:42 ` Matthias Hanft
2024-03-28 9:26 ` J. Roeleveld
2024-03-28 10:23 ` Matthias Hanft
2024-03-28 11:01 ` Michael
2024-03-28 11:07 ` J. Roeleveld
2024-03-28 11:04 ` J. Roeleveld [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1976037.PYKUYFuaPT@persephone \
--to=joost@antarean.org \
--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