head 1.12; access; symbols pkgsrc-2023Q4:1.12.0.2 pkgsrc-2023Q4-base:1.12 pkgsrc-2023Q3:1.11.0.26 pkgsrc-2023Q3-base:1.11 pkgsrc-2023Q2:1.11.0.24 pkgsrc-2023Q2-base:1.11 pkgsrc-2023Q1:1.11.0.22 pkgsrc-2023Q1-base:1.11 pkgsrc-2022Q4:1.11.0.20 pkgsrc-2022Q4-base:1.11 pkgsrc-2022Q3:1.11.0.18 pkgsrc-2022Q3-base:1.11 pkgsrc-2022Q2:1.11.0.16 pkgsrc-2022Q2-base:1.11 pkgsrc-2022Q1:1.11.0.14 pkgsrc-2022Q1-base:1.11 pkgsrc-2021Q4:1.11.0.12 pkgsrc-2021Q4-base:1.11 pkgsrc-2021Q3:1.11.0.10 pkgsrc-2021Q3-base:1.11 pkgsrc-2021Q2:1.11.0.8 pkgsrc-2021Q2-base:1.11 pkgsrc-2021Q1:1.11.0.6 pkgsrc-2021Q1-base:1.11 pkgsrc-2020Q4:1.11.0.4 pkgsrc-2020Q4-base:1.11 pkgsrc-2020Q3:1.11.0.2 pkgsrc-2020Q3-base:1.11 pkgsrc-2020Q2:1.9.0.6 pkgsrc-2020Q2-base:1.9 pkgsrc-2020Q1:1.9.0.2 pkgsrc-2020Q1-base:1.9 pkgsrc-2019Q4:1.9.0.4 pkgsrc-2019Q4-base:1.9 pkgsrc-2019Q3:1.8.0.2 pkgsrc-2019Q3-base:1.8 pkgsrc-2019Q2:1.7.0.26 pkgsrc-2019Q2-base:1.7 pkgsrc-2019Q1:1.7.0.24 pkgsrc-2019Q1-base:1.7 pkgsrc-2018Q4:1.7.0.22 pkgsrc-2018Q4-base:1.7 pkgsrc-2018Q3:1.7.0.20 pkgsrc-2018Q3-base:1.7 pkgsrc-2018Q2:1.7.0.18 pkgsrc-2018Q2-base:1.7 pkgsrc-2018Q1:1.7.0.16 pkgsrc-2018Q1-base:1.7 pkgsrc-2017Q4:1.7.0.14 pkgsrc-2017Q4-base:1.7 pkgsrc-2017Q3:1.7.0.12 pkgsrc-2017Q3-base:1.7 pkgsrc-2017Q2:1.7.0.8 pkgsrc-2017Q2-base:1.7 pkgsrc-2017Q1:1.7.0.6 pkgsrc-2017Q1-base:1.7 pkgsrc-2016Q4:1.7.0.4 pkgsrc-2016Q4-base:1.7 pkgsrc-2016Q3:1.7.0.2 pkgsrc-2016Q3-base:1.7 pkgsrc-2016Q2:1.6.0.10 pkgsrc-2016Q2-base:1.6 pkgsrc-2016Q1:1.6.0.8 pkgsrc-2016Q1-base:1.6 pkgsrc-2015Q4:1.6.0.6 pkgsrc-2015Q4-base:1.6 pkgsrc-2015Q3:1.6.0.4 pkgsrc-2015Q3-base:1.6 pkgsrc-2015Q2:1.6.0.2 pkgsrc-2015Q2-base:1.6 pkgsrc-2015Q1:1.5.0.6 pkgsrc-2015Q1-base:1.5 pkgsrc-2014Q4:1.5.0.4 pkgsrc-2014Q4-base:1.5 pkgsrc-2014Q3:1.5.0.2 pkgsrc-2014Q3-base:1.5 pkgsrc-2014Q2:1.4.0.4 pkgsrc-2014Q2-base:1.4 pkgsrc-2014Q1:1.4.0.2 pkgsrc-2014Q1-base:1.4 pkgsrc-2013Q4:1.3.0.12 pkgsrc-2013Q4-base:1.3 pkgsrc-2013Q3:1.3.0.10 pkgsrc-2013Q3-base:1.3 pkgsrc-2013Q2:1.3.0.8 pkgsrc-2013Q2-base:1.3 pkgsrc-2013Q1:1.3.0.6 pkgsrc-2013Q1-base:1.3 pkgsrc-2012Q4:1.3.0.4 pkgsrc-2012Q4-base:1.3 pkgsrc-2012Q3:1.3.0.2 pkgsrc-2012Q3-base:1.3 pkgsrc-2012Q2:1.2.0.10 pkgsrc-2012Q2-base:1.2 pkgsrc-2012Q1:1.2.0.8 pkgsrc-2012Q1-base:1.2 pkgsrc-2011Q4:1.2.0.6 pkgsrc-2011Q4-base:1.2 pkgsrc-2011Q3:1.2.0.4 pkgsrc-2011Q3-base:1.2 pkgsrc-2011Q2:1.2.0.2 pkgsrc-2011Q2-base:1.2 pkgsrc-20110516:1.1.1.1 TNF:1.1.1; locks; strict; comment @# @; 1.12 date 2023.12.09.01.46.30; author gdt; state Exp; branches; next 1.11; commitid d4ygHGUJD7yYkJPE; 1.11 date 2020.09.20.22.28.00; author gdt; state Exp; branches; next 1.10; commitid WbzVdkoLy52OZPoC; 1.10 date 2020.09.20.16.44.54; author gdt; state Exp; branches; next 1.9; commitid FrGCeTUnnkvI4OoC; 1.9 date 2019.11.19.15.01.25; author gdt; state Exp; branches; next 1.8; commitid dHULpumzPzAMltLB; 1.8 date 2019.09.12.00.28.47; author gdt; state Exp; branches; next 1.7; commitid BAyITOAQWaTJHECB; 1.7 date 2016.09.18.23.02.48; author gdt; state Exp; branches; next 1.6; commitid hsrTDZe5OnoodPmz; 1.6 date 2015.04.27.09.17.17; author wiz; state Exp; branches; next 1.5; commitid z7EyppXexdRF2djy; 1.5 date 2014.09.06.21.29.45; author wiz; state Exp; branches; next 1.4; commitid AhriHFsXyqzQzkPx; 1.4 date 2013.12.31.11.03.12; author wiz; state Exp; branches; next 1.3; commitid qgvZ965eINjg7hjx; 1.3 date 2012.09.04.13.43.15; author wiz; state Exp; branches; next 1.2; 1.2 date 2011.05.31.12.01.18; author wiz; state Exp; branches; next 1.1; 1.1 date 2011.05.16.13.52.56; author wiz; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2011.05.16.13.52.56; author wiz; state Exp; branches; next ; desc @@ 1.12 log @sysutils/bup: Update to 0.33.2 Upstream NEWS less some bugfixes and minor improvements: Notable changes in 0.33 since 0.32 Python 3 is now required, in particular 3.7 or newer. The version of Python is no longer determined by the value of PYTHON during ./configure. It is now determined by the version of python-config selected during configuration. The BUP_PYTHON_CONFIG environment variable can be set during configuration to select a particular executable (e.g. BUP_PYTHON_CONFIG=python3.9-config ./configure). See the README for further details. The bup executable is now a binary rather than a Python script. Practically speaking, this means that the Python version is determined by the libpython that the executable is linked against (selected via python-config), and it means that bup will show up as "bup" in process listings rather than a python invocation. The output of bup ls for multiple paths includes each path before its contents, more closely matching the system ls. The bup ftp ls command should now respect the working directory (set by cd), and that directory has been added to the prompt. The index-cache is no longer included in the bup midx --dir default. Performance may have improved after the relocation of a number of operations from Python to C, and a number of improvements to the VFS. Bugs Bup should now respect the current umask, directory sgid bit, etc. when creating new files (e.g. new packfiles). Previously, it would create them via mkstemp, which would cause them to be readable only by the current user. Bup should now be able to handle repositories containing signed commits. bup tag has been changed to rely on git update-ref instead of writing the (loose) refs directly so that it can handle packed refs correctly. bup save should be more careful about noting an error and skipping paths whose type (link, regular file, ...) has changed since indexing. There should no longer be a narrow window where save could store conflicting symlink targets or conflicting sizes (in the metadata record and the packfile symlink blob) for a path if the filesystem changed at just the wrong time during a save. bup fuse should no longer become unusable after an unfinished read of commits associated with tags. The underlying VFS issue may have affected other commands too. Bup's packfile names should now match git's. Previously bup computed the SHA1 from just the sorted object list (cf. git-index-pack(1)), but git appears to include the entire pack file in the hash. Passing idx files to bup midx along with --dir should now work correctly. Resource usage (e.g. memory) may have improved, given a number of changes intended to make bup release resources more carefully and sooner. Build and install The build process should now work on systems where make isn't GNU Make (the Makefile automatically redirects to GNUmakefile). Thanks to (at least) Abdel Said, Arthur Ward, Bas Stottelaar, Brian Minton, Greg Troxel, Johannes Berg, Mark Hewitt, Muh Muhten, and Rob Browning @ text @@@comment $NetBSD: PLIST,v 1.11 2020/09/20 22:28:00 gdt Exp $ bin/bup lib/bup/bup/__init__.py lib/bup/bup/_helpers.so lib/bup/bup/bloom.py lib/bup/bup/client.py lib/bup/bup/cmd/__init__.py lib/bup/bup/cmd/bloom.py lib/bup/bup/cmd/cat_file.py lib/bup/bup/cmd/daemon.py lib/bup/bup/cmd/damage.py lib/bup/bup/cmd/drecurse.py lib/bup/bup/cmd/features.py lib/bup/bup/cmd/fsck.py lib/bup/bup/cmd/ftp.py lib/bup/bup/cmd/fuse.py lib/bup/bup/cmd/gc.py lib/bup/bup/cmd/get.py lib/bup/bup/cmd/help.py lib/bup/bup/cmd/import_duplicity.py lib/bup/bup/cmd/index.py lib/bup/bup/cmd/init.py lib/bup/bup/cmd/join.py lib/bup/bup/cmd/list_idx.py lib/bup/bup/cmd/ls.py lib/bup/bup/cmd/margin.py lib/bup/bup/cmd/memtest.py lib/bup/bup/cmd/meta.py lib/bup/bup/cmd/midx.py lib/bup/bup/cmd/mux.py lib/bup/bup/cmd/on.py lib/bup/bup/cmd/on__server.py lib/bup/bup/cmd/prune_older.py lib/bup/bup/cmd/random.py lib/bup/bup/cmd/restore.py lib/bup/bup/cmd/rm.py lib/bup/bup/cmd/save.py lib/bup/bup/cmd/server.py lib/bup/bup/cmd/split.py lib/bup/bup/cmd/tag.py lib/bup/bup/cmd/tick.py lib/bup/bup/cmd/version.py lib/bup/bup/cmd/web.py lib/bup/bup/cmd/xstat.py lib/bup/bup/compat.py lib/bup/bup/drecurse.py lib/bup/bup/gc.py lib/bup/bup/git.py lib/bup/bup/hashsplit.py lib/bup/bup/helpers.py lib/bup/bup/hlinkdb.py lib/bup/bup/index.py lib/bup/bup/io.py lib/bup/bup/ls.py lib/bup/bup/main.py lib/bup/bup/metadata.py lib/bup/bup/midx.py lib/bup/bup/options.py lib/bup/bup/path.py lib/bup/bup/pwdgrp.py lib/bup/bup/repo.py lib/bup/bup/rm.py lib/bup/bup/shquote.py lib/bup/bup/source_info.py lib/bup/bup/ssh.py lib/bup/bup/tree.py lib/bup/bup/version.py lib/bup/bup/vfs.py lib/bup/bup/vint.py lib/bup/bup/xstat.py lib/bup/cmd/bup lib/bup/cmd/bup-import-rdiff-backup lib/bup/cmd/bup-import-rsnapshot lib/bup/web/list-directory.html lib/bup/web/static/styles.css man/man1/bup-bloom.1 man/man1/bup-cat-file.1 man/man1/bup-daemon.1 man/man1/bup-damage.1 man/man1/bup-drecurse.1 man/man1/bup-features.1 man/man1/bup-fsck.1 man/man1/bup-ftp.1 man/man1/bup-fuse.1 man/man1/bup-gc.1 man/man1/bup-get.1 man/man1/bup-help.1 man/man1/bup-import-duplicity.1 man/man1/bup-import-rdiff-backup.1 man/man1/bup-import-rsnapshot.1 man/man1/bup-index.1 man/man1/bup-init.1 man/man1/bup-join.1 man/man1/bup-ls.1 man/man1/bup-margin.1 man/man1/bup-memtest.1 man/man1/bup-meta.1 man/man1/bup-midx.1 man/man1/bup-mux.1 man/man1/bup-on.1 man/man1/bup-prune-older.1 man/man1/bup-random.1 man/man1/bup-restore.1 man/man1/bup-rm.1 man/man1/bup-save.1 man/man1/bup-server.1 man/man1/bup-split.1 man/man1/bup-tag.1 man/man1/bup-tick.1 man/man1/bup-web.1 man/man1/bup.1 share/doc/bup/DESIGN share/doc/bup/README @ 1.11 log @sysutils/bup: Update man page tarball for 0.31 @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.10 2020/09/20 16:44:54 gdt Exp $ d7 38 a45 1 lib/bup/bup/csetup.py d55 1 a60 1 lib/bup/bup/py2raise.py d66 1 a71 13 lib/bup/cmd/bup-bloom lib/bup/cmd/bup-cat-file lib/bup/cmd/bup-daemon lib/bup/cmd/bup-damage lib/bup/cmd/bup-drecurse lib/bup/cmd/bup-features lib/bup/cmd/bup-fsck lib/bup/cmd/bup-ftp lib/bup/cmd/bup-fuse lib/bup/cmd/bup-gc lib/bup/cmd/bup-get lib/bup/cmd/bup-help lib/bup/cmd/bup-import-duplicity a73 24 lib/bup/cmd/bup-index lib/bup/cmd/bup-init lib/bup/cmd/bup-join lib/bup/cmd/bup-list-idx lib/bup/cmd/bup-ls lib/bup/cmd/bup-margin lib/bup/cmd/bup-memtest lib/bup/cmd/bup-meta lib/bup/cmd/bup-midx lib/bup/cmd/bup-mux lib/bup/cmd/bup-on lib/bup/cmd/bup-on--server lib/bup/cmd/bup-prune-older lib/bup/cmd/bup-random lib/bup/cmd/bup-restore lib/bup/cmd/bup-rm lib/bup/cmd/bup-save lib/bup/cmd/bup-server lib/bup/cmd/bup-split lib/bup/cmd/bup-tag lib/bup/cmd/bup-tick lib/bup/cmd/bup-version lib/bup/cmd/bup-web lib/bup/cmd/bup-xstat @ 1.10 log @sysutils/bup: Update to 0.31 Passes bup's test suite on netbsd-8/amd64, with TZ=UTC (needed to work around what is likely a bug in git around DST changes). Packaging changes/notes: - bup depends directly on readline, GNU version required - man pages have not yet been updated Upstream changes include many minor improvements and bugfixes, and: Notable changes in 0.31 (since 0.30.1) ====================================== * Python 3 is now supported, and Python 2 support is deprecated. It's possible that we'll stop new development for Python 2 fairly soon. If so, we'll probably continue to fix bugs in the last Python 2 compatible version for a while, but please make plans to migrate. * `bup features` has been added. It reports information about bup itself, including the Python version, and the current availability of features like readline or support for POSIX ACLs. Build and install ----------------- * `bup` itself is now located in now located in the cmd/ directory in the install tree and finds sub-commands, etc. relative to its own location. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.9 2019/11/19 15:01:25 gdt Exp $ d80 1 @ 1.9 log @sysutils/bup: Update to 0.30 packaging changes: switch to 0.30 man tarball Notable changes in 0.30 as compared to 0.29.3 ============================================= May require attention --------------------- * The minimum `git` version required is now 1.5.6. * The `prune-older` command now keeps the most recent save in each period group (day, week, month, ...) rather than the oldest. * `bup` now adds a zero-padded suffix to the names of saves with the same timestamp (e.g. 1970-01-01-214640-07) in order to avoid duplicates. The sequence number currently represents the save's reversed position in default `git rev-list` order, so that given: /foo/1970-01-01-214640-09 /foo/1970-01-01-214640-10 In the normal case, the -10 save would be the next save made after -09 (and the -09 save would be the single parent commit for -10). * `bup` is not currently compatible with Python 3 and will now refuse to run if the Python version is not 2 unless `BUP_ALLOW_UNEXPECTED_PYTHON_VERSION=true` is set in the environment (which can be useful for development and testing). * `bup ls -s` now reports the tree hash for commits unless `--commit-hash` is also specified. General ------- * `bup get` has been added. This command allows the transfer or rewriting of data within and between repositories, local or remote. Among other things, it can be used to append remote saves to a local branch, which by extension supports merging repositories. See `bup-get(1)` for further information, and please note, this is a new *EXPERIMENTAL* command that can (intentionally) modify your data in destructive ways. It is potentially much more dangerous than most `bup` commands. Treat with caution. * `bup` can now restore directly from a remote repository via `bup restore -r host:path ...`. See `bup-restore(1)` for more information. * `bup ls` can now report information for remote repositories via `bup ls -r host:path ...`. See `bup-ls(1)` for more information. * `bup` should respect the git pack.packSizeLimit setting when writing packfiles, though at the moment it will only affect a remote repository when the option is set there directly. * `bup save` now stores the size for all links and normal files. For directories saved using this new format retrieving file sizes for larger files should be notably less expensive. Among other things this may improve the performance of commands like `bup ls -l` or `find /some/fuse/dir -ls`. * The VFS (Virtual File System) that underlies many operations, and provides the basis for commands like `restore`, `ls`, etc. has been rewritten in a way that makes remote repository access easier, should decrease the memory footprint in some cases (e.g. for bup fuse), and should make it easier to provide more selective caching. At the moment, data is just evicted at random once a threshold is reached. * A `--noop <--blobs|--tree>` option has been added to `bup split` which prints the resulting id without storing the data in the repository. Bugs ---- * The way `bup` handles output from subprocesses (diagnostics, progress, etc.) has been adjusted in a way that should make it less likely that bup might continue running after the main process has exited, say via a C-c (SIGINT). * `bup` should now respect the specified compression level when writing to a remote repository. * `bup restore` now creates FIFOs with mkfifo, not mknod, which is more portable. The previous approach did not work correctly on (at least) some versions of NetBSD. * `bup` should no longer just crash when it encounters a commit with a "mergetag" header. For the moment, it just ignores them, and they'll be discarded whenever `bup` rewrites a commit, say via the `rm`, `prune-older`, or `get` commands. * The bloom command should now end progress messages with \r, not \n, which avoids leaving spurious output lines behind at exit. * A missing space has been added to the `bup split --bench` output. * Various Python version compatibility problems have been fixed, including some of the incompatibilities introduced by Python 3. * Some issues with mincore on WSL have been fixed. * Some Android build incompatibilities have been fixed. Build system ------------ * The tests no longer assume pwd is in /bin. * The tests should be less sensitive to the locale. * `test-meta` should no longer try to apply chattr +T to files. 'T' only works for directories, and newer Linux kernels actually reject the attempt (as of at least 4.12, and maybe 4.10). * `test-rm` should no longer fail when newer versions of git automatically create packed-refs. * `test-sparse-files` should be less likely to fail when run inside a container. * `test-index-check-device` and `test-xdev` now use separate files for their loopback mounts. Previously each was mounting the same image twice, which could produce the same device number. Thanks to (at least) ==================== Alexander Barton, Artem Leshchev, Ben Kelly, Fabian 'xx4h' Melters, Greg Troxel, Jamie Wyrick, Julien Goodwin, Mateusz Konieczny, Nathaniel Filardo, Patrick Rouleau, Paul Kronenwetter, Rob Browning, Robert Evans, Tim Riemenschneider, and bedhanger @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.8 2019/09/12 00:28:47 gdt Exp $ a4 1 lib/bup/bup/_release.py d16 1 d22 2 d27 1 d33 1 d39 1 @ 1.8 log @sysutils/bup: Update to 0.29.3 Upstream changes (other than bugfixes minor improvements): 0.29.3: * Newer versions of par2 can process in parallel using multiple threads/cores, and they do so automatically. This ends up competing with `bup fsck`s own parallelism, enabled by `-j`, in such a way that the command can actually run much *slower* (and be much more expensive) than it would have been with no parallelism at all. When appropriate `bup fsck` now disables par2's competing parallelism (via its `-t1` option) to avoid the contention. 0.29.0: * An experimental `prune-older` command has been added. It removes (permanently deletes) all saves except those preserved by a set of arguments like `--keep-monthlies-for 3y`. See `bup help prune-older` for further information. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.7 2016/09/18 23:02:48 gdt Exp $ d8 1 d22 1 d39 1 a53 1 lib/bup/cmd/bup-newliner d79 1 a92 1 man/man1/bup-newliner.1 d94 1 @ 1.7 log @Update to 0.28.1 Upstream changes: * The index format has changed, which will trigger a full index rebuild on the next index run, making that run more expensive than usual. * When given `--xdev`, `bup save` should no longer skip directories that are explicitly listed on the command line when the directory is both on a separate filesystem, and a subtree of another path listed on the command line. Previously `bup save --xdev / /usr` could skip "/usr" if it was on a separate filesystem from "/". * Tags along a branch are no longer shown in the branch's directory in the virtual filesystem (VFS). i.e. given `bup tag special /foo/latest`, "/foo/special" will no longer be visible via `bup ls`, `bup web`, `bup fuse`, etc., but the tag will still be available as "/.tag/special". * bup now provides experimental `rm` and `gc` subcommands, which should allow branches and saves to be deleted, and their storage space reclaimed (assuming nothing else refers to the relevant data). For the moment, these commands require an `--unsafe` argument and should be treated accordingly. Although if an attempt to `join` or `restore` the data you still care about after a `gc` succeeds, that's a fairly encouraging sign that the commands worked correctly. (The `t/compare-trees` command in the source tree can be used to help test before/after results.) Note that the current `gc` command is probabilistic, which means it may not remove *all* of the obsolete data from the repository, but also means that the command should be fairly efficient, even for large repositories. * bup may have less impact on the filesystem cache. It now attempts to leave the cache roughly the way it found it when running a `save` or `split`. * A specific Python can be specified at `./configure` time via PYTHON, i.e. `PYTHON=/some/python ./configure`, and that Python will be embedded in all of the relevant scripts as an explicit "#!/..." line during `make install`. * The way bup writes the data to disk (the packfiles in particular), should be a bit safer now if there is a coincident power failure or system crash. * bup should be more likely to get the data to permanent storage safely on OS X, which appears to follow a surprising interpretation of the `fsync()` specification. * The build system now creates and uses cmd/bup-python which refers to the `./configure` selected python. @ text @d1 1 a1 1 @@comment $NetBSD$ d10 1 d21 1 d54 1 @ 1.6 log @Update to 0.27: This version primarily fixes bugs, but it includes a few new features, and hopefully will provide a solid base for 0.28, which may finally include rm/gc support. Of note since 0.26: - Files can be restored sparsely via "restore --sparse". See bup-sparse(1) for the details. Given that this option is completely new and affects the data written, some caution/verification may be wise (i.e. there were bugs in some of the development revisions that could mangle the output). - Duplicity backups can be imported via the *experimental* command "bup import-duplicity". Please exercise caution, and let us know if you have any trouble. - Tests can be run in parallel now via "make -j check". As before, the metadata support is somewhat immature, but it seems to be holding up fairly well. Though we still need to add better support for cross-filesystem-type save/restore (which can be too noisy), etc. @ text @d5 1 a5 1 lib/bup/bup/_version.py d22 1 d34 1 d54 1 d73 1 d91 1 @ 1.5 log @Update to 0.26: This release doesn't include anything as significant as the metadata support added in 0.25, but it has quite a few bug fixes and internal improvements, in addition to these notable changes: - When --meta is specified to the fuse command, instead of generic data, the originally saved mode, uid, git, atime, mtime, and ctime will be reported for the archive paths. - When --browser is specified to the web command, a browser window will be opened for the repository. - The -x/--xdev/--one-filesystem options now include the mountpoint itself in the traversal (matching rsyc, tar, etc.). - Empty lines in --exclude-rx-from files will be ignored. Previously they would cause all paths to be excluded. - The index and restore commands now support --exclude-rx-from. - Relative filesystem --excludes like "--exclude bar" should now work. Previously --excludes had to be absolute. - The drecurse command now supports --exclude-rx and --exclude-rx-from. - The --compress option should now work for remote repositories. - Streams saved via "bup split" will now show up as a single file named "data" at the top level of the VFS, instead of as a subtree (i.e. when examined via ftp, ls, and fuse). - The ls command now supports -n, -A, -F, --file-type, --numeric-ids, and detailed -l options. - The save dates are now taken from the corresponding git commit's author date, not the committer date. - The tornado server, required by the web command, is no longer included. See the README for installation instructions. Note that the metadata support is still somewhat immature. For example, we still need to add better support for cross-filesystem-type save/restore (which is too noisy), etc. Please give this release a try and let us know what's broken. If you're new to bup, start with the README (and then HACKING if you'd like to help further): https://github.com/bup/bup/blob/master/README.md https://github.com/bup/bup/blob/master/HACKING http://anonscm.debian.org/gitweb/?p=users/rlb/bup.git;a=blob;f=README.md;hb=refs/heads/master http://anonscm.debian.org/gitweb/?p=users/rlb/bup.git;a=blob;f=HACKING;hb=refs/heads/master And although I probably sound like a broken record -- while we expect bup to work fairly well, I still don't recommend it as your sole backup strategy. I'd still suggest a periodic tar/rsync/etc. backstop. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.4 2013/12/31 11:03:12 wiz Exp $ d34 1 d71 1 @ 1.4 log @Update to 0.25: This release includes a veritable ton of work, but the biggest change is probably the addition of real (YMMV) metadata support, including hardlinks, and the ability to directly save/restore trees without tar and split/join. See bup-index(1), bup-save(1), bup-restore(1), bup-meta(1), bup-xstat(1), and the updated "Using bup" section in the README. Note though, that the metadata support really is our first pass, and there are already things that we know need fixing (i.e. better support for cross-filesystem-type save/restore (too noisy), etc.). And check the "Notes on ..." sections in the README for some platform-specific limitations. An incomplete list of other notable changes since 0.24b: - bup will no longer create ~/.bup implicitly; "bup init" is required. - "bup split" now supports a compression-level option (-#). - "bup tag" now supports "-f". - "bup ls" now supports "-a", "-s", "--human-readable", etc., and reports more information. - "bup web" now supports "--human-readable". - "bup import-rdiff-backup" has been added. - "bup cat-file" has been added. - The default "/usr" installation prefix can be overridden via PREFIX. - Python 2.4 is no longer supported. And we have at least one (likely minor) known issue: - *Very* large (i.e. probably greater than MAX_LONG), or negative filesystem timestamps may not always be handled correctly at the moment. We'll fix that soon. And related -- some of the tests may fail on FUSE filesystems. @ text @d1 1 a1 1 @@comment $NetBSD$ a58 18 lib/bup/tornado/__init__.py lib/bup/tornado/auth.py lib/bup/tornado/autoreload.py lib/bup/tornado/database.py lib/bup/tornado/escape.py lib/bup/tornado/httpclient.py lib/bup/tornado/httpserver.py lib/bup/tornado/httputil.py lib/bup/tornado/ioloop.py lib/bup/tornado/iostream.py lib/bup/tornado/locale.py lib/bup/tornado/options.py lib/bup/tornado/s3server.py lib/bup/tornado/template.py lib/bup/tornado/web.py lib/bup/tornado/websocket.py lib/bup/tornado/win32_support.py lib/bup/tornado/wsgi.py @ 1.3 log @Update to 0.25rc1. Add py-readline dependency for better 'bup ftp' support. This is the latest stable release, despite its name. Lots of bug fixes compared to previous one, but no NEWS provided. @ text @d13 1 d26 1 d34 1 d80 1 d88 1 @ 1.2 log @Install README and design document. Bump PKGREVISION. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.1.1.1 2011/05/16 13:52:56 wiz Exp $ d14 2 d22 2 d40 1 d55 1 @ 1.1 log @Initial revision @ text @d1 1 a1 1 @@comment $NetBSD$ d99 2 a100 2 @@pkgdir share/man/man1 @@pkgdir share/doc/bup @ 1.1.1.1 log @Initial import of bup-0.24b. bup is a program that backs things up. bup has a few advantages over other backup software: It uses a rolling checksum algorithm (similar to rsync) to split large files into chunks. The most useful result of this is you can backup huge virtual machine (VM) disk images, databases, and XML files incrementally, even though they're typically all in one huge file, and not use tons of disk space for multiple versions. It uses the packfile format from git (the open source version control system), so you can access the stored data even if you don't like bup's user interface. Unlike git, it writes packfiles directly (instead of having a separate garbage collection / repacking stage) so it's fast even with gratuitously huge amounts of data. bup's improved index formats also allow you to track far more filenames than git (millions) and keep track of far more objects (hundreds or thousands of gigabytes). Data is "automagically" shared between incremental backups without having to know which backup is based on which other one - even if the backups are made from two different computers that don't even know about each other. You just tell bup to back stuff up, and it saves only the minimum amount of data needed. You can back up directly to a remote bup server, without needing tons of temporary disk space on the computer being backed up. And if your backup is interrupted halfway through, the next run will pick up where you left off. And it's easy to set up a bup server: just install bup on any machine where you have ssh access. Bup can use "par2" redundancy to recover corrupted backups even if your disk has undetected bad sectors. Even when a backup is incremental, you don't have to worry about restoring the full backup, then each of the incrementals in turn; an incremental backup acts as if it's a full backup, it just takes less disk space. You can mount your bup repository as a FUSE filesystem and access the content that way, and even export it over Samba. @ text @@