------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-desktop-plasma-systemd_libressl_20190321-223608 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-8.3.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) Available Rust versions: [1] rust-1.32.0 * emerge -qpvO sys-apps/baselayout-prefix !!! Repository 'libressl' is missing masters attribute in '/var/db/repos/libressl/metadata/layout.conf'
Created attachment 570780 [details] emerge-info.txt
Created attachment 570782 [details] emerge-history.txt
Created attachment 570784 [details] etc.portage.tbz2
Created attachment 570786 [details] logs.tbz2
Created attachment 570788 [details] sys-apps:baselayout-prefix-2.6-r1:20190325-183433.log
I'm curious why prefix needs baselayout-prefix? Thanks, William
While this is a dupe of bug#681756, I'll keep it open to answer comment #6, as I planned to create some pull request with prefix patches onto baselayout anyway: There are up to 3 variants of Prefix: * RAP as in "RAP ain't Prefix" (USE="prefix") For Android and Ubuntu, using Linux host kernel but it's own glibc. This is most similar to Gentoo Linux and does neither need the prefix-overlay nor baselayout-prefix once bootstrapped. * Prefix Guest (USE="prefix prefix-guest") The original Prefix as invented, using POSIX host libc+kernel. * Prefix Stack (USE="prefix prefix-guest prefix-stack") Use build environment (bash, python, portage, compiler, etc) from some base Prefix (traditionally Prefix Guest on Cygwin) to build packages for platforms (traditionally Win32 using MSVC toolchain) that would not allow for a native portage - but without the whole cross-compilation pain, because Cygwin can very well execute native Win32 binaries. Recently, I have adapted the baselayout prefix patches for potential inclusion into original baselayout, and I'd be happy to get some review comments: https://github.com/haubi/gentoo-baselayout/pull/1 For the ebuild: The baselayout-prefix-2.6-r1 ebuild should work for vanilla Gentoo Linux as well, hence I've added these keywords that caused the tinderbox troubles (didn't expect anyone would merge baselayout-prefix on non-Prefix without purpose).
(In reply to Michael Haubenwallner from comment #7) > (didn't expect anyone would merge baselayout-prefix on non-Prefix without > purpose). Well, whilst the tindebrox should focus on real world problems it sometimes unveils corner cases and/or did stupid stuff - which is intended and/or can be ignored ;)
(In reply to Michael Haubenwallner from comment #7) > While this is a dupe of bug#681756, I'll keep it open to answer comment #6, > as I planned to create some pull request with prefix patches onto baselayout > anyway: > > There are up to 3 variants of Prefix: > > * RAP as in "RAP ain't Prefix" > (USE="prefix") > For Android and Ubuntu, using Linux host kernel but it's own glibc. This is > most similar to Gentoo Linux and does neither need the prefix-overlay nor > baselayout-prefix once bootstrapped. > > * Prefix Guest > (USE="prefix prefix-guest") > The original Prefix as invented, using POSIX host libc+kernel. > > * Prefix Stack > (USE="prefix prefix-guest prefix-stack") > Use build environment (bash, python, portage, compiler, etc) from some base > Prefix (traditionally Prefix Guest on Cygwin) to build packages for > platforms (traditionally Win32 using MSVC toolchain) that would not allow > for a native portage - but without the whole cross-compilation pain, because > Cygwin can very well execute native Win32 binaries. Interesting summary! I think "USE=prefix prefix-stack" should also be possible, for example, user-emerged packages on a Gentoo host.
(In reply to Benda Xu from comment #9) > (In reply to Michael Haubenwallner from comment #7) > > * Prefix Stack > > (USE="prefix prefix-guest prefix-stack") Actually I'm not decided yet if USE="prefix prefix-stack" is enough here. > Interesting summary! I think "USE=prefix prefix-stack" should also be > possible, for example, user-emerged packages on a Gentoo host. Indeed!
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7210d0e93e748f4cdfee6b7d42d06dbf3b1215e7 commit 7210d0e93e748f4cdfee6b7d42d06dbf3b1215e7 Author: Michael Haubenwallner <haubi@gentoo.org> AuthorDate: 2019-05-13 15:09:32 +0000 Commit: Michael Haubenwallner <haubi@gentoo.org> CommitDate: 2019-05-13 15:11:01 +0000 sys-apps/baselayout-prefix: prefix-stack: ROOTPATH needs EPREFIX before BROOT For both EPREFIX and BROOT, portage does add some default PATH before the env.d ROOTPATH. Since bug 667662, anything found in env.d ROOTPATH is not added any more, so env.d ROOTPATH needs to contain BROOT as well, or we end up with BROOT path before EPREFIX path in ROOTPATH. Bug: https://bugs.gentoo.org/681760 Package-Manager: Portage-2.3.62, Repoman-2.3.11 Signed-off-by: Michael Haubenwallner <haubi@gentoo.org> sys-apps/baselayout-prefix/Manifest | 1 + .../baselayout-prefix-2.6-r2.ebuild | 337 +++++++++++++++++++++ 2 files changed, 338 insertions(+)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=46e8c3d51b5fa54d598bbfbdbb7c55877c444d1f commit 46e8c3d51b5fa54d598bbfbdbb7c55877c444d1f Author: Fabian Groffen <grobian@gentoo.org> AuthorDate: 2021-01-18 18:21:11 +0000 Commit: Fabian Groffen <grobian@gentoo.org> CommitDate: 2021-01-18 18:22:07 +0000 sys-apps/baselayout-prefix: add blocker on sys-apps/baselayout Closes: https://bugs.gentoo.org/681760 Package-Manager: Portage-3.0.12, Repoman-3.0.2 Signed-off-by: Fabian Groffen <grobian@gentoo.org> sys-apps/baselayout-prefix/Manifest | 1 - .../baselayout-prefix-2.2-r5.ebuild | 86 ------ .../baselayout-prefix-2.6-r1.ebuild | 336 --------------------- .../baselayout-prefix-2.6-r2.ebuild | 2 + 4 files changed, 2 insertions(+), 423 deletions(-)
