Summary: | bootstrap-prefix.sh: ln: failed to create symbolic link '${ROOT}/tmp//var/db/repos/gentoo': No such file or directory | ||
---|---|---|---|
Product: | Gentoo/Alt | Reporter: | Alexander Bezrukov <phmagic> |
Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | sam |
Priority: | Low | Keywords: | PATCH |
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | OS X | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Fix for tmp portage tree linking |
Description
Alexander Bezrukov
2020-10-27 04:53:50 UTC
I'm not saying this is wrong or anything, but what bothers me is that this particular bit of code hasn't changed for years, and it certainly did work in the past, so I really wonder why it suddenly stopped working. New versions of portage are rolled out sparingly, and always tested... The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/proj/prefix.git/commit/?id=6c17f821de91c518556ea345a1a88abbe8706bc3 commit 6c17f821de91c518556ea345a1a88abbe8706bc3 Author: Fabian Groffen <grobian@gentoo.org> AuthorDate: 2020-10-27 07:42:40 +0000 Commit: Fabian Groffen <grobian@gentoo.org> CommitDate: 2020-10-27 07:42:40 +0000 scripts/bootstrap-prefix: pre-create portroot For some reason linking the portage tree in the tmp image fails, so ensure whilst setting up all other dirs in /tmp that also the portroot is created. Bug: https://bugs.gentoo.org/751421 Signed-off-by: Fabian Groffen <grobian@gentoo.org> scripts/bootstrap-prefix.sh | 2 ++ 1 file changed, 2 insertions(+) I'm curious if this helps (In reply to Fabian Groffen from comment #1) > I'm not saying this is wrong or anything, but what bothers me is that this > particular bit of code hasn't changed for years, and it certainly did work > in the past, so I really wonder why it suddenly stopped working. I guess this has happened because the default location of portage tree directory (${PORTDIR}) changed from usr/portage to var/db/cache/repos/, that is depth of this path increased. Update of portage per se does not change the location, clean install does. yes, that would be the first thing, but there have been successful bootstraps since that change Ok, seems that e.g. https://bootstrap.prefix.bitzolder.nl/results/x86_64-pc-solaris2.11/20200607 shows this in stage1.log: ln: failed to create symbolic link '/gentoo/bootstrap64-20200607/tmp//var/db/repos/gentoo': No such file or directory So the thing failed, but it never bothered anything for some reason. (In reply to Fabian Groffen from comment #5) > So the thing failed, but it never bothered anything for some reason. That's why I wrote that > I do not know whether this link is actually necessary for bootstrap, > maybe simply removing the offending command is a better solution. I could not spot where this link is used further in the bootstrapping. But I have had no previous experience with gentoo prefix so I consider myself an ignorant dummy at the moment. Ok, let's close it then, thanks :) |