On Thu, May 29, 2014 at 12:14:17PM +0200, Holger Levsen wrote: > Package: gummiboot > Version: 44-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package failed to install. As per > definition of the release team this makes the package too buggy for a > release, thus the severity. > > From the attached log (scroll to the bottom...): > > Selecting previously unselected package gummiboot. > (Reading database ... 8370 files and directories currently installed.) > Preparing to unpack .../gummiboot_44-1_amd64.deb ... > Unpacking gummiboot (44-1) ... > Setting up gummiboot (44-1) ... > cat: /etc/machine-id: No such file or directory > dpkg: error processing package gummiboot (--configure): > subprocess installed post-installation script returned error exit status 1 >
systemd creates this file by running systemd-machine-id-setup in its postinst.
The
thing is: Some people might not want systemd, should I force them to install it?
Three options:
(a) Pre-Depend on systemd
(b) Depend on systemd and run systemd-machine-id-setup in our postinst as well
=> kind of pointless, as systemd's postinst does it as well
(c) Use debconf to warn users if machine-id is not present
=> works with systems that do not have systemd installed.
(a) is the easiest option for me, (b) might be easier for a package manager to
handle, and (c) is just annoying, especially if systemd is installed during the
same apt run. So, if there are no other options, I'd go and pre-depend on
systemd.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Please do not top-post if possible.
pgpLb3iyqivdG.pgp
Description: PGP signature
