Backport is rejected if an older backport is already there
Bug #58144 reported by
John Dong
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Celso Providelo |
Bug Description
k3b 0.12.16 was already in dapper-backports, but I now want 0.12.17 in dapper-backports. Soyuz is rejecting the backport because an older backport exists in the archive. This should not be the case; newer backports should replace older ones.
The exact message I got via e-mail is:
k3b: Version newer than that in BACKPORTS. 0.12.17-
To post a comment you must log in.
I think this check is wrong anyway. If we want to supersede a version in backports with a version in another pocket, then we should be able to do so. Certainly I agree with John that an upload to backports should be able to supersede an older upload to backports, but I'd go further and say that this check should be removed entirely as it's wrong.
Does anyone on the Soyuz team know why this check was added?