Your message dated Thu, 24 Dec 2015 11:45:58 +0100
with message-id <20151224104558.4674.79824@localhost>
and subject line Re: Bug#554953: buildd: Fails to upgrade, doesn't work.
has caused the Debian Bug report #554953,
regarding buildd: Fails to upgrade, doesn't work.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
554953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554953
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: buildd
Version: 0.59.0-1
Severity: serious
Hi,
When upgrading buildd on one of the buildds I get:
Setting up buildd (0.59.0-1) ...
Installing new version of config file /etc/cron.d/buildd ...
Starting Debian package autobuilder: builddE:
/home/buildd/.builddrc: Errors found in configuration file:
Global symbol "$sshcmd" requires explicit package name at (eval 7)
line 35.
Global symbol "$wanna_build_user" requires explicit package name
at (eval 7) line 38.
Global symbol "$wanna_build_dbbase" requires explicit package name
at (eval 7) line 39.
invoke-rc.d: initscript buildd, action "start" failed.
dpkg: error processing buildd (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
buildd
E: Sub-process /usr/bin/dpkg returned an error code (1)
I removed the config file, and then it started, but end up with:
buildd 14095 0.0 0.1 98952 8336 ? S 12:21 0:00 /usr/bin/perl
/usr/bin/buildd
buildd 14096 0.0 0.1 98952 8416 ? Ss 12:21 0:00 /usr/bin/perl
/usr/bin/buildd
And the log file shows:
Nov 7 12:21:17 buildd[14089]: Daemon started. (pid=14096)
Nov 7 12:21:17 buildd[14089]: Nothing to do -- sleeping 300 seconds
Notice that it has the pid wrong.
Looking at /etc/buildd/buildd.conf, I see:
# database used for wanna-build
#$wanna_build_db = "arch/build-db";
# Database to use for wanna-build.
#$wanna_build_db_name = 'arch/build-db';
Only $wanna_build_db_name seems to be used, and that seems to
work.
The current wanna-build does not need the database name anymore.
It just needs to know the arch. You can pass it with -A $arch.
If that's not used, it falls back to using the arch from database
name.
$wanna_build_user seems to have changed to $wanna_build_db_user.
$sshcmd seems to need to get replaced by $wanna_build_ssh_user.
$sshsocket seems to be renamed to $wanna_build_ssh_socket.
After all that, it seems to start fine, but complain with:
Nov 7 12:53:32 buildd[16668]: take_from_dists is empty, aborting.
at /usr/share/perl5/Buildd/Daemon.pm line 99.
While I have:
@take_from_dists = qw(unstable);
Kurt
--- End Message ---
--- Begin Message ---
Hi,
Quoting Kurt Roeckx (2015-12-24 11:30:51)
> On Thu, Dec 24, 2015 at 01:04:16AM +0100, Johannes Schauer wrote:
> > this bug is six years old and I'm thus wondering if the problem still
> > persists. Could somebody show me how to reproduce it or submit a patch to
> > fix the problem?
>
> I don't think this bug is longer relevant.
thanks for confirming! Closing then.
cheers, josch
signature.asc
Description: signature
--- End Message ---
