Higher version at destination if something is in backports pocket

Bug #1680137 reported by Christian Ehrhardt 
6
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://bileto.ubuntu.com/#/ticket/2703

Revision history for this message
Robert Bruce Park (robru) wrote :

So you're wanting to release an update to trusty-updates that ignores the one in trusty-backports?

Revision history for this message
Robert Bruce Park (robru) wrote :

Let me know if you need a configuration option to determine whether or not a ticket should inspect *-backports or whether -backports should just be universally ignored.

Changed in bileto:
status: New → Incomplete
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Since backports are "unsupported" and SRU activity is the supported path I'd lean to -backports generally being ignored.

Now Bileto is clearly for more than SRU work, so I beg your pardon if I overlook a use-case which would want -backports to be considered.

But I'd think unless you introduce something like "<Release>-backports" in the Bileto Ticket dropdown for "Target Series" it should IMHO always be right to ignore -backports.
Once you'd introduce such a feature, that would also be the "switch" that changes which pocket to inspect to compare versions (and create Diffs btw).

Changed in bileto:
status: Incomplete → New
Revision history for this message
Robert Bruce Park (robru) wrote :

Ok I've pushed a fix that makes bileto ignore *-backports. If that breaks somebody then they can complain and I'll add a configurable option to the ticket to be able to choose if you want backports or not.

Changed in bileto:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.