Destination version check should ignore versions that were published from the same ticket

Bug #1678332 reported by Robert Bruce Park
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bileto
Fix Released
High
Robert Bruce Park

Bug Description

Consider this scenario:

1. Ticket is built & published
2. Package is stuck in -proposed
3. Fix is added to MP, ticket rebuilt

You get the status "destination version missing from changelog" because the package published in step 1 is essentially "orphaned", eg, bileto sees it there but doesn't realize that it's its own package from a previous publication.

The dest version check should grow an exception that inspects the publish log to ignore package versions previously published from within the same ticket.

Workaround for now: get a core dev to delete the offending package from -proposed.

Changed in bileto:
status: New → Triaged
assignee: nobody → Robert Bruce Park (robru)
importance: Undecided → High
Revision history for this message
Robert Bruce Park (robru) wrote :

Ok I pushed an experimental fix for this. Please try again and let me know if this happens again.

Changed in bileto:
status: Triaged → 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.