Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 899900

Summary: non-rap bootstrap-prefix.sh failures and fixes
Product: Gentoo/Alt Reporter: hsk17
Component: Prefix SupportAssignee: Gentoo Prefix <prefix>
Status: RESOLVED FIXED    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description hsk17 2023-03-06 14:10:16 UTC
once again i have re-bootstrapped my non-rap prefix installation on top
of opensuse leap, and i want to report on the issues i had to overcome.

summary:  issue 1) should get fixed in tree, and a recent tree snapshot
seems neccessary, possibly (see 4) with updated prefix-portage sources.

1) this one also affects upgrading existing non-rap prefix, not only
bootstrap.

since 1.10.1-r2, the ebuild for dev-libs/libgcrypt has +getentropy
in IUSE, adding dependency on glibc or musl.  this does not work, if
the prefix uses the host libc.  to bootstrap, i solved this by adding

echo 'dev-libs/libgcrypt -getentropy' >> "${ROOT}"/etc/portage/package.use

to bootstrap_stage3() in bootstrap-prefix.sh, but i think this should
go somewhere into the prefix profiles.
gitweb.gentoo.org/repo/gentoo.git/commit?id=8d8e261 did not help in my case.

2) using the current bootstrap tree, i.e. 20221104, fails with Manifest
errors w.r.t. dev-libs/libgpg-error, see also bug 883371.  after adding
to bootstrap-prefix.sh some sed commands to manipulate
dev-libs/libgpg-error/Manifest in the downloaded  prefix-overlay-20221104,
and with the change from 1) above, running non-rap bootstrap-prefix.sh
succeeds.

3) OTOH, applying the change from 1) to bootstrap-prefix.sh and running

  LATEST_TREE_YES=1 PREFIX_DISABLE_RAP=yes bootstrap-prefix.sh

succeeds.

4) inspired by the comment at the beginning of bootstrap_portage(),
i also tried to bootstrap latest tree using portage from current prefix
tree, i.e., 3.0.34.2, but bootstrap_portage() fails on non-existant
readpecoff.  this i found fixed but not yet released in
gitweb.gentoo.org/proj/portage.git/commit/?h=prefix&id=32ed39b
Comment 1 Larry the Git Cow gentoo-dev 2023-05-03 19:07:02 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=578ff3ee42365ac9de7f3c80db76b0208b5acbb5

commit 578ff3ee42365ac9de7f3c80db76b0208b5acbb5
Author:     Fabian Groffen <grobian@gentoo.org>
AuthorDate: 2023-05-03 19:06:12 +0000
Commit:     Fabian Groffen <grobian@gentoo.org>
CommitDate: 2023-05-03 19:06:56 +0000

    profiles/prefix/linux/package.use.mask: mask USE=getentroy on libgcrypt
    
    Bug: https://bugs.gentoo.org/899900
    Signed-off-by: Fabian Groffen <grobian@gentoo.org>

 profiles/prefix/linux/package.use.mask | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)
Comment 2 Fabian Groffen gentoo-dev 2023-05-03 19:10:06 UTC
tree snapshot was bumped, I believe portage installs fine too.

I've applied the getentropy USE-mask, it indeed will require a libc in its current form.

Thanks!