This got fixed in xenial, so closing: Setting up udev (229-4ubuntu4) ... addgroup: The group `input' already exists as a system group. Exiting. A chroot environment has been detected, udev not started.
I confirm the issue for trusty. However, if you want to work with chroots you really need to create a policy-rc.d to disable starting of services. If you don't, then pretty well any package that tries to start a service will actually do/attempt so, which is often failing and usually undesirable in such chroots. mk-sbuild and similar tools create this automatically, but the simplest form is /usr/sbin/policy-rc.d: #!/bin/sh exit 101 See man invoke-rc.d and https://people.debian.org/~hmh/invokerc.d-policyrc.d-specification.txt ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Trusty) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1571569 Title: Cannot upgrade udev in the debootstrapped environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1571569/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
