Retrying failed builds in later releases
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Undecided
|
Malcolm Cleaton | ||
Bug Description
I've found a difference in behaviour between the old queue builder code and the new. Although this has come about as part of the PAS implementation, it doesn't have anything to do with PAS directly, it's just come out of the way the code has been reorganised.
In the previous code, an arch-all source package which was tried and failed to build on a previous distrorelease would never be built on a later release. An example is tomcat4, which failed to build in dapper, and which also appears (as a source package) in edgy.
The new code doesn't examine the builds in the same way (it has less special handling for arch all) and therefore wants to create a build for this on edgy, as it would create edgy builds for any architectures which failed to build on dapper for any non-arch-all package.
I don't know enough about the requirements here to know if we've introduced a bug or fixed one :). Can somebody enlighten me?
| Changed in soyuz: | |
| assignee: | nobody → malcolmcleaton |
| Colin Watson (cjwatson) wrote | #1 |
| Christian Reis (kiko) wrote | #2 |
| Changed in soyuz: | |
| status: | Unconfirmed → Rejected |
I think you've fixed a bug. There's no harm in retrying builds here for the next release along, and possibly some use in doing so.