| 1 |
On 12/31/20 12:33 AM, Jack wrote: |
| 2 |
> On 2020.12.30 17:17, n952162 wrote: |
| 3 |
>> When I try to restore my pkgs, after the --depclean, the emerge fails. |
| 4 |
>> It seems like there's an error in the pre-inst script of acct-group/lp? |
| 5 |
>> That's need by cups: |
| 6 |
>> |
| 7 |
>> 1270~/adm/gentoo/emerged>sudo cat |
| 8 |
>> /var/tmp/portage/acct-group/lp-0-r1/temp/build.log |
| 9 |
>> * Package: acct-group/lp-0-r1 |
| 10 |
>> * Repository: gentoo |
| 11 |
>> * Maintainer: systemd@g.o printing@g.o |
| 12 |
>> * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU |
| 13 |
>> * FEATURES: network-sandbox preserve-libs sandbox userpriv |
| 14 |
>> usersandbox |
| 15 |
>> >>> Unpacking source... |
| 16 |
>> >>> Source unpacked in /var/tmp/portage/acct-group/lp-0-r1/work |
| 17 |
>> >>> Preparing source in /var/tmp/portage/acct-group/lp-0-r1/work ... |
| 18 |
>> >>> Source prepared. |
| 19 |
>> >>> Configuring source in /var/tmp/portage/acct-group/lp-0-r1/work ... |
| 20 |
>> >>> Source configured. |
| 21 |
>> >>> Compiling source in /var/tmp/portage/acct-group/lp-0-r1/work ... |
| 22 |
>> >>> Source compiled. |
| 23 |
>> >>> Test phase [not enabled]: acct-group/lp-0-r1 |
| 24 |
>> |
| 25 |
>> >>> Install acct-group/lp-0-r1 into |
| 26 |
>> /var/tmp/portage/acct-group/lp-0-r1/image |
| 27 |
>> >>> Completed installing acct-group/lp-0-r1 into |
| 28 |
>> /var/tmp/portage/acct-group/lp-0-r1/image |
| 29 |
>> |
| 30 |
>> * Final size of build directory: 4 KiB |
| 31 |
>> * Final size of installed tree: 20 KiB |
| 32 |
>> |
| 33 |
>> * checking 1 files for package collisions |
| 34 |
>> >>> Merging acct-group/lp-0-r1 to / |
| 35 |
>> error writing group entry: Invalid argument |
| 36 |
>> * Adding group 'lp' to your system ... |
| 37 |
>> error writing group entry: Invalid argument |
| 38 |
>> * - Groupid: 7 |
| 39 |
>> groupadd: group 'lp' already exists |
| 40 |
> This seems to be the basic cause. |
| 41 |
|
| 42 |
|
| 43 |
Perhaps. But there are two "invalid argument" error messages before the |
| 44 |
"already exists" msg. |
| 45 |
|
| 46 |
|
| 47 |
> However, I have no idea what that emerge should do if the group it |
| 48 |
> wants to install does already exist. I can re-emerge this package |
| 49 |
> with no problems. |
| 50 |
|
| 51 |
|
| 52 |
That's interesting! Maybe re-emerge would behave differently from a |
| 53 |
de-install/emerge? |
| 54 |
|
| 55 |
In any case though, crashing if the group already exists would be a bug |
| 56 |
the developers should be interested in. |
| 57 |
|
| 58 |
|
| 59 |
> Is this a new install or reinstall? All the logic is in the eclass |
| 60 |
> which does have the comment "Creates the group if it does not exist." |
| 61 |
|
| 62 |
|
| 63 |
I was looking for that ... I didn't find groupadd in |
| 64 |
/var/db/pkg/acct-group/lp-0. Where should I look? |
| 65 |
|
| 66 |
|
| 67 |
> |
| 68 |
> What happens if you just run "emerge -1 acct-group/lp"? |
| 69 |
|
| 70 |
|
| 71 |
Same thing |
| 72 |
|
| 73 |
|
| 74 |
> Have you done a successful "emerge -auDvN @system" ? |
| 75 |
|
| 76 |
|
| 77 |
Yes |
| 78 |
|
| 79 |
|
| 80 |
> There may well be something else required still missing, but not an |
| 81 |
> explicit dependency because it is part of @system. |
| 82 |
> |
| 83 |
> |
| 84 |
|
| 85 |
One thing I just re-discovered is --keep-going, which works, thank |
| 86 |
goodness, so I'll should have a working system (sometime tomorrow!), |
| 87 |
albeit, without cups. |
Archives