P-a-s broken: yaboot built on !powerpc

Bug #68457 reported by Colin Watson
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Undecided
Unassigned

Bug Description

https://launchpad.net/+builds/+build/231049 shows a yaboot build on i386, but P-a-s says:

yaboot: powerpc # PowerPC

(This has been in P-a-s since October 2000.)

Tags: lp-soyuz
Revision history for this message
Christian Reis (kiko) wrote :

This is actually a build that was created back in July. The way the build system works is that the queue builder creates Build objects for source packages that haven't been built for a certain distribution release. If that build fails it is left in FAILED state but it can be retried later; this is the case for the build of yaboot you've brought up:

Date recorded:
2006-07-25 12:43:42 UTC
Date built:
2006-10-22 16:17:23 UTC

The date built might be best labeled "Date last built", as it's the date we last tried to build the package for edgy.

Interestingly enough, this will never happen again for feisty. The reason is that builds are for a specific distribution release, and when we initialized feisty, the packages in edgy that had not yet built will get completely new build records created. Because the queue builder code now respects P-a-s properly, the bogus builds will not be created again, and everything will work as desired.

Changed in soyuz:
status: Unconfirmed → Rejected
Revision history for this message
Christian Reis (kiko) wrote :

That had not yet built successfully in edgy, I meant. Essentially, feisty will not have build records for the invalid architectures, and therefore we will never attempt to do builds for them.

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.