1 2Notable changes in 0.31 (since 0.30.1) 3====================================== 4 5* Python 3 is now supported, and Python 2 support is deprecated. It's 6 possible that we'll stop new development for Python 2 fairly soon. 7 If so, we'll probably continue to fix bugs in the last Python 2 8 compatible version for a while, but please make plans to migrate. 9 10* `bup features` has been added. It reports information about bup 11 itself, including the Python version, and the current availability 12 of features like readline or support for POSIX ACLs. 13 14May require attention 15--------------------- 16 17* bup now relies on libacl directly instead of python-pylibacl, which 18 will require installing the relevant packages (e.g. libacl1-dev) 19 before building. 20 21* bup now relies on libreadline directly instead of python's built-in 22 support, which will require installing the relevant packages 23 (e.g. libreadline-dev) before building. 24 25* `bup version --tag` has been removed. It was actually a synonym for 26 `bup version`, which still works fine. The fact that the version 27 may have a corresponding git tag is no longer relevant to the 28 command. 29 30* `git describe` style strings will no longer appear in the `bup 31 version` for non-release builds. The version in that case will 32 currently just be formatted as `PENDING_RELEASE~HASH`, where `~` has 33 the [Debian semantics](https://www.debian.org/doc/debian-policy/ch-controlfields.html#version), 34 for example, 0.31~5ac3821c0f1fbd6a1b1742e91ffd556cd1116041). This 35 is part of the fix for the issue with varying `git archive` content 36 mentioned below. 37 38General 39------- 40 41* `bup fsck` should now avoid displaying `par2` errors when testing it 42 for parallel processing support. 43 44* The documentation for the hashsplit algorithm in DESIGN has been 45 updated to reflect quirks of the implementation, which didn't quite 46 match the original specification. 47 48Bugs 49---- 50 51* When running `bup on` with a remote ssh `ForceCommand`, bup should 52 now respect that setting when running sub-commands. 53 54* It should no longer be possible for the content of archives generated 55 by `git archive` (including releases retrieved from github) to vary 56 based on the current set of repository refs (tags, branches, etc.). 57 Previously archives generated from the same tag could differ 58 slightly in content. 59 60Build and install 61----------------- 62 63* `bup` itself is now located in now located in the cmd/ directory in 64 the install tree and finds sub-commands, etc. relative to its own 65 location. 66 67* The metadata tests should no longer fail on systems with SELinux 68 enabled. 69 70Thanks to (at least) 71==================== 72 73Aaron M. Ucko, Aidan Hobson Sayers, Alexander Barton, Brian Minton, 74Christian Cornelssen, Eric Waguespack, Gernot Schulz, Greg Troxel, 75Hartmut Krafft, Johannes Berg, Luca Carlon, Mark J Hewitt, Ralf 76Hemmecke, Reinier Maas, Rob Browning, Robert Edmonds, Wyatt Alt, Zev 77Eisenberg, gkonstandinos, and kd7spq 78