recipes attempt to build packages with version older than previous build
Bug #931131 reported by
Jelmer Vernooij
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Launchpad should be able to see that a recipe build it's going to fire off will have a version string that's older than that of the last build; it shouldn't even start the build and print a clear error rather than fail confusingly during the upload.
It could also clearly indicate that the next recipe build will have a too old version number on the recipe page.
This is related to bug 670474
summary: |
- attempts to build packages with version older than previous build + recipes attempt to build packages with version older than previous build |
Changed in launchpad: | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
importance: | High → Low |
To post a comment you must log in.
Fixing this will also fix some annoying issues that come up when a user requests a build for a recipe daily. We often end up building the package twice, with the second build triggered by the recipe cron job. This second build will fail to upload, because a package with the same version string already exists.