Bug 446243 - Update Bazaar to latest version
Update Bazaar to latest version
Product: Fedora
Classification: Fedora
Component: bzr (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Toshio Ernie Kuratomi
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-05-13 13:44 EDT by Sebastian Pölsterl
Modified: 2008-05-13 14:03 EDT (History)
2 users (show)

See Also:
Fixed In Version: bzr-1.4-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-13 14:03:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sebastian Pölsterl 2008-05-13 13:44:11 EDT
Fedora 9 is using version 1.3.1. However the latest stable release is 1.4 and
the 1.5rc1 has been released, too.
Comment 1 Toshio Ernie Kuratomi 2008-05-13 13:56:34 EDT
1.4 has been built for Fedora 9 testing. Unfortunately, with all the special
things happening around the release, this is probably not apparent.

1.5 will be packaged after it's hit final and may or may not make it into Fedora
9.  There's API breaks in 1.4 (but being a zero day update, I decided to do it.)
 1.5 seems likely to have more API breaks but they may be minor or Fedora 9 may
feel new enough that this is doable.

I'm probably not going to release 1.4 for Fedora < 9 due to the API breaks :-(
but I do flip-flop on this.  The basic conundrum is that as the repository
format changes it is backwards compatible but not forward compatible.  So there
is an inclination to upgrade for older releases so they can use the bzr repos
created with new releases.  OTOH, the API is changing so upgrading will break
things for people who have built custom code on top of bzr.  Not a great set of
options for me to try and target.
Comment 2 Toshio Ernie Kuratomi 2008-05-13 14:00:53 EDT
BTW, The update info is here:


If you use bzr-1.4 and bzrtools-1.4.0 from the testing repository or download
and use it from the build link on that page, you can submit comments on whether
it works for you.  More positive comments will move it from testing to stable
quicker :-)

Note You need to log in before you can comment on or make changes to this bug.