Please backport bzr 2.0.2 from karmic-updates
Bug #302987 reported by
Martin Pool
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Invalid
|
Undecided
|
Unassigned | ||
Hardy Backports |
Won't Fix
|
Undecided
|
Morten Kjeldgaard | ||
Intrepid Ibex Backports |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty Jackalope Backports |
Invalid
|
Undecided
|
Unassigned | ||
bzr (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
bzr 2.0.2 is a large improvement over the 1.x features shipped in earlier releases, and includes supports for the 2a repository format used for ubuntu distributed development and many other branches.
2.0.2 has passed through the SRU process into karmic-updates. It would be good to now backport it into earlier releases. It should build at least back to hardy with no changes.
This is causing some user pain (see bug 505007) because users on hardy (using bzr 1.3) try to get branches from Launchpad and cannot.
summary: |
- Please backport bzr 1.6 or 1.9 + Please backport bzr 1.14 |
description: | updated |
Changed in hardy-backports: | |
assignee: | nobody → Morten Kjeldgaard (mok0) |
Changed in jaunty-backports: | |
status: | New → Invalid |
Changed in bzr (Ubuntu): | |
status: | Incomplete → Invalid |
To post a comment you must log in.
Doing this backport will probably require a synchronized update to the bzr plugins shipped in ubuntu, primarily bzrtools, bzr-svn and bzr-gtk. The 1.3.1 versions will probably give warnings or not work well with 1.6 or later.