First build in a new PPA fails

Bug #196782 reported by James Westby
8
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Celso Providelo

Bug Description

Hi,

I was told that a bug might already be reported for this,
but I could not find it. My apologies if this is a duplicate.

I just uploaded the first package to my PPA, and it failed
to build, ending in the CHROOTWAIT state. Inspecting
the log showed that it failed to build as it tried to download
the Packages.gz from the PPA, which didn't exist as nothing
had been built yet.

I restarted the build and it worked the second time, thanks
for the people in #launchpad for pointin me to this.

Thanks,

James

Tags: lp-soyuz ppa
Revision history for this message
Celso Providelo (cprov) wrote :

I wonder if "ppa-is-too-fast" would be an accurate nickname for this bug :)

Changed in soyuz:
importance: Undecided → Low
milestone: none → 1.2.4
status: New → Triaged
Revision history for this message
Artem Popov (artfwo) wrote :

The workaround worked, thanks for pointing this out!

Changed in soyuz:
milestone: 1.2.4 → none
Revision history for this message
Christian Reis (kiko) wrote :

Perhaps we could fix this by not sending the PPA apt sources line to the buildd until the PPA has any binaries published in it. After all, no use getting apt all excited about the PPA if there's nothing to fetch from it.

Changed in soyuz:
milestone: none → 1.2.5
Celso Providelo (cprov)
Changed in soyuz:
assignee: nobody → cprov
importance: Low → Medium
milestone: 1.2.5 → 1.2.4
status: Triaged → In Progress
Revision history for this message
Celso Providelo (cprov) wrote :

RF 6147

Changed in soyuz:
status: In Progress → Fix Committed
Celso Providelo (cprov)
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.