FS#56549 - [arch-install-scripts] arch-chroot and unpopulated /etc/passwd, /etc/group

Attached to Project: Arch Linux
Opened by Andreas Baumann (andreas_baumann) - Sunday, 03 December 2017, 08:50 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 03 December 2017, 18:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Commit 41b5633332a4980b6ac9a4c84d802d97799476ee of filesystem removed
all but the root user in passwd,gpasswd,group,gpasswd.

Now if entering the chroot with arch-chroot who takes care those files
are properly populated?

There are cases where it matters, for instance when building
a package inside the chroot like util-linux a group tty must be present
so the files are installed with proper ownership.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 03 December 2017, 18:50 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Sunday, 03 December 2017, 14:07 GMT
If you're building packages, you have base-devel installed. If you have base-devel completely installed, then hooks added by the systemd package take care of creating users/groups.
Comment by Doug Newgard (Scimmia) - Sunday, 03 December 2017, 15:45 GMT
What does arch-install-scripts have to do with building inside a chroot?

This ticket also just seems to be asking questions, do you have an actual problem?
Comment by Andreas Baumann (andreas_baumann) - Sunday, 03 December 2017, 18:31 GMT
arch-chroot is part of this package last time I checked:

pacman -Qo /usr/bin/arch-chroot
/usr/bin/arch-chroot is owned by arch-install-scripts 17-1

shell> arch-chroot /home/cross/i486-root/

chroot-shell> cat /etc/passwd
root:x:0:0::/root:/bin/bash

The problem is, I don't get the proper groups and accounts this
way.
Comment by Dave Reisner (falconindy) - Sunday, 03 December 2017, 18:35 GMT
I don't know why you expect arch-chroot to be responsible for this....
Comment by Andreas Baumann (andreas_baumann) - Sunday, 03 December 2017, 18:40 GMT
...ok, I'll think about another place and way to communicate this..
Comment by Doug Newgard (Scimmia) - Sunday, 03 December 2017, 18:40 GMT
The problem is how you're creating the chroots. That's a local problem, not an Arch problem as far as I can see.
Comment by Andreas Baumann (andreas_baumann) - Sunday, 03 December 2017, 18:45 GMT
Ok, arch-chroot is not for building software, for this you have to use the
devtools (and arch-nspawn is executing systemd-nspawn), then /etc/passwd
and friends get populated, right?
Comment by Doug Newgard (Scimmia) - Sunday, 03 December 2017, 18:49 GMT
That doesn't really matter. I'm more convinced that there is no issue and you're doing something really strange when creating the chroots.

Loading...