Higher version at destination if something is in backports pocket
Bug #1680137 reported by
Christian Ehrhardt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bileto |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi,
on the example of apache2 for trusty I can't work on an SRU via Bileto including the dep8 testing.
The reason is that there is a newer version in trusty-backports. That is fine but it should still let me go on right?.
Well actually that might be part of the ppa setup as the ppa thinks it is outdated, but I checked the ppa config and it is not on "backports" so I still don't see why it should block going on.
But enough assumptions - I'll let you tell me which tool decides in this case before going deeper.
Example ticket: https:/
To post a comment you must log in.
So you're wanting to release an update to trusty-updates that ignores the one in trusty-backports?