On 07/10/08 at 13:02 -0400, Eric Cooper wrote: > On Tue, Oct 07, 2008 at 10:09:44AM +0200, Lucas Nussbaum wrote: > > Is there something special I should do, besides keeping the content of > > /var/log/daemon.log, to help debugging this? > > If you can spare the disk space in /var/log, please include > $debug true > in /etc/approx/approx.conf, and send me the portions of the log > that show the failures (and also any non-default settings in approx.conf) > > I suspect that you're putting approx under more stress than I'm able > to when I do my own testing. Sorry for any inconvenience, and thank > you for your patience.
Hi, I attached a build log with the failure, including /var/log/daemon.log. http://beaujolais.grenoble.grid5000.fr/mirrors/debian/pool/main/x/xorp/xorp_1.5~cvs.20080519-1.dsc does exist. Is it possible that you get an error code from curl (possibly because the system was too loaded) and translate it to 404 even if the error was something else? Or could it be related to: Oct 8 11:12:52 paravent-36 approx: mkdir: File exists (./debian/pool/main/x/xorp) Thank you, -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
xorp.log.gz
Description: Binary data
