Hi, On Mon, May 06, 2013 at 11:22:15AM +0200, Ansgar Burchardt wrote: > 144.32.168.77 - - [06/May/2013:06:43:03 +0000] "GET /buildd-unstable/Release > HTTP/1.1" 200 1419 "-" "Debian APT-HTTP/1.3 (0.9.7.8)" > 193.201.200.200 - - [06/May/2013:07:13:54 +0000] "GET > /buildd-unstable/Release HTTP/1.1" 200 1419 "-" "Debian APT-HTTP/1.3 > (0.9.7.7)" > 140.211.166.78 - - [06/May/2013:07:30:47 +0000] "GET /buildd-unstable/Release > HTTP/1.1" 200 1419 "-" "Debian APT-HTTP/1.3 (0.9.7.8)" > 129.143.160.6 - - [06/May/2013:08:00:01 +0000] "GET /buildd-unstable/Release > HTTP/1.1" 200 1419 "-" "Debian APT-HTTP/1.3 (0.9.7.8)"
I fixed mayer and caballero. They do not use LVM and hence do not use the chroot setup script. As for poulenc and zemlinsky: I've got an automatic apt-get update cron'ed that you see. The setup script will only create a sources.buildd.list which sbuild will use, but will not update the base sources.list in the chroot. This means that updates and manual dist-upgrades by the buildd admins will still show up in your logs. Option 1: Let's break it and the buildd maints have to fix it on their next dist-upgrade. Option 2: Let's rewrite the normal sources.list as well as creating a new one. Opinions? Kind regards Philipp Kern
signature.asc
Description: Digital signature
