654270 – sys-apps/portage-2.31.31 portage fails to add users to ROOT specified in PORTAGE_CONFROOT/etc/portage/make.conf

Bug 654270 - sys-apps/portage-2.31.31 portage fails to add users to ROOT specified in PORTAGE_CONFROOT/etc/portage/make.conf

Summary: sys-apps/portage-2.31.31 portage fails to add users to ROOT specified in PORT...

Status:	RESOLVED DUPLICATE of bug 541406

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All Linux

Importance:	Normal normal
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2018-04-29 02:30 UTC by Joe Harvell
Modified:	2022-04-26 06:20 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
output of sudo armv7a-pip-linux-gnueabi-emerge --info (pip-emerge-info.txt,4.72 KB, text/plain) 2018-04-29 02:30 UTC, Joe Harvell	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Joe Harvell 2018-04-29 02:30:54 UTC

Created attachment 528746 [details]
output of sudo armv7a-pip-linux-gnueabi-emerge --info

When I install packages with cross-emerge and the package adds a new user to the ROOT specified in $PORTAGE_CONFROOT.

For example, I run:

sudo armv7a-pip-linux-gnueabi-emerge -a1v sys-apps/systemd

The package installs successfully in /usr/armv7a-pip-linux-gnueabi.  However etc/passwd, etc/group and etc/shadow in /usr/armv7a-pip-linux-gnueabi are not modified to contain the various users and groups systemd normally adds.

I have to add them manually.

Comment 1 Sam James archtester

2022-04-26 06:20:50 UTC

I think this is pretty much handled by bug 541406 which is now fixed.

*** This bug has been marked as a duplicate of bug 541406 ***