| 1 |
On 09/11/2014 01:51 AM, Bertrand Simonnet wrote: |
| 2 |
> Hi everyone, |
| 3 |
> |
| 4 |
> I think there is a bug in the read only detection logic: portage will |
| 5 |
> check the write permission on the system relative to / and not relative |
| 6 |
> to ROOT. |
| 7 |
> |
| 8 |
> I found this when emerging a package with --root=/usr/local on my system |
| 9 |
> with: |
| 10 |
> * / read only |
| 11 |
> * /usr/local read-write |
| 12 |
> |
| 13 |
> Note, the error message was also wrong as it indicated that /usr/local |
| 14 |
> was read only when it actually detected / as read only and prefixed it |
| 15 |
> with ROOT in the message. |
| 16 |
> |
| 17 |
> I attached a patch that fix the detection logic and the error message. |
| 18 |
> |
| 19 |
> Bertrand Simonnet |
| 20 |
|
| 21 |
This is in git, for release in portage-2.2.13: |
| 22 |
|
| 23 |
https://github.com/gentoo/portage/commit/34e3661b76e6c8a95e57c95d78ba673be32cc2b1 |
| 24 |
-- |
| 25 |
Thanks, |
| 26 |
Zac |
Archives