Bug#749706: gummiboot: fails to install if /etc/machine-id is missing

2014-05-29 Thread Holger Levsen 
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


cheers,
Holger
Start: 2014-05-26 01:10:26 UTC

Package: gummiboot
Version: 44-1
Installed-Size: 118
Maintainer: Julian Andres Klode j...@debian.org
Architecture: amd64
Depends: libblkid1 (= 2.17.2), libc6 (= 2.14)
Recommends: systemd
Description: Simple UEFI bootloader
Multi-Arch: foreign
Homepage: http://freedesktop.org/wiki/Software/gummiboot/
Description-md5: 0eb68a39d2e8ea71909029c314883129
Section: admin
Priority: optional
Filename: pool/main/g/gummiboot/gummiboot_44-1_amd64.deb
Size: 44326
MD5sum: 25d73e04213f473fce7b4f491fe5aa70
SHA1: 8dee5183358f08c942b34fb3e1ee09f553ef47e6
SHA256: a73fa50d196a95aeea9244f879d278d1e1a0368d5ac06dff475cbff53616ebc7

Executing: sudo env PYTHONPATH=/srv/piuparts.debian.org/lib/python2.7/dist-packages timeout -s INT -k 5m 35m /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --scriptsdir /etc/piuparts/scripts-leftovers --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/sid_amd64.tar.gz -d sid --no-upgrade-test --apt gummiboot=44-1
0m0.0s INFO: --
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: The FAQ also explains how to contact us in case you think piuparts is wrong.
0m0.0s INFO: --
0m0.0s INFO: piuparts version 0.59~201405251745~0.58-51-g40e02a6 starting up.
0m0.0s INFO: Command line arguments: /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --scriptsdir /etc/piuparts/scripts-leftovers --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/sid_amd64.tar.gz -d sid --no-upgrade-test --apt gummiboot=44-1
0m0.0s INFO: Running on: Linux piu-slave-bm-a 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u1 x86_64
0m0.0s DEBUG: Created temporary directory /srv/piuparts.debian.org/tmp/tmpQ7SiKX
0m0.0s DEBUG: Unpacking /srv/piuparts.debian.org/slave/basetgz/sid_amd64.tar.gz into /srv/piuparts.debian.org/tmp/tmpQ7SiKX
0m0.0s DEBUG: Starting command: ['tar', '-C', '/srv/piuparts.debian.org/tmp/tmpQ7SiKX', '-zxf', '/srv/piuparts.debian.org/slave/basetgz/sid_amd64.tar.gz']
0m1.8s DEBUG: Command ok: ['tar', '-C', '/srv/piuparts.debian.org/tmp/tmpQ7SiKX', '-zxf', '/srv/piuparts.debian.org/slave/basetgz/sid_amd64.tar.gz']
0m1.8s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmpQ7SiKX', 'mount', '-t', 'proc', 'proc', '/proc']
0m1.8s DEBUG: Command ok: ['chroot', '/srv/piuparts.debian.org/tmp/tmpQ7SiKX', 'mount', '-t', 'proc', 'proc', '/proc']
0m1.8s DEBUG: sources.list:
  deb http://mirror.bm.debian.org/debian/ sid main
0m1.8s DEBUG: Created policy-rc.d and chmodded it.
0m1.8s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmpQ7SiKX', 'apt-get', 'update']
0m7.0s DUMP: 
  Get:1 http://mirror.bm.debian.org sid InRelease [206 kB]
  Get:2 http://mirror.bm.debian.org sid/main amd64 Packages [6757 kB]
  Get:3 http://mirror.bm.debian.org sid/main Translation-en [4602 kB]
  Fetched 11.6 MB in 2s (3870 kB/s)
  Reading package lists...
0m7.0s DEBUG: Command ok: ['chroot', '/srv/piuparts.debian.org/tmp/tmpQ7SiKX', 'apt-get', 'update']
0m7.0s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmpQ7SiKX', 'apt-get', '-yf', 'dist-upgrade']
0m7.9s DUMP: 
  Reading package lists...
  Building dependency tree...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0m7.9s DEBUG: Command ok: ['chroot', '/srv/piuparts.debian.org/tmp/tmpQ7SiKX', 'apt-get', '-yf', 'dist-upgrade']
0m7.9s DEBUG: Copying scriptsdir /etc/piuparts/scripts to /srv/piuparts.debian.org/tmp/tmpQ7SiKX/tmp/scripts/
0m7.9s DEBUG: Copying scriptsdir /etc/piuparts/scripts-leftovers to /srv/piuparts.debian.org/tmp/tmpQ7SiKX/tmp/scripts/
0m7.9s INFO: Running scripts

Bug#749706: gummiboot: fails to install if /etc/machine-id is missing

2014-05-29 Thread Julian Andres Klode 
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.


pgpEI9vpNfGlS.pgp
Description: PGP signature

Bug#749706: gummiboot: fails to install if /etc/machine-id is missing

2014-05-29 Thread Holger Levsen 
Hi,

On Donnerstag, 29. Mai 2014, Julian Andres Klode wrote:
 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.

d.) (there is no other way to) deal with the absence gracefully?
 
 (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.

:-/

Your postinst could also copy /var/lib/dbus/machine-id to /etc but I'm not 
sure that would be right/appropriate.


cheers, 
Holger




signature.asc
Description: This is a digitally signed message part.