From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Filesystem with python3_12, but /var/db,cache with python3_13
Date: Mon, 19 May 2025 19:00:35 -0400 [thread overview]
Message-ID: <a20b1a0b-2deb-49ac-b0d0-f1c5637f8372@gentoo.org> (raw)
In-Reply-To: <1827948.VLH7GnMWUR@rogueboard>
[-- Attachment #1.1: Type: text/plain, Size: 1072 bytes --]
On 5/19/25 6:27 PM, Michael wrote:
> No buildpkg on this system. :-(
Gentoo provides a large (45 gb) public buildpkg cache at
https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart
>> I'm not sure how to
>> fix that. Basically, portage stores data on what is installed in /var
>> but the packages are in /, mostly /(s)bin and /usr. Basically, portage
>> thinks one thing but the truth is something else. I suspect emerge
>> isn't happy since it is so confused.
>
> Emerge is not happy when it tries to use package versions which the filesystem
> does not have installed yet. I'll try once more to tweak python targets in
> case I can get emerge to build a working toolchain. If that doesn't work I'll
> fetch a stage 3, build what I need as binaries and then emerge them on the
> live system before I carry on.
With the public binhost you should be able to skip the stage3 and go
straight to emerging a binary toolchain. I'd suggest you should even use
--getbinpkg --emptytree @world for consistency.
--
Eli Schwartz
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2025-05-19 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 9:30 [gentoo-user] Filesystem with python3_12, but /var/db,cache with python3_13 Michael
2025-05-19 13:17 ` Dale
2025-05-19 22:27 ` Michael
2025-05-19 23:00 ` Eli Schwartz [this message]
2025-05-19 23:04 ` Michael
2025-05-20 18:08 ` Michael
2025-05-20 18:42 ` Dale
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=a20b1a0b-2deb-49ac-b0d0-f1c5637f8372@gentoo.org \
--to=eschwartz@gentoo.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