Bug#843251: udev i386 232-14 did not fix it.

[Ola Dunk]

Dear Maintainer, sorry to report that udev i386 232-14 did not fix it.

Upgrade from udev 232-10 to 232-13 left my test system not bootable.
Downgrade was reuired.

Attempt with 232-14 did fail.

Log ->

 Setting up udev (232-14) ...
addgroup: The group `input' already exists as a system group. Exiting.
Job for systemd-udevd.service failed because a timeout was exceeded.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for
details.
invoke-rc.d: initscript udev, action "restart" failed.
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static;
vendor preset: enabled)
   Active: activating (start) since Tue 2017-01-24 10:43:22 UTC; 14ms ago
     Docs: man:systemd-udevd.service(8)
           man:udev(7)
 Main PID: 4751 ((md-udevd))
    Tasks: 1
   CGroup: /system.slice/systemd-udevd.service
           └─4751 (md-udevd)

Jan 24 10:43:22 unassigned-hostname systemd[1]: Starting udev Kernel Device
....
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (231-4) ...
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
 udev
E: Sub-process /usr/bin/dpkg returned an error code (1)
root at unassigned-hostname:/home/datb# /etc/init.d/udev restart
[....] Restarting udev (via systemctl): udev.serviceJob for
systemd-udevd.service failed because a timeout was exceeded.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for
details.
 failed!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170124/8deb2e0f/attachment.html>