| Summary: | /var/lib/portage/home should be owned by portage:portage instead of root | ||
|---|---|---|---|
| Product: | Gentoo Release Media | Reporter: | Rahil Bhimjiani <me> |
| Component: | Stages | Assignee: | Gentoo Release Team <releng> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | ajak, bkohler, gentoo, sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=886147 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Rahil Bhimjiani
2023-06-15 01:48:00 UTC
In what context were you getting a bunch of errors? Could you share them in full? It is owned by portage:portage on my systems and in stage3-amd64-systemd-20230611T170207Z.tar.xz. You didn't mention which stage3 tarball you are using. Tested Tarball: https://bouncer.gentoo.org/fetch/root/all/releases/amd64/autobuilds/20230611T170207Z/stage3-amd64-nomultilib-systemd-mergedusr-20230611T170207Z.tar.xz I was getting errors when I tried to use ssh:// URI for GENTOO_MIRRORS saying "couldn't create /var/lib/portage/home/.ssh permission denied" Ok, I can confirm that.
> % tar -tvf stage3-amd64-systemd-mergedusr-20230611T170207Z.tar.xz | grep -F /var/lib/portage/home
> drwxr-xr-x root/root 0 2023-06-11 15:47 ./var/lib/portage/home/
> -rw-r--r-- root/root 0 2022-11-22 21:06 ./var/lib/portage/home/.keep_acct-user_portage-0
Expected result:
> % ls -ld /var/lib/portage/home /var/lib/portage/home/.keep_acct-user_portage-0
> drwxr-xr-x 1 portage portage 50 Jun 15 14:01 /var/lib/portage/home
> -rw-r--r-- 1 root root 0 Jun 15 14:01 /var/lib/portage/home/.keep_acct-user_portage-0
I looked into this a bit and don't have a solution but I have a bit of info to share. This has been broken since the 2022-11-22 build, the previous 2022-11-20 was not broken. The problematic permissions are in the corresponding stage1 as well, so it would appear that the "ROOT=/tmp/stage1root emerge ..." which installs acct-user/portage is not creating the dir with the correct permissions. This could be because the dir already exists ahead of time (it's emerging into a clean ROOT but acct-user/portage is package 88 of 139 to emerge), or because something is going wrong in the acct-user/portage pkg_preinst phase which is supposed to call fowners to set portage:portage as owner. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=91fbc7f77708183b5300199a5cb6fb03bf425913 commit 91fbc7f77708183b5300199a5cb6fb03bf425913 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2023-06-16 20:50:23 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2023-06-16 20:54:32 +0000 acct-user/portage: revbump to ensure proper permissions on HOME Permissions were broken in f1885c714d2082bc29f7269b9342870e084b00ff, and fixed in 22e986ce87b4f983e9508803b83466c5183cde65. Revbump to ensure binpkgs get updated. Bug: https://bugs.gentoo.org/908511 Signed-off-by: Mike Gilbert <floppym@gentoo.org> acct-user/portage/{portage-0.ebuild => portage-0-r1.ebuild} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) We now need to let this propagate into new builds. please mark this as resolved |
