It would be nice to have bugs-autoclosing working for intermediate revisions non accepted to the archive but included in a new upload
Bug #1170301 reported by
Sebastien Bacher
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
During freeze times it happens that some revisions of a packages are "stacked" in the queue, each closing some bugs, and that only the most recent one is accepted. If the uploader failed to upload the .changes with -v<current_
It would be good to have those bugs closed by the upload.
summary: |
- It would be nice to have bugs autoclosing working for intermediate + It would be nice to have bugs-autoclosing working for intermediate revisions non accepted to the archive but included in a new upload |
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: bugs packages |
tags: | added: soyuz-build soyuz-core |
tags: |
added: soyuz-upload removed: soyuz-build |
To post a comment you must log in.
Given that bug closures are supposed to happen by parsing the .changes file for Launchpad- Bugs-Fixed (and temporarily ignoring the fact that LP sometimes goes and invalidly reparses the changelog anyway), I suspect the best way to fix this would be to make it possible to accept all the uploads and have only the most recent one actually be built. This might end up being dependent on the ability to cancel builds ...