head	1.4;
access;
symbols
	pkgsrc-2026Q1:1.4.0.6
	pkgsrc-2026Q1-base:1.4
	pkgsrc-2025Q4:1.4.0.4
	pkgsrc-2025Q4-base:1.4
	pkgsrc-2025Q3:1.4.0.2
	pkgsrc-2025Q3-base:1.4
	pkgsrc-2016Q2:1.2.0.20
	pkgsrc-2016Q2-base:1.2
	pkgsrc-2016Q1:1.2.0.18
	pkgsrc-2016Q1-base:1.2
	pkgsrc-2015Q4:1.2.0.16
	pkgsrc-2015Q4-base:1.2
	pkgsrc-2015Q3:1.2.0.14
	pkgsrc-2015Q3-base:1.2
	pkgsrc-2015Q2:1.2.0.12
	pkgsrc-2015Q2-base:1.2
	pkgsrc-2015Q1:1.2.0.10
	pkgsrc-2015Q1-base:1.2
	pkgsrc-2014Q4:1.2.0.8
	pkgsrc-2014Q4-base:1.2
	pkgsrc-2014Q3:1.2.0.6
	pkgsrc-2014Q3-base:1.2
	pkgsrc-2014Q2:1.2.0.4
	pkgsrc-2014Q2-base:1.2
	pkgsrc-2014Q1:1.2.0.2
	pkgsrc-2014Q1-base:1.2
	pkgsrc-2013Q4:1.1.0.12
	pkgsrc-2013Q4-base:1.1
	pkgsrc-2013Q3:1.1.0.10
	pkgsrc-2013Q3-base:1.1
	pkgsrc-2013Q2:1.1.0.8
	pkgsrc-2013Q2-base:1.1
	pkgsrc-2013Q1:1.1.0.6
	pkgsrc-2013Q1-base:1.1
	pkgsrc-2012Q4:1.1.0.4
	pkgsrc-2012Q4-base:1.1
	pkgsrc-2012Q3:1.1.0.2
	pkgsrc-2012Q3-base:1.1;
locks; strict;
comment	@# @;


1.4
date	2025.09.13.00.33.37;	author gdt;	state Exp;
branches;
next	1.3;
commitid	43w4BOMHAbfjfuaG;

1.3
date	2016.09.18.23.02.48;	author gdt;	state dead;
branches;
next	1.2;
commitid	hsrTDZe5OnoodPmz;

1.2
date	2013.12.31.11.03.12;	author wiz;	state Exp;
branches;
next	1.1;
commitid	qgvZ965eINjg7hjx;

1.1
date	2012.09.04.13.43.15;	author wiz;	state Exp;
branches;
next	;


desc
@@


1.4
log
@sysutils/bup: Work around clang judgement

clang warns if there is a -L argument that is "unused".  With -Werror,
this is an error.  pkgsrc wrappers add -L args whether they are needed
or not.  Patch out -Werror in bup's configure, to be proposed for
upstream.

Resolves build failure on macOS 15.
@
text
@$NetBSD$

Disable -Werror on test builds, to avoid running afoul of clang
complaining that a -L flag was "unused".

Sent to bup via email.  Arguably this is a clang bug, but I have no
reason to expect it to be fixed there.

--- config/configure.orig	2025-08-30 18:10:07.000000000 +0000
+++ config/configure
@@@@ -29,7 +29,7 @@@@ bup_try_c_code()
     esac
     tmpdir="$(mktemp -d "bup-try-c-compile-XXXXXXX")" || exit $?
     echo "$code" > "$tmpdir/test.c" || exit $?
-    $AC_CC -Wall -Werror $cflags -c -o "$tmpdir/test" "$tmpdir/test.c"
+    $AC_CC -Wall $cflags -c -o "$tmpdir/test" "$tmpdir/test.c"
     rc=$?
     rm -r "$tmpdir" || exit $?
     return $rc
@


1.3
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
$NetBSD: patch-config_configure,v 1.2 2013/12/31 11:03:12 wiz Exp $
d3 2
a4 1
Use PYTHON passed through from Makefile.
d6 4
a9 1
--- config/configure.orig	2013-11-11 08:52:33.000000000 +0000
d11 9
a19 9
@@@@ -42,7 +42,7 @@@@ if [ -z "$MAKE_VERSION" ]; then
 fi
 expr "$MAKE_VERSION" '>=' '3.81' || AC_FAIL "ERROR: $MAKE must be >= version 3.81"
 
-if test -z "$(bup_find_prog python '')"; then
+if test -z "$(bup_find_prog python "$PYTHON")"; then
     AC_FAIL "ERROR: unable to find python"
 fi
 
@


1.2
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
$NetBSD$
@


1.1
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
@d3 1
a3 3
Use PYTHON from environment.
Do not check for utimensat. It is found on NetBSD even though unusable
for now (20120827).
d5 1
a5 1
--- config/configure.orig	2011-06-09 03:24:45.000000000 +0000
d7 3
a9 2
@@@@ -30,7 +30,7 @@@@ expr "$MAKE_VERSION" '>=' '3.81' || AC_F
 TLOG " ok"
d11 3
a13 5
 TLOGN "checking the python"
-PYTHON=`acLookFor python`
+[ -n "$PYTHON" ] || PYTHON=`acLookFor python`
 if [ -z "$PYTHON" ]; then
     AC_FAIL " Cannot find python";
a14 7
@@@@ -59,7 +59,6 @@@@ AC_CHECK_HEADERS unistd.h
 AC_CHECK_HEADERS linux/fs.h
 AC_CHECK_HEADERS sys/ioctl.h
 
-AC_CHECK_FUNCS utimensat 
 AC_CHECK_FUNCS utimes
 AC_CHECK_FUNCS lutimes
@