Your message dated Thu, 14 Jun 2012 23:52:45 +0200
with message-id <[email protected]>
and subject line Re: Bug#654419: piuparts-master should not fail on network
errors
has caused the Debian Bug report #654419,
regarding piuparts-master should not fail on network errors
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.)
--
654419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654419
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: piuparts
Version: 0.42
Severity: normal
piuparts-master failures cause piuparts-slave to die. This is probably
fine for "serious errors", but nasty for transient network errors
(failing to resolve the mirror host or downloading the packages file)
where the slave could just switch to the next section (and finally go to
sleep if nothing is to do).
I see two possible solutions:
* catch the error and initialize an "empty" packages list (accept logs
from the slave, but don't issue packages to be checked)
* instead of 'hello' return 'initialization failed' (or something else)
and let the slave skip this master
Andreas
--- End Message ---
--- Begin Message ---
Version: 0.44
On 2012-01-03 17:52, Holger Levsen wrote:
>> * instead of 'hello' return 'initialization failed' (or something else)
>> and let the slave skip this master
> I prefer option 2.
since 0.44 the slave will skip a section if communication with the
master failed.
Andreas
--- End Message ---
