daily built recipes may error if a manual build has been done
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
Recipe build at https:/
Regardless of how it got initiated, it still shouldn't have built a package at all since there were no code changes to the associated branch. Since I use the bzr revno in the package title (and no date) it failed when trying to upload the package since I have a package for the revision already. But at the very least it should've failed before building while checking for branch changes.
Solutions
=========
* Put a timestamp as well as the revision in the debversion
Changed in launchpad-code: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in launchpad: | |
importance: | Medium → High |
summary: |
- Recipe built duplicate package + daily built recipes may error if a manual build has been done |
description: | updated |
tags: | added: recipe |
This was kicked off by the daily build.
Yes we are in the process of changing how to determine whether to build or not. We are moving to manifests.