| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Paweł Madej wrote: |
| 5 |
| Zac Medico wrote: |
| 6 |
|>> You should have done `ls -ld /usr/portage/distfiles/.locks`. |
| 7 |
|>> |
| 8 |
|>> I'm able to reproduce that problem here. It seems that portage |
| 9 |
|>> automatically changes the group id on ${DISTDIR} (when run as root) but |
| 10 |
|>> it neglects to change the group id on ${DISTDIR}/.locks (I'd consider it |
| 11 |
|>> a bug). If you do `chgrp portage /usr/portage/distfiles/.locks && chmod |
| 12 |
|>> g+w /usr/portage/distfiles/.locks` then that should allow you to work |
| 13 |
|>> around the problem. |
| 14 |
|>> |
| 15 |
|>> Zac |
| 16 |
| |
| 17 |
| Thank you very much Zac. That resolved a problem. I think if I should |
| 18 |
| file a bug about this? |
| 19 |
| |
| 20 |
|
| 21 |
Yeah, I think should. The version of portage that I'm using (2.1_pre3) will create the directory with the correct gid (if the directory does not exist). However, after the directory has been created, portage does not ensure that .locks continues to have the correct gid. |
| 22 |
|
| 23 |
Zac |
| 24 |
-----BEGIN PGP SIGNATURE----- |
| 25 |
Version: GnuPG v1.4.2 (GNU/Linux) |
| 26 |
|
| 27 |
iD8DBQFDvCt2/ejvha5XGaMRAgXSAJ0REINi8BZ9sUHi/RSIUDLFVErgHQCeIaCc |
| 28 |
ICVFMzigOEXKOPI2mQIVkkc= |
| 29 |
=9gg1 |
| 30 |
-----END PGP SIGNATURE----- |
| 31 |
-- |
| 32 |
gentoo-user@g.o mailing list |
Archives