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

2012-06-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-dev-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. https://bugs.launchpad.net/b

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

2012-06-01 Thread Evan Broder
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.

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

2012-06-01 Thread Jeremy Bicha
By the way, what does this mean? "backportpackage: Switch to ~ubuntu12.04.1-style version numbers instead of ~precise1, to make our version numbers more future-proof." -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. htt

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

2012-06-01 Thread Benjamin Drung
Wouldn't it be better to tweak dpkg-source to look for "ubuntu", but not for "~ubuntu"? -- 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