| 1 |
Nope, just plain emerge as root. |
| 2 |
|
| 3 |
> On 9/02/2021, at 11:55, Aisha Tammy <gentoo.science@×××××.cc> wrote: |
| 4 |
> |
| 5 |
> Are you installing/building with the ebuild command and then merging with sudo or |
| 6 |
> something similar? |
| 7 |
> That may be one reason something like this is happening. |
| 8 |
> |
| 9 |
> On 2/8/21 5:28 PM, François Bissey wrote: |
| 10 |
>> Hi all, |
| 11 |
>> |
| 12 |
>> I discovered an issue in a couple of packages for which sage-on-gentoo |
| 13 |
>> provides ebuilds. |
| 14 |
>> Some packages install data directly from a tar command. By that I mean |
| 15 |
>> Makefile.am will a line like |
| 16 |
>> cd $(DESTDIR)$(dbdir) && tar xf $(dist_db_DATA) && rm $(dist_db_DATA) |
| 17 |
>> |
| 18 |
>> From a real Makefile at |
| 19 |
>> https://github.com/sagemath/p_group_cohomology/blob/master/present/Makefile.am |
| 20 |
>> |
| 21 |
>> I looks innocuous until you realise it has some funny effects on ownership. |
| 22 |
>> fbissey@moonloop ~ $ ll /usr/share/pGroupCohomology/ |
| 23 |
>> total 1.1M |
| 24 |
>> drwxr-xr-x 270 root root 12K Feb 3 21:55 . |
| 25 |
>> drwxr-xr-x 319 root root 12K Feb 3 21:55 .. |
| 26 |
>> drwxr-xr-x 3 fbissey fbissey 4.0K Feb 9 10:46 64gp1 |
| 27 |
>> drwxr-xr-x 4 fbissey fbissey 4.0K Feb 9 10:46 64gp10 |
| 28 |
>> drwxr-xr-x 4 fbissey fbissey 4.0K Feb 9 10:46 64gp100 |
| 29 |
>> drwxr-xr-x 4 fbissey fbissey 4.0K Feb 9 10:46 64gp101 |
| 30 |
>> drwxr-xr-x 4 fbissey fbissey 4.0K Feb 9 10:46 64gp102 |
| 31 |
>> |
| 32 |
>> the files in the tarball are owned by user/group 1001:1001 |
| 33 |
>> and on my system it is my personal user. |
| 34 |
>> sci-mathematics/singular and that may include the version in the main tree, |
| 35 |
>> would have to check, install its documentation from a tarball as well |
| 36 |
>> fbissey@moonloop ~ $ ll /usr/share/doc/singular-4.1.1_p2-r3/ |
| 37 |
>> total 216K |
| 38 |
>> drwxr-xr-x 3 2345 uucp 4.0K Nov 10 10:49 . |
| 39 |
>> drwxr-xr-x 1361 root root 64K Feb 9 10:39 .. |
| 40 |
>> drwxr-xr-x 2 2345 uucp 128K Nov 10 10:49 html |
| 41 |
>> -rw-r--r-- 1 root root 497 Nov 10 10:48 README.bz2 |
| 42 |
>> -rw-r--r-- 1 root root 517 Nov 10 10:48 README.md.bz2 |
| 43 |
>> -rw-r--r-- 1 root root 585 Nov 10 10:48 README.pkg.bz2 |
| 44 |
>> fbissey@moonloop ~ $ ll /usr/share/doc/singular-4.1.1_p2-r3/html |
| 45 |
>> total 30M |
| 46 |
>> drwxr-xr-x 2 2345 uucp 128K Nov 10 10:49 . |
| 47 |
>> drwxr-xr-x 3 2345 uucp 4.0K Nov 10 10:49 .. |
| 48 |
>> -rwxr-xr-x 1 2345 uucp 915 Feb 14 2018 a_begin.gif |
| 49 |
>> -rwxr-xr-x 1 2345 uucp 909 Feb 14 2018 a_begin_na.gif |
| 50 |
>> -rwxr-xr-x 1 2345 uucp 927 Feb 14 2018 a_document.gif |
| 51 |
>> |
| 52 |
>> I tried to use fowners inside the ebuild, but it only fixes file ownership, |
| 53 |
>> folders are not touched. I tried to insert “—no-same-owner” in the call to tar |
| 54 |
>> and that didn’t really help either. At best, I am expecting ownership to change |
| 55 |
>> to portage:portage. |
| 56 |
>> |
| 57 |
>> Has anyone dealt with something like this before? Apart from “recursively” |
| 58 |
>> scripting install in the make file is there anything simple I could do? |
| 59 |
>> |
| 60 |
>> Cheers, |
| 61 |
>> François |
| 62 |
> |
| 63 |
> |
Archives