On Tuesday, 20 May 2025 00:00:35 British Summer Time Eli Schwartz wrote: > 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.
Thank you Eli, I'll take a look at this approach as it will be a quicker option.
signature.asc
Description: This is a digitally signed message part.
