Re: [gentoo-proxy-maint] Repoman: Need user access

[Vieri <rentorbuy@yahoo.com>]

On Wednesday, December 12, 2018, 2:56:39 PM GMT+1, Sarah White <kuzetsa@gmail.com> wrote: 
>
> This is the correct workaround. The problem goes away any time I've
> experienced it by making sure my non-root user is member of the portage
> user group, and verifying permissions on DISTDIR (typically
> /usr/portage/distfiles) - the most I've ever had to do was re-log or
> reboot after checking those settings.

I'll try to add my user to the portage group.
Before doing so, I also tried to run "emerge --sync" as root, but running repoman as the user still yields the same message.
I was kind of hoping not to touch the user's groups especially since it's a pam-winbind authenticated user.
Anyway, as I apparently have no choice I did:

# usermod -a -G portage my_user
# groups my_user
portage domain users

Now I get this:

 $ repoman manifest
*** the local copy of metadata.xsd needs to be refetched, doing that now
--2018-12-12 15:54:01--  https://www.gentoo.org/xml-schema/metadata.xsd
[snip]
2018-12-12 15:54:02 (109 MB/s) - '/usr/portage/distfiles/metadata.xsd.c_zl6in2' saved [18186/18186]

>>> Creating Manifest for blabla

I'm not 100% sure, but the file doesn't seem to have changed (at least based on the timestamp).

To sum it all up:

1) is it safe/common practice to add the user to the portage group?
2) can 1) be avoided by running repoman as root just once and only when this type of error shows up?

Thanks,

Vieri