Your message dated Sun, 27 Nov 2011 12:50:55 +0100
with message-id <[email protected]>
and subject line closing
has caused the Debian Bug report #650010,
regarding 8dc22d7e17a309dadcf1f2becd7e663def4cea84 is problematic
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.)
--
650010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650010
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: piuparts
version: 0.42~
Hi,
commit 8dc22d7e17a309dadcf1f2becd7e663def4cea84
Author: Andreas Beckmann <[email protected]>
Date: Mon Nov 21 01:25:54 2011 +0100
check tarball age regularily
Perform the tarball age check (and eventually recreate the tgz)
every time a section is run.
Until now long running slaves only updated the tarball at startup.
will lead to waste of ressources when the tarball creation fails, cause the
suite is temporarily broken. then, each time a section is run, tarball
creation will be tried and failed. it's better to only retry once a day.
cheers,
Holger
--- End Message ---
--- Begin Message ---
<anbe> h01ger, re #650010: I don't see a problem, there are already two
timeouts: "max-tgz-age": 2592000, "min-tgz-retry-delay": 21600,
<h01ger> anbe, oh, wasnt aware of min-tgz-retry-delay :) 21600 is 6h, which is
sane for sid
<h01ger> cool
--- End Message ---
