[Bug 1007042] Re: [backportpackage] fails but worked last week

Evan Broder evan at ebroder.net
Fri Jun 1 19:15:45 UTC 2012


We used to generate backport version numbers of the form
VERSION_BEING_BACKPORTED~RELEASE_CODENAME1. It worked well at the time
because it guaranteed that a backport of the same version to, e.g.,
natty would have a lower version number than the backport to oneiric,
since the n would sort before o. That's important because we rely on the
version numbers sorting like that for release upgrade paths with
backports to work.

Colin pointed out that this would break down when we ran out of letters
and started wrapping around, and suggested that we instead switch to
using the version number, which is what backportpackage now does.

-- 
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1007042

Title:
  [backportpackage] fails but worked last week

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1007042/+subscriptions



More information about the ubuntu-backports mailing list