| 1 |
On 10/02/2014 19:03, Walter Dnes wrote: |
| 2 |
> On Mon, Feb 10, 2014 at 05:09:55PM +0000, Stroller wrote |
| 3 |
>> |
| 4 |
>> On Mon, 10 February 2014, at 4:55 pm, Gleb Klochkov <glebiuskv@×××××.com> wrote: |
| 5 |
>> |
| 6 |
>>> Hi. Try to use sudo with no password for eix-sync. |
| 7 |
>> |
| 8 |
>> I'd really rather not. Thanks, though. |
| 9 |
> |
| 10 |
> Being in group "portage" is not enough. That merely lets you do |
| 11 |
> emerges with "--pretend". "emerge --sync" modifies files in |
| 12 |
> /usr/portage. Files and directories in /usr/portage/ are user:group |
| 13 |
> root:root. Therefore you *NEED* root-level permission to modify them. |
| 14 |
> No ifs/ands/ors/buts. The overall easiest method is to (as root)... |
| 15 |
|
| 16 |
Your are mistaken. The "usersync" FEATURE is a default. You can rename |
| 17 |
your make.conf file and invoke portageq envvar FEATURES to verify this. |
| 18 |
The consequence of this feature being enabled is that portage assumes |
| 19 |
the privileges of the owner of /usr/portage. The entire point of this is |
| 20 |
that portage doesn't have to exec rsync as root. Doing so is both |
| 21 |
needless and dangerous. |
| 22 |
|
| 23 |
Ergo, recursively setting the permissions of /usr/portage to |
| 24 |
portage:portage is actually a really good idea. Indeed, you should find |
| 25 |
that recent portage snapshot tarballs extract in such a way that portage |
| 26 |
is both the owner and associated group. |
| 27 |
|
| 28 |
The problem the OP is having concerns only the file modes, which is a |
| 29 |
separate matter altogether. |
| 30 |
|
| 31 |
--Kerin |
Archives