Yes, it seems /etc/group is hard-copied from the host system (hash is
identical).
(stonking-test)root@canonical:/tmp# dpkg-statoverride --list
root _chrony 640 /etc/chrony/chrony.keys
root crontab 2755 /usr/bin/crontab
_chrony _chrony 750 /var/lib/chrony
root messagebus 4754 /usr/lib/dbus-1.0/dbus-daemon-launch-helper
_chrony _chrony 750 /var/log/chrony
so during debootstrap chrony is installed and creates the _chrony group
(chrony.postinst), and then sets up the dpkg-statoverride.
when schroot is blindly copying/overriding the groups of the
"container", dpkg is unhappy about the missing group.
as i see it this is a bug in schroot, not in chrony.
** Also affects: schroot (Ubuntu)
Importance: Undecided
Status: New
** Changed in: chrony (Ubuntu)
Status: Triaged => Invalid
** Summary changed:
- unknown system group '_chrony' in statoverride file; the system group got
removed
+ schroot overrides /etc/groups, corrupts dpkg-statoverride from chrony
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2156084
Title:
schroot overrides /etc/groups, corrupts dpkg-statoverride from chrony
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2156084/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
