| 1 |
On 10/02/2014 16:05, Stroller wrote: |
| 2 |
> Hello all, |
| 3 |
> |
| 4 |
> I'm a little bit rusty, but my recollection is that I should be able to perform `eix-sync` (or `emerge --sync`?) as a user to synchronise my local copy of the portage tree with Gentoo's master portage tree. |
| 5 |
> |
| 6 |
> User is in the portage group: |
| 7 |
> |
| 8 |
> $ whoami |
| 9 |
> stroller |
| 10 |
> $ groups stroller |
| 11 |
> wheel audio video portage cron users |
| 12 |
> $ |
| 13 |
> |
| 14 |
> Yet I get these permissons denied errors: |
| 15 |
> |
| 16 |
> $ eix-sync |
| 17 |
> * Running emerge --sync |
| 18 |
>>>> Synchronization of repository 'gentoo' located in '/usr/portage'... |
| 19 |
>>>> Starting rsync with rsync://91.186.30.235/gentoo-portage... |
| 20 |
>>>> Checking server timestamp … |
| 21 |
> … |
| 22 |
> receiving incremental file list |
| 23 |
> rsync: delete_file: unlink(app-accessibility/caribou/caribou-0.4.12.ebuild) failed: Permission denied (13) |
| 24 |
> rsync: delete_file: unlink(app-accessibility/emacspeak/files/emacspeak-33.0-respect-ldflags.patch) failed: Permission denied (13) |
| 25 |
> rsync: delete_file: unlink(app-accessibility/emacspeak/files/emacspeak-33.0-greader-garbage.patch) failed: Permission denied (13) |
| 26 |
> |
| 27 |
> (full output attached) |
| 28 |
> |
| 29 |
> |
| 30 |
> Googling the problem I see a bunch of Gentoo Forums posts talking about changing at random the permissions of /var/tmp/ or /var/tmp/portage/, but no rationale is given, and I don't think this is the cause: |
| 31 |
> |
| 32 |
> $ emerge --info | grep -i tmpdir |
| 33 |
> PORTAGE_TMPDIR="/var/tmp" |
| 34 |
> $ ls -ld /var/tmp/ |
| 35 |
> drwxrwxrwt 3 root root 4096 Feb 5 13:47 /var/tmp/ |
| 36 |
> $ ls -ld /var/tmp/portage/ |
| 37 |
> drwxrwxr-x 5 portage portage 4096 Feb 5 12:32 /var/tmp/portage/ |
| 38 |
> $ |
| 39 |
> |
| 40 |
> |
| 41 |
> More likely seems to be the permissions of /usr/portage/: |
| 42 |
> |
| 43 |
> $ ls -ld /usr/portage/ |
| 44 |
> drwxr-xr-x 167 portage portage 4096 Jan 5 02:31 /usr/portage/ |
| 45 |
> $ ls -ld /usr/portage/app-accessibility/caribou/caribou*.ebuild |
| 46 |
> -rw-r--r-- 1 portage portage 2432 Aug 25 23:11 /usr/portage/app-accessibility/caribou/caribou-0.4.12.ebuild |
| 47 |
> -rw-r--r-- 1 portage portage 2431 Dec 8 18:01 /usr/portage/app-accessibility/caribou/caribou-0.4.13.ebuild |
| 48 |
> $ |
| 49 |
> |
| 50 |
> This would seem to allow portage itself to synchronise the Portage tree, but not members of the portage group. |
| 51 |
> |
| 52 |
> |
| 53 |
> I am able to run `emerge --sync` as root, but it doesn't solve the solve the problem - next time I run `eix-sync` as user, I'm permissions denied, again. |
| 54 |
> |
| 55 |
> Shouldn't a sync reset the permissions of the portage tree to be correct? |
| 56 |
> |
| 57 |
> |
| 58 |
> `emerge --info | grep -i feature` shows that FEATURES="userfetch userpriv usersandbox usersync" (and some others - see attached) are set. |
| 59 |
> |
| 60 |
> I can reproduce this on a second AMD64 machine, both are running portage-2.2.7. |
| 61 |
> |
| 62 |
> Thanks in advance for any help, advice or suggestions you can offer, |
| 63 |
|
| 64 |
This should work:- |
| 65 |
|
| 66 |
PORTAGE_RSYNC_EXTRA_OPTS="--chmod=g+w" |
| 67 |
|
| 68 |
--Kerin |
Archives