merge-package does the wrong thing when when upstream goes from n.m to n.p where (m < 10) and (p >= 10)
Bug #494123 reported by
James Westby
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bzr-builddeb |
Fix Released
|
Critical
|
Unassigned | ||
| bzr-builddeb (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
| Karmic |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Thanks to Colin Watson I found this:
merge-package currently uses a string compare to know which branch
of the package has the newest upstream. Debian version numbers do
not string compare correctly.
This leads to it choosing the older content for the tree, and so a mis-merge.
Thanks,
James
Related branches
| Changed in bzr-builddeb: | |
| status: | New → Fix Committed |
| importance: | Undecided → Critical |
| Changed in bzr-builddeb (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in bzr-builddeb: | |
| status: | Fix Committed → Fix Released |
| Changed in bzr-builddeb (Ubuntu): | |
| status: | Triaged → Fix Released |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #1 |
| Changed in bzr-builddeb (Ubuntu Karmic): | |
| status: | New → Won't Fix |
To post a comment you must log in.
Karmic has long since stopped to receive any updates. Marking the Karmic task for this ticket as "Won't Fix".