requestsync gets confused by epoch numbers

Bug #261930 reported by Bryce Harrington on 2008-08-27
Affects Status Importance Assigned to Milestone
ubuntu-dev-tools (Ubuntu)
Michael Casadevall

Bug Description

Binary package hint: ubuntu-dev-tools

For example, see:

It appears that for syncs of packages with versions that include epoch numbers, requestsync has problems calculating against the ubuntu version (which was 1:1.1.8-1.1 in this case). As a result, it ends up including a lot more of the upstream changelog than is actually necessary. Both debian and ubuntu have the same epoch number in this case; I suspect it's simply not accounting for the presence of an epoch number when comparing versions or something.

This actually isn't a bug in requestsync. The XDM's changelog was corrupted. In general, the following events happened:

xdm was updated to 1:1.1.8-1.1 via NMU (.1 point release)
xdm maintainer doesn't properly ack the NMU, -2 is uploaded, 1.1 is removed from the changelog
requestsync can't find the matching version and prints out a bunch of the changelog log, classic GIGO situation.

Tagging this invalid.

Changed in ubuntu-dev-tools:
assignee: nobody → sonicmctails
importance: Undecided → Wishlist
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers