This happens regularly at my tinderbox images after an "emaint sync -a" since 4th of december: >>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'... /usr/bin/git fetch origin --verbose --depth 1 POST git-upload-pack (416 bytes) POST git-upload-pack (gzip 5695 to 2767 bytes) From https://github.com/gentoo-mirror/gentoo = [up to date] stable -> origin/stable /usr/bin/git reset --merge refs/remotes/origin/stable === Sync completed for gentoo * Copying old database to /var/cache/eix/previous.eix cp: cannot stat '/var/cache/eix/portage.eix': No such file or directory * Could not copy database to /var/cache/eix/previous.eix * Spawn failed for: 50-eix-postsync, /etc/portage/postsync.d/50-eix-postsync Action: sync for repo: gentoo, returned code = 0 Action: post-sync for repo: None, returned code = 2
commit 81376e34a9dcd743e92f757a17add6081e20150c Author: Florian Schmaus <flow@gentoo.org> Date: Wed Dec 4 11:53:54 2024 +0100 app-portage/eix: add 0.36.7-r2 hooking eix-postsync into portage's postsync As acked by mgorny in #-dev, this makes eix install a symlink that hooks eix-postsync into portage's postsync via /etc/portage/postsync.d. Signed-off-by: Florian Schmaus <flow@gentoo.org> The hook seems to fail on first sync.
Presumably a permission problem: The directory /var/cache/eix should have the permissions given by /usr/lib/tmpfiles.d: drwxrwxr-x 2 portage portage /var/cache/eix -rw-rw-r-- 1 portage portage /var/cache/eix/portage.eix -rw-rw-r-- 1 portage portage /var/cache/eix/previous.eix
@Martin I am not sure that it is a permission problem. Instead, I believe that sam is right that it is an issue on the very first eix-postsync. I've created https://github.com/vaeth/eix/pull/127 which should fix this. I would consider applying the patch from the PR to the eix ebuild, until a version of eix with the fix is released.
Ignore my previous comment. I seem to have looked at an old 'master' branch of eix. Such a check is already in place. This makes the permission thesis more likely. @toralf: could you show us the permissions of /var/cache/eix. Maybe you need to manually create the directory with portage:portage as owner and group in your tinderbox scripts as workaround.
https://github.com/vaeth/eix/commit/c7931407b9f0f7293801845f26f09404b45e35ed Is our version out of date?
(In reply to Florian Schmaus from comment #4) > @toralf: could you show us the permissions of /var/cache/eix. $ ls -ld ~/run/*//var/cache/eix drwxrwxr-x 1 portage portage 0 Dec 5 07:36 /home/tinderbox/run/23.0-20241201-015002/var/cache/eix drwxrwxr-x 1 portage portage 0 Dec 5 08:39 /home/tinderbox/run/23.0_abi32+64-20241201-114734/var/cache/eix drwxrwxr-x 1 portage portage 0 Dec 5 20:32 /home/tinderbox/run/23.0_desktop_gnome-20241130-085002/var/cache/eix drwxrwxr-x 1 portage portage 0 Dec 5 00:10 /home/tinderbox/run/23.0_hardened_systemd-20241130-094502/var/cache/eix drwxrwxr-x 1 portage portage 0 Dec 7 03:16 /home/tinderbox/run/23.0_no_multilib_hardened_systemd-20241204-211002/var/cache/eix drwxrwxr-x 1 portage portage 0 Dec 2 21:25 /home/tinderbox/run/23.0_no_multilib_systemd-20241201-173009/var/cache/eix drwxrwxr-x 1 portage portage 0 Dec 7 02:40 /home/tinderbox/run/23.0_no_multilib_systemd-20241204-215502/var/cache/eix
(In reply to Sam James from comment #5) > https://github.com/vaeth/eix/commit/c7931407b9f0f7293801845f26f09404b45e35ed > > Is our version out of date? Yes, the newest version in portage 0.36.7-r2 while the newest release is 0.36.9.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=924ab6fe1e0c5165d37c9881ef1fa99b9f549b1b commit 924ab6fe1e0c5165d37c9881ef1fa99b9f549b1b Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2024-12-07 10:49:36 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2024-12-07 10:52:04 +0000 app-portage/eix: add 0.36.9, drop 0.36.7-r2 Closes: https://bugs.gentoo.org/945989 Signed-off-by: Florian Schmaus <flow@gentoo.org> app-portage/eix/Manifest | 1 + app-portage/eix/{eix-0.36.7-r2.ebuild => eix-0.36.9.ebuild} | 0 2 files changed, 1 insertion(+)
