Package: distcc
Version: 3.1-6.3
Severity: normal
Dear Maintainer,
When I upgraded to 3.1-6.3, apt-get failed with the following error
message, thus interrupting the upgrade and blocking the upgrade of many
packages.
$ apt-get install distcc
[...]
Setting up distcc (3.1-6.3) ...
Updating symlinks in /usr/lib/distcc ...
Job for distcc.service failed because the control process exited with error
code.
See "systemctl status distcc.service" and "journalctl -xe" for details.
invoke-rc.d: initscript distcc, action "start" failed.
* distcc.service - LSB: simple distributed compiler server
Loaded: loaded (/etc/init.d/distcc; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2017-11-06 18:47:31 CET; 4ms ago
Docs: man:systemd-sysv-generator(8)
Process: 10779 ExecStart=/etc/init.d/distcc start (code=exited, status=101)
Nov 06 18:47:31 amboise distcc[10779]: Starting Distributed Compiler Daemon:
distccd/etc/init.d/distcc: start failed with error code 101 ... (warning).
Nov 06 18:47:31 amboise distcc[10779]: failed!
Nov 06 18:47:31 amboise systemd[1]: distcc.service: Control process exited,
code=exited status=101
Nov 06 18:47:31 amboise systemd[1]: distcc.service: Failed with result
'exit-code'.
Nov 06 18:47:31 amboise systemd[1]: Failed to start LSB: simple distributed
compiler server.
dpkg: error processing package distcc (--configure):
installed distcc package post-installation script subprocess returned error
exit status 1
Processing triggers for systemd (235-2) ...
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
distcc
E: Sub-process /usr/bin/dpkg returned an error code (1)
The reason for this error is that my /etc/default/distcc file has the
following line:
ZEROCONF="true"
Removing that line fixed the issue.
As far as I can tell the distcc package was compiled without support
for zeroconf but no step was taken to warn the user (e.g. with a
debconf message), update the configuration file, and ensure a smooth
upgrade.
Given that this release was a non-maintainer upgrade maybe the loss of
zeroconf support was unintentional. If so fixing the issue is probably a
'simple matter' of adding a missing Build-Depends.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages distcc depends on:
ii adduser 3.116
ii debconf [debconf-2.0] 1.5.64
ii libc6 2.24-17
ii libpopt0 1.16-10+b2
ii lsb-base 9.20170808
ii netbase 5.4
distcc recommends no packages.
Versions of packages distcc suggests:
ii ccache 3.3.4-1
ii dbus 1.12.0-1
pn distcc-pump <none>
ii distccmon-gnome 3.1-6.3
pn dmucs <none>
-- debconf information:
distcc/daemon-nice: 10
distcc/daemon-listen: 192.168.12.250
distcc/daemon: true
distcc/daemon-jobs:
distcc/daemon-zeroconf: true
distcc/daemon-allow: 192.168.12.250/32 192.168.12.128/25 192.168.12.64/26
