|2.2.6:||NOT RELEASED YET|
This is a bugfix release. One regression introduced in 2.2b1 has been fixed for some rare conflict resolutions. Also a warning is now emmitted when branching an out-of-date ubuntu packaging branch. Upgrading is recommended for all users on earlier 2.2 releases.
This is a bugfix release. Only one bug has been fixed, a regression from 2.2.3 involving only certain operations with launchpad. Upgrading is recommended for all users on earlier 2.2 releases.
This is a bugfix release. Upgrading is recommended for all users on earlier 2.2 releases.
This is a bugfix release. None of these bugfixes are critical, but upgrading is recommended for all users on earlier 2.2 releases.
This is a bugfix release which also includes bugfixes from 2.0.6 and 2.1.3. None are critical, but upgrading is recommended for all users on earlier 2.2 releases.
This release marks the start of another long-term-stable series. From here, we will only make bugfix releases on the 2.2 series (2.2.1, etc), while 2.3 will become our new development series. The 2.0 and 2.1 series will also continue to get bugfixes. (Currently 2.0 is planned to be supported for another 6 months.)
This is primarily a bugfix and polish release over the 2.1 series, with a large number of bugs fixed (>120), and some performance improvements.
There are some compatibility changes in this release. For users of bzrlib as a library, we now request that they call bzrlib.initialize and use the returned context manager appropriately. For commandline users we no longer guess user identity for bzr commit, users must specify their identity using bzr whoami (you don’t need to specify your identity for readonly operations).
Users are encouraged to upgrade from the other stable series.
This fourth and final beta in the 2.2 series now stabilizes the internal APIs. Plugin authors are recommended to ensure their releases are compatible, so that 2.2rc1 can be a true release candidate, containing stable and compatible plugin versions.
For users of bzrlib as a library, one of the primary changes is to request that they call bzrlib.initialize and use the returned context manager appropriately.
Better interaction with bzr-loom to make sure branching from a loom even over a smart server still yields a local loom. Not to mention lots of bugfixes over 2.2b3.
This third beta in the 2.2 series brings with it all the goodness of 2.1.2 and 2.0.6 (though it preceeds 2.0.6 slightly). Of particular note for users are compatibility fixes with bzr 1.5 and below servers, a hopeful end to the EINTR errors caused by SIGWINCH interactions, a shiny new bash completion script and bzr will no longer guess at identity details - it was too unreliable in reality. Use bzr whoami on every new install. For developers we have some API changes which may impact plugins as well as a bunch of our regular improvements to internal clarity and test support.
Added bzrlib.tests.matchers as a place to put matchers, along with our first in-tree matcher. See the module docstring for details. (Robert Collins)
(Gordon Tyler, #551332)
Workaround Crypto.Random check leading to spurious test failures on Lucid, FreeBSD and gentoo. (Vincent Ladeuil, #528436)
New class ExecutableFeature for checking the availability of executables on the PATH. Migrated from bash_completion plugin. (Martin von Gagern)
This is a somewhat early second beta of the 2.2 series, to fix a python2.4 incompatibility in the 2.2b1 release. It also includes a swag of performance, usability and correctness improvements: test feedback on all of these would be welcome.
This is the first beta of the 2.2 series, leading up to a 2.2.0 release in July or August. Beta releases are suitable for everyday use but may cause some incompatibilities with plugins. Some plugins may need small updates to work with 2.2b1.
2.2b1 includes some changes to make merge conflicts easier to understand and resolve. It also removes some old unnecessary code, and loads somewhat less code at startup. It starts adding a common infrastructure for dealing with colocated named branches, which can be implemented in various ways in either bzr native or foreign formats. On Ubuntu and other platforms with the apport bug-reporting library, there’s an easier path to report problems with bzr. We plan to continue with these themes through the 2.2 series.
Over thirty bugs have been fixed, including in the log command, exporting to tarballs, restarting interrupted system calls, portability of compiled extensions, making backups during upgrade, and locking on FTP.
Added docstring for Tree.iter_changes (John Arbash Meinel, #304182)
Allow additional arguments to RemoteRepository.add_inventory_by_delta(). (Jelmer Vernooij, #532631)
Allow exporting a single file using bzr export. (Michal Junák, #511987)
Allow syscalls to automatically restart when TextUIFactory‘s SIGWINCH handler is invoked, avoiding EINTR errors during blocking IO, which are often poorly handled by Python’s libraries and parts of bzrlib. (Andrew Bennetts, #496813)
Avoid infinite recursion when probing for apport. (Vincent Ladeuil, #516934)
Avoid malloc(0) in patiencediff, which is non-portable. (Martin Pool, #331095)
Avoid truncating svn URLs. (Martin Pool, Martin von Gagern, #545185)
bzr add will not add conflict related files unless explicitly required. (Vincent Ladeuil, #322767, #414589)
bzr dump-btree now works on *.cix and *.six files. Those indices do not have reference lists, so dump-btree will simply show None instead. (Andrew Bennetts, #488607)
bzr help will no longer trigger the get_missing_command hook when doing a topic lookup. This avoids prompting (like ‘no command plugins/loom, did you mean log?’) when getting help. In future we may trigger the hook deliberately when no help topics match from any help index. (Robert Collins, #396261)
bzr log -n0 -r..A.B.C should not crash but just consider the None revspec as representing the first revision of the branch. (Vincent Ladeuil, #519862)
bzr remove-tree can now remove multiple working trees. (Jared Hance, Andrew Bennetts, #253137)
bzr resolve --take-this and --take-other now correctly renames the kept file on content conflicts where one side deleted the file. (Vincent Ladeuil, #529968)
bzr upgrade now creates the backup.bzr directory with the same permissions as .bzr directory on a POSIX OS. (Parth Malwankar, #262450)
bzr upgrade now names backup directory as backup.bzr.~N~ instead of backup.bzr. This directory is ignored by bzr commands such as add. (Parth Malwankar, #335033, #300001)
Cope with non-utf8 characters inside .bzrignore. (Jason Spashett, #183504)
Correctly interpret “451 Rename/move failure: Directory not empty” from FTP servers while trying to take a lock. (Martin Pool, #528722)
DirStateRevisionTree.kind() was returning wrong result when ‘kind’ changes occured between the workingtree and one of its parents. (Vincent Ladeuil, #535547)
Fix log to better check ancestors even if merged revisions are involved. (Vincent Ladeuil, #476293)
Loading a plugin from a given path with BZR_PLUGINS_AT doesn’t depend on os.lisdir() order and is now reliable. (Vincent Ladeuil, #552922).
Many IO operations that returned EINTR were retried even if it wasn’t safe to do so via careless use of until_no_eintr. Bazaar now only retries operations that are safe to retry, and in some cases has switched to operations that can be retried (e.g. sock.send rather than sock.sendall). (Andrew Bennetts, Martin <email@example.com>, #496813)
Path conflicts now support –take-this and –take-other even when a deletion is involved. (Vincent Ladeuil, #531967)
Network transfer amounts and rates are now displayed in SI units according to the Ubuntu Units Policy <https://wiki.ubuntu.com/UnitsPolicy>. (Gordon Tyler, #514399)
Support kind markers for socket and fifo filesystem objects. This prevents bzr status --short from crashing when those files are present. (John Arbash Meinel, #303275)
directory. (Parth Malwankar, #138600)
SSH child processes will now ignore SIGQUIT on nix systems so breaking into the debugger won’t kill the session. (Martin <firstname.lastname@example.org>, #162502)
Tolerate patches with leading noise in bzr-handle-patch. (Toshio Kuratomi, Martin Pool, #502076)
update -r now supports updating to revisions that are not on mainline (i.e. it supports dotted revisions). (Parth Malwankar, #517800)
Use first apparent author not committer in GNU Changelog format. (Martin von Gagern, #513322)