[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 MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
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

-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs

[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 MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
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

-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs

[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 MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
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

-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs

[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. 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 MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
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

-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs

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

2012-05-31 Thread Jeremy Bicha 
-- 
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
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

-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs