bzr - New upstream versions released

Bug #269770 reported by David Futcher
6
Affects Status Importance Assigned to Milestone
bzr (Ubuntu)
Fix Released
Undecided
David Futcher
Intrepid
Fix Released
Undecided
David Futcher

Bug Description

Binary package hint: bzr

New upstream versions of bzr have been released (1.6.1, 1.7rc1 and 1.7 final shouldnt be too far away). The current ubuntu version is 1.6, which contains some regressions, which need to be fixed by Intrepid release. We need to evaluate which version to use in Intrepid, package it and the bzr side packages (bzr-gtk, bzrtools), get the correct Freeze exceptions and upload it.

David Futcher (bobbo)
Changed in bzr:
assignee: nobody → bobbo
status: New → In Progress
Revision history for this message
Colin Watson (cjwatson) wrote :

Please consider bzr 1.6.1 to have a freeze exception from me; judging from the NEWS file it's clearly appropriate. (bzr 1.7 would be a harder sell, I think, although who knows; depends somewhat when it's released.)

bzr 1.6.1 2008-09-05
--------------------

A couple regressions were found in the 1.6 release. There was a
performance issue when using ``bzr+ssh`` to branch large repositories,
and some problems with stacking and ``rich-root`` capable repositories.

bzr 1.6.1rc2 2008-09-03
-----------------------

  BUG FIXES:

    * Copying between ``rich-root`` and ``rich-root-pack`` (and vice
      versa) was accidentally using the inter-model fetcher, instead of
      recognizing that both were 'rich root' formats.
      (John Arbash Meinel, #264321)

bzr 1.6.1rc1 2008-08-29
-----------------------

This release fixes a few regressions found in the 1.6 client. Fetching
changes was using an O(N^2) buffering algorithm, so for large projects it
would cause memory thrashing. There is also a specific problem with the
``--1.6-rich-root`` format, which prevented stacking on top of
``--rich-root-pack`` repositories, and could allow users to accidentally
fetch experimental data (``-subtree``) without representing it properly.
The ``--1.6-rich-root`` format has been deprecated and users are
recommended to upgrade to ``--1.6.1-rich-root`` immediately. Also we
re-introduced a workaround for users who have repositories with incorrect
nodes (not possible if you only used official releases).
I should also clarify that none of this is data loss level issues, but
still sufficient enough to warrant an updated release.

  BUG FIXES:

    * ``RemoteTransport.readv()`` was being inefficient about how it
      buffered the readv data and processed it. It would keep appending to
      the same string (causing many copies) and then pop bytes out of the
      start of the string (causing more copies).
      With this patch "bzr+ssh://local" can improve dramatically,
      especially for projects with large files.
      (John Arbash Meinel)

    * Revision texts were always meant to be stored as fulltexts. There
      was a bug in a bzr.dev version that would accidentally create deltas
      when copying from a Pack repo to a Knit repo. This has been fixed,
      but to support those repositories, we know always request full texts
      for Revision texts. (John Arbash Meinel, #261339)

    * The previous ``--1.6-rich-root`` format used an incorrect xml
      serializer, which would accidentally support fetching from a
      repository that supported subtrees, even though the local one would
      not. We deprecated that format, and introduced a new one that uses
      the correct serializer ``--1.6.1-rich-root``.
      (John Arbash Meinel, #262333)

Revision history for this message
James Westby (james-w) wrote :

Hi,

1.6.1 synced now,

Thanks,

James

Changed in bzr:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.