builds from new PPAs fail due to chrootwait

Steveire is a new PPA contributor. This is his first package. https://edge.launchpad.net/~steveire/+archive

However, each of the builds for this package (xine-lib) fail, as:
Err http://ppa.launchpad.net gutsy/main Packages
  404 Not Found

This appears to be vaguely transient - if the build is given back hours later, it eventually works.

From #launchpad earlier:
[22:54] <Hobbsee> cprov: the chroot waits for hte first package on any ppa
[22:55] <Hobbsee> cprov: as in: user activates ppa, user uploads package, package gets stuck in chroot problem, enosolution, go bug cprov.
[22:56] <cprov> Hobbsee: chroot wait have to be retried manually, atm
[22:56] <Hobbsee> cprov: sure, but the problem isn't that the chroot waits need to be retried, it's that they occur in the first place.
[22:57] <Hobbsee> cprov: it's because ppa is attempting to check the packages in the new person's ppa, which doesn't exist, so gets back a 404, and dies with a chroot error.
[22:59] <cprov> Hobbsee: fine, but we do recognized missing/broken archive as chroot-wait. File a bug about this situation, I will discuss a solution with Adam.
[23:00] <Hobbsee> cprov: right, OK. i assume that either a) you should just create an empty packages.gz file when the ppa gets activated (probably the better solution), or b) special case the ppa line check.
[23:01] <cprov> Hobbsee: it's a race condition between publication & build, we will sort it out.
[23:01] <Hobbsee> ok