Package: mixmaster Version: 3.0.0-6 Severity: minor Dear Maintainer,
the proxy one of my mixmaster installations uses became unavailble for a short time, by coincide the time cron.daily and therefore mixmaster-update were running: | /etc/cron.daily/mixmaster: | /usr/bin/mixmaster-update: Get failed for http://www.noreply.org/echolot/rlist2.txt (504 Gateway Time-out) | Exiting eval via next at /usr/bin/mixmaster-update line 384. | /usr/bin/mixmaster-update: Get failed for http://www.noreply.org/echolot/mlist2.txt (504 Gateway Time-out) | Exiting eval via next at /usr/bin/mixmaster-update line 384. | (...) | Downloading of mlist and/or mixring failed (do you need a proxy?). Aborting. | run-parts: /etc/cron.daily/mixmaster exited with return code 255 The "Get failed" are a sound error message, the "Exiting eval via next" however signal a programming error. The impact is probably neglectable since mixmaster-update cannot do its work anyway. Christoph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
