2016-09-19 10:52:24 by Thomas Klausner | Files touched by this commit (3) |
Log message:
Remove unnecessary REPLACE_PYTHON lines and patch.
Add perl to run-time depends, at least one subcommand uses it.
(should perhaps be replaced, it's just for stat())
Fix path to REPLACE_PERL files.
Add rsync to BUILD_DEPENDS, it's needed for some tests.
|
2016-09-19 01:02:48 by Greg Troxel | Files touched by this commit (5) |
Log message:
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.
|
2016-07-09 15:04:18 by Thomas Klausner | Files touched by this commit (599) |
Log message:
Remove python33: adapt all packages that refer to it.
|
2016-07-09 08:39:18 by Thomas Klausner | Files touched by this commit (1068) |
Log message:
Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.
|
2016-03-10 00:53:17 by Thomas Klausner | Files touched by this commit (1) |
Log message:
Drop maintainership.
|
2015-12-05 22:26:09 by Adam Ciarcinski | Files touched by this commit (578) |
Log message:
Extend PYTHON_VERSIONS_INCOMPATIBLE to 35
|
2015-11-04 02:32:42 by Alistair G. Crooks | Files touched by this commit (499) |
Log message:
Add SHA512 digests for distfiles for sysutils category
Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
|
2015-06-12 12:52:19 by Thomas Klausner | Files touched by this commit (3152) |
Log message:
Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.
|
2015-04-27 11:17:17 by Thomas Klausner | Files touched by this commit (3) |
Log message:
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.
|
2014-09-11 08:26:22 by Thomas Klausner | Files touched by this commit (1) | |
Log message:
Remove patch that's not needed any longer after 0.26 update.
|