changelog version checking mistakenly picks up versions in proposed.
Bug #1461661 reported by
Robert Bruce Park
on 2015-06-03
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | CI Train [cu2d] |
Won't Fix
|
Undecided
|
Robert Bruce Park | |
Bug Description
Consider this case:
1. silo is built normally, and published.
2. proposed migration finds a problem and blocks the package.
3. lander fixes the problem and rebuilds the package.
4. The build job does a sanity check on the changelog to ensure it has the latest destination release, but in this case it sees the version in proposed and says "whoa! this version in proposed isn't in the trunk changelog! please sync dest version back to trunk.".
The workaround is to just FORCE_REBUILD to skip that check, but really versions in -proposed should not be considered when doing changelog integrity checks.
To post a comment you must log in.
Hm, I'm having second thoughts about this. FORCE_REBUILD does workaround the issue stated above, and I think in the case of publishing two conflicting silos, we DO want to check against proposed, because if there's a version in proposed it's more likely to mean that you need to wait for a conflicting silo to merge before building.