| 1 |
On Wednesday, December 12, 2018, 2:56:39 PM GMT+1, Sarah White <kuzetsa@×××××.com> wrote: |
| 2 |
> |
| 3 |
> This is the correct workaround. The problem goes away any time I've |
| 4 |
> experienced it by making sure my non-root user is member of the portage |
| 5 |
> user group, and verifying permissions on DISTDIR (typically |
| 6 |
> /usr/portage/distfiles) - the most I've ever had to do was re-log or |
| 7 |
> reboot after checking those settings. |
| 8 |
|
| 9 |
I'll try to add my user to the portage group. |
| 10 |
Before doing so, I also tried to run "emerge --sync" as root, but running repoman as the user still yields the same message. |
| 11 |
I was kind of hoping not to touch the user's groups especially since it's a pam-winbind authenticated user. |
| 12 |
Anyway, as I apparently have no choice I did: |
| 13 |
|
| 14 |
# usermod -a -G portage my_user |
| 15 |
# groups my_user |
| 16 |
portage domain users |
| 17 |
|
| 18 |
Now I get this: |
| 19 |
|
| 20 |
$ repoman manifest |
| 21 |
*** the local copy of metadata.xsd needs to be refetched, doing that now |
| 22 |
--2018-12-12 15:54:01-- https://www.gentoo.org/xml-schema/metadata.xsd |
| 23 |
[snip] |
| 24 |
2018-12-12 15:54:02 (109 MB/s) - '/usr/portage/distfiles/metadata.xsd.c_zl6in2' saved [18186/18186] |
| 25 |
|
| 26 |
>>> Creating Manifest for blabla |
| 27 |
|
| 28 |
I'm not 100% sure, but the file doesn't seem to have changed (at least based on the timestamp). |
| 29 |
|
| 30 |
To sum it all up: |
| 31 |
|
| 32 |
1) is it safe/common practice to add the user to the portage group? |
| 33 |
2) can 1) be avoided by running repoman as root just once and only when this type of error shows up? |
| 34 |
|
| 35 |
Thanks, |
| 36 |
|
| 37 |
Vieri |
Archives