x11-plugins/e_modules-tclock-9999 fails to fetch sources during emerge. It fails during the unpack phase with displaying the following: >>> Unpacking source... error: could not lock config file config: Permission denied error: cannot open FETCH_HEAD: Permission denied This is a network error, and is always reproducible. Nor is it a repository issue, I can manually git clone the source without problems. Build log and emerge --info attache separately
Created attachment 361824 [details] emerge --info
Created attachment 361826 [details] Build log
Please check the permissions for the Portage user on your distfiles directory as well as the underlying egit-src directory.
On the system in question $ ls -ld /usr/portage/distfiles/ drwxrwxr-x 5 root portage 352256 Oct 25 00:17 /usr/portage/distfiles/ On another gentoo system without this problem (~x86 in case it matters) $ ls -ld /usr/portage/distfiles/ drwxrwsr-x 5 root portage 376832 Oct 22 10:47 /usr/portage/distfiles/ I copied distfiles over from the working system to the new system using a USB drive and cp -r, because I couldn't get networking to work without installing a recent linux-firmware. I'll try to fix the permissions and see if that sorts the problem out.
I've just moved /usr/portage/distfiles to /usr/portage/distfiles.old and then emerged portage again with $ emerge -1 portage The newly created distfiles had the same permissions as distfiles.old, but emerging the e_modules-tclock worked. I'm guessing it has something to do with permissions on directories inside of distfiles. Thanks though, this has solved my problem. If you need me to do further diagnosis, I'll keep the old distfiles.old directory for a couple of days.
Seems like this was a setup issue on user side, not sure what the enlightenment team can do about it. Anyway, for some additional details, please provide the permissions on the egit-src directory and any enlightenment related subdirectories.
Sorry, I nuked distfile.old a couple of days ago. I'm running on an SSD and space is kinda a t a premium. For what it's worth, I had a VERY limiting umask set (007), so I suspect the scp of the original distfiles from my old machine lost the 'other' permissions. I'm fine if this bug is closed. It was definitely something screwy on my side, and not a bug, so there's nothing to fix. thanks for the help though. I wouldn't have had a clue where to go digging in the file system to sort this out.
Thanks for your reply, so i will close this bug as invalid.
