Bug#842057: [buildd-tools-devel] Bug#842057: fixed in sbuild 0.72.0-2

2016-12-02 Thread Johannes Schauer 
Hi,

Quoting Gianfranco Costamagna (2016-12-02 12:25:21)
> >to figure out the reason for this problem, could you give me the content of
> 
> >your /var/lib/buildd/daemon.log?
> 
> distribution list is empty, aborting. at /usr/share/perl5/Buildd/Daemon.pm
> line 95.

maybe somebody with buildd knowledge can comment on this? Aurélien?

This is the same error I'm getting over here. I'd expect this to happen because
the default /etc/buildd/buildd.conf does not set anything for "$distributions".
The questions are:

 - should the buildd package automatically start the buildd service (and fail)?
 - should there be a default value for the DISTRIBUTIONS configuration variable
   such that buildd does not fail when initially started?

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#842057: [buildd-tools-devel] Bug#842057: fixed in sbuild 0.72.0-2

2016-12-02 Thread Gianfranco Costamagna 
Hi,

>to figure out the reason for this problem, could you give me the content of

>your /var/lib/buildd/daemon.log?



distribution list is empty, aborting. at /usr/share/perl5/Buildd/Daemon.pm line 
95.

thanks,

G.

Bug#842057: [buildd-tools-devel] Bug#842057: fixed in sbuild 0.72.0-2

2016-12-01 Thread Johannes Schauer 
Hi,

Quoting Gianfranco Costamagna (2016-11-22 15:11:36)
> there still seems to be some regression, because apt can't finish its job
> 
> You can see the execstart fail here 
> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/sbuild/20161122_123905_6a3eb@/log.gz
> 
> Setting up libsbuild-perl (0.72.0-2ubuntu1) ...
> Setting up sbuild (0.72.0-2ubuntu1) ...
> ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
> (cannot open shared object file): ignored.
> Setting up buildd (0.72.0-2ubuntu1) ...
> ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
> (cannot open shared object file): ignored.
> Job for buildd.service failed because the control process exited with error 
> code.
> See "systemctl status buildd.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript buildd, action "start" failed.
> ● buildd.service - LSB: Debian package autobuilder daemon
>Loaded: loaded (/etc/init.d/buildd; generated; vendor preset: enabled)
>Active: failed (Result: exit-code) since Tue 2016-11-22 
> 12:38:48 UTC; 12ms ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 4794 ExecStart=/etc/init.d/buildd start (code=exited, 
> status=2)
>   CPU: 301ms
> 
> Nov 22 12:38:40 autopkgtest systemd[1]: Starting LSB: Debian package 
> autobui…...
> Nov 22 12:38:40 autopkgtest buildd[4794]:  * Starting Debian package 
> autobui…ldd
> Nov 22 12:38:48 autopkgtest systemd[1]: buildd.service: Control 
> process exit…s=2
> Nov 22 12:38:48 autopkgtest systemd[1]: Failed to start LSB: Debian 
> package …on.
> Nov 22 12:38:48 autopkgtest systemd[1]: buildd.service: Unit entered 
> failed …te.
> Nov 22 12:38:48 autopkgtest systemd[1]: buildd.service: Failed with 
> result '…e'.
> Hint: Some lines were ellipsized, use -l to show in full.
> dpkg: error processing package buildd (--configure):
>  subprocess installed post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of autopkgtest-satdep:
>  autopkgtest-satdep depends on buildd (>= 0~); however:
>   Package buildd is not configured yet.
> 
> dpkg: error processing package autopkgtest-satdep (--configure):
>  dependency problems - leaving unconfigured
> Processing triggers for ureadahead (0.100.0-19) ...
> No apport report written because the error message indicates its a followup 
> error from a previous failure.
> Processing triggers for libc-bin (2.24-3ubuntu1) ...
> Processing triggers for systemd (232-6) ...
> Errors were encountered while processing:
>  buildd
>  autopkgtest-satdep
> E: Sub-process /usr/bin/dpkg returned an error code (1)

to figure out the reason for this problem, could you give me the content of
your /var/lib/buildd/daemon.log?

Thanks!

cheers, josch


signature.asc
Description: signature