Nathanael Nerode wrote: > So, http://bugs.debian.org/release-critical/other/all.html > and http://packages.qa.debian.org/ > and http://bts.turmzimmer.net/ > all show packages as being in 'testing' which aren't, because they were > removed on the last run. > > Perhaps there's some way to schedule the (apparently daily) update of these > so that it happens shortly *after* the testing scripts run?
I had this problem for my script too, and my solution is to simply poll for new testing run results ever hour and rebuilding the pages when updated data is available. I'm doing it with curl in this way: curl --silent --remote-name --time-cond update_output.txt http://ftp-master.debian.org/testing/update_output.txt -- Björn
