head	1.75;
access;
symbols
	pkgsrc-2026Q1:1.75.0.2
	pkgsrc-2026Q1-base:1.75
	pkgsrc-2025Q4:1.73.0.4
	pkgsrc-2025Q4-base:1.73
	pkgsrc-2025Q3:1.73.0.2
	pkgsrc-2025Q3-base:1.73
	pkgsrc-2025Q2:1.71.0.2
	pkgsrc-2025Q2-base:1.71
	pkgsrc-2025Q1:1.70.0.2
	pkgsrc-2025Q1-base:1.70
	pkgsrc-2024Q4:1.67.0.2
	pkgsrc-2024Q4-base:1.67
	pkgsrc-2024Q3:1.66.0.2
	pkgsrc-2024Q3-base:1.66
	pkgsrc-2024Q2:1.64.0.4
	pkgsrc-2024Q2-base:1.64
	pkgsrc-2024Q1:1.64.0.2
	pkgsrc-2024Q1-base:1.64
	pkgsrc-2023Q4:1.63.0.2
	pkgsrc-2023Q4-base:1.63
	pkgsrc-2023Q3:1.62.0.2
	pkgsrc-2023Q3-base:1.62
	pkgsrc-2023Q2:1.61.0.2
	pkgsrc-2023Q2-base:1.61
	pkgsrc-2023Q1:1.60.0.6
	pkgsrc-2023Q1-base:1.60
	pkgsrc-2022Q4:1.60.0.4
	pkgsrc-2022Q4-base:1.60
	pkgsrc-2022Q3:1.60.0.2
	pkgsrc-2022Q3-base:1.60
	pkgsrc-2022Q2:1.58.0.4
	pkgsrc-2022Q2-base:1.58
	pkgsrc-2022Q1:1.58.0.2
	pkgsrc-2022Q1-base:1.58
	pkgsrc-2021Q4:1.57.0.2
	pkgsrc-2021Q4-base:1.57
	pkgsrc-2021Q3:1.55.0.4
	pkgsrc-2021Q3-base:1.55
	pkgsrc-2021Q2:1.55.0.2
	pkgsrc-2021Q2-base:1.55
	pkgsrc-2021Q1:1.54.0.2
	pkgsrc-2021Q1-base:1.54
	pkgsrc-2020Q4:1.50.0.2
	pkgsrc-2020Q4-base:1.50
	pkgsrc-2020Q3:1.49.0.2
	pkgsrc-2020Q3-base:1.49
	pkgsrc-2020Q2:1.43.0.2
	pkgsrc-2020Q2-base:1.43
	pkgsrc-2020Q1:1.41.0.2
	pkgsrc-2020Q1-base:1.41
	pkgsrc-2019Q4:1.41.0.4
	pkgsrc-2019Q4-base:1.41
	pkgsrc-2019Q3:1.36.0.2
	pkgsrc-2019Q3-base:1.36
	pkgsrc-2019Q2:1.33.0.2
	pkgsrc-2019Q2-base:1.33
	pkgsrc-2019Q1:1.31.0.6
	pkgsrc-2019Q1-base:1.31
	pkgsrc-2018Q4:1.31.0.4
	pkgsrc-2018Q4-base:1.31
	pkgsrc-2018Q3:1.31.0.2
	pkgsrc-2018Q3-base:1.31
	pkgsrc-2018Q2:1.29.0.10
	pkgsrc-2018Q2-base:1.29
	pkgsrc-2018Q1:1.29.0.8
	pkgsrc-2018Q1-base:1.29
	pkgsrc-2017Q4:1.29.0.6
	pkgsrc-2017Q4-base:1.29
	pkgsrc-2017Q3:1.29.0.4
	pkgsrc-2017Q3-base:1.29
	pkgsrc-2017Q2:1.28.0.4
	pkgsrc-2017Q2-base:1.28
	pkgsrc-2017Q1:1.28.0.2
	pkgsrc-2017Q1-base:1.28
	pkgsrc-2016Q4:1.27.0.4
	pkgsrc-2016Q4-base:1.27
	pkgsrc-2016Q3:1.27.0.2
	pkgsrc-2016Q3-base:1.27
	pkgsrc-2016Q2:1.23.0.4
	pkgsrc-2016Q2-base:1.23
	pkgsrc-2016Q1:1.23.0.2
	pkgsrc-2016Q1-base:1.23
	pkgsrc-2015Q4:1.22.0.2
	pkgsrc-2015Q4-base:1.22
	pkgsrc-2015Q3:1.21.0.4
	pkgsrc-2015Q3-base:1.21
	pkgsrc-2015Q2:1.21.0.2
	pkgsrc-2015Q2-base:1.21
	pkgsrc-2015Q1:1.19.0.6
	pkgsrc-2015Q1-base:1.19
	pkgsrc-2014Q4:1.19.0.4
	pkgsrc-2014Q4-base:1.19
	pkgsrc-2014Q3:1.19.0.2
	pkgsrc-2014Q3-base:1.19
	pkgsrc-2014Q2:1.18.0.2
	pkgsrc-2014Q2-base:1.18
	pkgsrc-2014Q1:1.16.0.2
	pkgsrc-2014Q1-base:1.16
	pkgsrc-2013Q4:1.11.0.2
	pkgsrc-2013Q4-base:1.11
	pkgsrc-2013Q3:1.10.0.2
	pkgsrc-2013Q3-base:1.10
	pkgsrc-2013Q2:1.9.0.2
	pkgsrc-2013Q2-base:1.9
	pkgsrc-2013Q1:1.8.0.4
	pkgsrc-2013Q1-base:1.8
	pkgsrc-2012Q4:1.8.0.2
	pkgsrc-2012Q4-base:1.8
	pkgsrc-2012Q3:1.6.0.2
	pkgsrc-2012Q3-base:1.6
	pkgsrc-2012Q2:1.5.0.4
	pkgsrc-2012Q2-base:1.5
	pkgsrc-2012Q1:1.5.0.2
	pkgsrc-2012Q1-base:1.5
	pkgsrc-2011Q4:1.4.0.2
	pkgsrc-2011Q4-base:1.4
	pkgsrc-2011Q3:1.3.0.2
	pkgsrc-2011Q3-base:1.3
	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.75
date	2026.01.29.00.35.05;	author gdt;	state Exp;
branches;
next	1.74;
commitid	PAfpEYHPYaZsPdsG;

1.74
date	2025.12.30.17.40.03;	author gdt;	state Exp;
branches;
next	1.73;
commitid	PoAkkvDdOjtSssoG;

1.73
date	2025.09.13.00.33.37;	author gdt;	state Exp;
branches;
next	1.72;
commitid	43w4BOMHAbfjfuaG;

1.72
date	2025.08.30.19.41.46;	author gdt;	state Exp;
branches;
next	1.71;
commitid	43mgKX9ppqKZ2N8G;

1.71
date	2025.06.07.11.27.28;	author gdt;	state Exp;
branches;
next	1.70;
commitid	pvUdF8QWAUSA1XXF;

1.70
date	2025.01.11.01.50.31;	author gdt;	state Exp;
branches;
next	1.69;
commitid	YPuoKEyWW1UCy0FF;

1.69
date	2025.01.11.01.48.17;	author gdt;	state Exp;
branches;
next	1.68;
commitid	AywCU7k88WjRx0FF;

1.68
date	2025.01.03.00.38.37;	author gdt;	state Exp;
branches;
next	1.67;
commitid	kP0Tsy2xNGRtpYDF;

1.67
date	2024.12.11.01.19.15;	author gdt;	state Exp;
branches;
next	1.66;
commitid	ypZfy5vj01aGn1BF;

1.66
date	2024.08.26.13.57.02;	author gdt;	state Exp;
branches;
next	1.65;
commitid	0OngsDun0SSS0lnF;

1.65
date	2024.08.12.17.45.52;	author gdt;	state Exp;
branches;
next	1.64;
commitid	QNRHhhOFWV3iJylF;

1.64
date	2023.12.30.15.34.49;	author gdt;	state Exp;
branches;
next	1.63;
commitid	wxS0Sc84ZSongvSE;

1.63
date	2023.12.09.01.46.30;	author gdt;	state Exp;
branches;
next	1.62;
commitid	d4ygHGUJD7yYkJPE;

1.62
date	2023.08.14.05.25.13;	author wiz;	state Exp;
branches;
next	1.61;
commitid	LOSB79OLVxvXjIAE;

1.61
date	2023.06.18.22.35.59;	author gdt;	state Exp;
branches;
next	1.60;
commitid	xfw7UcutzABGRttE;

1.60
date	2022.06.30.11.18.49;	author nia;	state Exp;
branches;
next	1.59;
commitid	AhctUV91Vubws3KD;

1.59
date	2022.06.28.11.35.54;	author wiz;	state Exp;
branches;
next	1.58;
commitid	D2UoJrTHpoHEANJD;

1.58
date	2022.02.05.09.05.42;	author adam;	state Exp;
branches;
next	1.57;
commitid	R5yHDOFtKF7joprD;

1.57
date	2021.11.30.05.31.56;	author pho;	state Exp;
branches;
next	1.56;
commitid	gdiBFcZcNGTumMiD;

1.56
date	2021.10.26.00.19.27;	author gdt;	state Exp;
branches;
next	1.55;
commitid	IXA68WxdRTg3LfeD;

1.55
date	2021.05.24.19.54.09;	author wiz;	state Exp;
branches;
next	1.54;
commitid	qokaiStTApGMcrUC;

1.54
date	2021.03.21.13.04.49;	author gdt;	state Exp;
branches;
next	1.53;
commitid	j0OFCoElehVX1bMC;

1.53
date	2021.03.15.16.02.12;	author gdt;	state Exp;
branches;
next	1.52;
commitid	v1YrtWhnZQxScqLC;

1.52
date	2021.03.15.13.35.42;	author gdt;	state Exp;
branches;
next	1.51;
commitid	EB612Gob7u4CopLC;

1.51
date	2021.03.15.13.32.35;	author gdt;	state Exp;
branches;
next	1.50;
commitid	st00HoLSRyZxnpLC;

1.50
date	2020.12.04.20.45.41;	author nia;	state Exp;
branches;
next	1.49;
commitid	FPz71MqRX3WN0tyC;

1.49
date	2020.09.20.22.28.00;	author gdt;	state Exp;
branches;
next	1.48;
commitid	WbzVdkoLy52OZPoC;

1.48
date	2020.09.20.18.33.13;	author gdt;	state Exp;
branches;
next	1.47;
commitid	jGEQz5FZ0CvqHOoC;

1.47
date	2020.09.20.16.46.08;	author gdt;	state Exp;
branches;
next	1.46;
commitid	3yUDDOKO6kmH6OoC;

1.46
date	2020.09.20.16.44.54;	author gdt;	state Exp;
branches;
next	1.45;
commitid	FrGCeTUnnkvI4OoC;

1.45
date	2020.08.31.18.11.24;	author wiz;	state Exp;
branches;
next	1.44;
commitid	7zxRbfOkDOoxbfmC;

1.44
date	2020.08.19.13.42.52;	author pho;	state Exp;
branches;
next	1.43;
commitid	0yiImoavTUTL6GkC;

1.43
date	2020.06.16.21.12.53;	author gdt;	state Exp;
branches;
next	1.42;
commitid	KAF5Cgzu72ppFucC;

1.42
date	2020.06.16.21.09.36;	author gdt;	state Exp;
branches;
next	1.41;
commitid	2biUEqhDntXoEucC;

1.41
date	2019.11.23.21.25.12;	author gdt;	state Exp;
branches;
next	1.40;
commitid	8tukgQmL9YtLl1MB;

1.40
date	2019.11.21.17.34.06;	author gdt;	state Exp;
branches;
next	1.39;
commitid	K4EIUyXjIxUZ8KLB;

1.39
date	2019.11.21.16.19.05;	author gdt;	state Exp;
branches;
next	1.38;
commitid	GETOiftCMwfgIJLB;

1.38
date	2019.11.19.15.01.25;	author gdt;	state Exp;
branches;
next	1.37;
commitid	dHULpumzPzAMltLB;

1.37
date	2019.11.04.21.28.42;	author rillig;	state Exp;
branches;
next	1.36;
commitid	P8zvC5DaquV1ZzJB;

1.36
date	2019.09.12.00.28.47;	author gdt;	state Exp;
branches;
next	1.35;
commitid	BAyITOAQWaTJHECB;

1.35
date	2019.09.02.13.20.09;	author adam;	state Exp;
branches;
next	1.34;
commitid	JNtg51I3DnX4jrBB;

1.34
date	2019.08.11.13.23.03;	author wiz;	state Exp;
branches;
next	1.33;
commitid	Ifet9Pg6Qt99ZByB;

1.33
date	2019.04.26.13.14.14;	author maya;	state Exp;
branches;
next	1.32;
commitid	U4pISddzN4WXpRkB;

1.32
date	2019.04.25.07.33.17;	author maya;	state Exp;
branches;
next	1.31;
commitid	1FEMQBEPb9uTxHkB;

1.31
date	2018.08.22.09.46.31;	author wiz;	state Exp;
branches;
next	1.30;
commitid	YLub8g3ofvFGb6PA;

1.30
date	2018.07.03.05.03.33;	author adam;	state Exp;
branches;
next	1.29;
commitid	bH4MNADzVzoIfEIA;

1.29
date	2017.07.30.22.32.22;	author wiz;	state Exp;
branches;
next	1.28;
commitid	gjZWVQWOLKneVi1A;

1.28
date	2017.01.01.14.43.57;	author wiz;	state Exp;
branches;
next	1.27;
commitid	TmfhF2MIYbgU4hAz;

1.27
date	2016.09.19.08.52.24;	author wiz;	state Exp;
branches;
next	1.26;
commitid	4n81MRwVMwgptSmz;

1.26
date	2016.09.18.23.02.48;	author gdt;	state Exp;
branches;
next	1.25;
commitid	hsrTDZe5OnoodPmz;

1.25
date	2016.07.09.13.04.05;	author wiz;	state Exp;
branches;
next	1.24;
commitid	k9A2yv7vTRunbEdz;

1.24
date	2016.07.09.06.38.58;	author wiz;	state Exp;
branches;
next	1.23;
commitid	dlqnocGpOoXV2Cdz;

1.23
date	2016.03.09.23.53.17;	author wiz;	state Exp;
branches;
next	1.22;
commitid	6vXYbeX8HfJtH1Yy;

1.22
date	2015.12.05.21.25.58;	author adam;	state Exp;
branches;
next	1.21;
commitid	bgA0CynThkP3WNLy;

1.21
date	2015.06.12.10.51.11;	author wiz;	state Exp;
branches;
next	1.20;
commitid	B4JmCfaVUbiY38py;

1.20
date	2015.04.27.09.17.17;	author wiz;	state Exp;
branches;
next	1.19;
commitid	z7EyppXexdRF2djy;

1.19
date	2014.09.06.21.29.45;	author wiz;	state Exp;
branches;
next	1.18;
commitid	AhriHFsXyqzQzkPx;

1.18
date	2014.05.29.23.37.27;	author wiz;	state Exp;
branches;
next	1.17;
commitid	laryHfkCalgYtuCx;

1.17
date	2014.05.09.07.37.18;	author wiz;	state Exp;
branches;
next	1.16;
commitid	wfzXpL2biguCPPzx;

1.16
date	2014.03.19.17.50.00;	author gdt;	state Exp;
branches;
next	1.15;
commitid	XZJ7u8N7R3KCRktx;

1.15
date	2014.03.19.13.15.13;	author gdt;	state Exp;
branches;
next	1.14;
commitid	lFzKX9I2kcLrljtx;

1.14
date	2014.03.19.12.54.02;	author gdt;	state Exp;
branches;
next	1.13;
commitid	HYrKelRx3CXMdjtx;

1.13
date	2014.01.25.10.30.21;	author wiz;	state Exp;
branches;
next	1.12;
commitid	VOWgk3vYhVXj8umx;

1.12
date	2013.12.31.11.03.12;	author wiz;	state Exp;
branches;
next	1.11;
commitid	qgvZ965eINjg7hjx;

1.11
date	2013.12.18.23.48.22;	author wiz;	state Exp;
branches;
next	1.10;
commitid	jx3AVvJwSx71MFhx;

1.10
date	2013.09.09.14.07.59;	author wiz;	state Exp;
branches;
next	1.9;
commitid	R7Ndtjk1XwlaML4x;

1.9
date	2013.05.31.12.41.59;	author wiz;	state Exp;
branches;
next	1.8;
commitid	hIeXGcx6VfKHwMRw;

1.8
date	2012.10.23.19.50.54;	author asau;	state Exp;
branches;
next	1.7;

1.7
date	2012.10.03.21.57.36;	author wiz;	state Exp;
branches;
next	1.6;

1.6
date	2012.09.04.13.43.14;	author wiz;	state Exp;
branches;
next	1.5;

1.5
date	2012.03.15.11.53.38;	author obache;	state Exp;
branches;
next	1.4;

1.4
date	2011.12.15.00.58.14;	author gdt;	state Exp;
branches;
next	1.3;

1.3
date	2011.09.08.21.57.55;	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.75
log
@sysutils/bup: Update to 0.33.10

(Significantly, bup's tests now pass on NetBSD, with many test issues resolved.)

Upstream NEWS:

Notable changes in 0.33.10 since 0.33.9
=======================================

Bugs
----

* As noted in 0.33.8, `bup fsck` switched from symlinks to hardlinks
  to accommodate an incompatible change in `par2` 1.0's behavior.  To
  allow the use of filesystems without hardlinks, `bup` now copies the
  input files if hardlinking fails.

Thanks to (at least)
====================

Greg Troxel and Rob Browning
@
text
@# $NetBSD: Makefile,v 1.74 2025/12/30 17:40:03 gdt Exp $

DISTNAME=	bup-0.33.10
CATEGORIES=	sysutils
MASTER_SITES=	${MASTER_SITE_GITHUB:=bup/}
# bup has two problems that make packaging difficult.  One is that
# building man pages requires non-portable tools (pandoc).  The other
# is that it is hosted on github, which makes hosting tarballs
# difficult.  The combination of this leads to having a branch "man"
# in bup's git which has autogenerated man pages.  The third problem
# is that github.mk assumes that there is one distfile.

# (Note to future updating self) We would like to fetch the following files, e.g.:
#   https://github.com/bup/bup/archive/0.30.tar.gz
#   https://github.com/bup/bup/archive/28876cde4a3dac518e773860aa7969c106f5390d.tar.gz

# Upstream should have a tag, but doesn't.
# EXTRACT_SUFX default value is set too late, so using it in SITES.* fails.
EXTRACT_SUFX=		.tar.gz
MAN_TAG=		26d961455dc071f166a3f6f54e6ceb0b71cf2524
MAN_UNPACK=		bup-${MAN_TAG}
MAN_DISTFILE=		bup-man-${MAN_TAG}${EXTRACT_SUFX}
SITES.${MAN_DISTFILE}=	-${MASTER_SITE_GITHUB:=bup/bup/archive/}${MAN_TAG}${EXTRACT_SUFX}
# Upstream provides html, but we choose not to include it in the package.
#HTML_TAG=		66eccb7eb49575d006d193276018d9551ac5b4d4
DISTFILES=		${DEFAULT_DISTFILES} ${MAN_DISTFILE}

MAINTAINER=	gdt@@NetBSD.org
HOMEPAGE=	https://github.com/bup/bup
COMMENT=	Highly efficient file backup system based on the git packfile format
LICENSE=	gnu-gpl-v2

USE_LANGUAGES=	c
USE_TOOLS+=	bash gmake perl:run
HAS_CONFIGURE=	yes

# On macOS 10.13, building bup fails with defaults but builds with
# USE_CWRAPPERS=no.   The error is
#   Looking for cpp (/path/to/pkgsrc/sysutils/bup/work/.cwrapper/bin/cpp) (can't run cpp as a pipeline)

DEPENDS+=	par2-[0-9]*:../../archivers/par2
DEPENDS+=	${PYPKGPREFIX}-tornado-[0-9]*:../../www/py-tornado
DEPENDS+=	git-base-[0-9]*:../../devel/git-base
TEST_DEPENDS+=	${PYPKGPREFIX}-test-[0-9]*:../../devel/py-test
TEST_DEPENDS+=	${PYPKGPREFIX}-test-xdist-[0-9]*:../../devel/py-test-xdist
TEST_DEPENDS+=	rsync-[0-9]*:../../net/rsync

PYTHON_VERSIONS_INCOMPATIBLE=	27 # py-tornado

DIST_MANPAGES=		${WRKDIR}/${MAN_UNPACK}

ALL_ENV+=	BUP_PYTHON_CONFIG=${LOCALBASE}/bin/python${PYVERSSUFFIX}-config

# Note that tests 1) will fail on a fs mounted noatime and 2) need a
# lot of space, perhaps 1 GB.
# Tests fail on netbsd-9 because of non-portable use of script(1)
# introduced in 0.33.9.  Reported upstream by email 20250830.
TEST_TARGET=	test
# \todo Pass MAKE_JOBS into "gmake test" via -j.
TEST_ENV+=	TZ=UTC

# bup's configure is buggy and ends up with a make->make symlink.
# Whack it to something sensible.  Reported upstream 20221204.
#
# bup's Makefile is buggy in that there is no install target.  Whack
# Makefile from GNUmakefile so that the install target will be run.
# Reported upstream 20221204.
post-configure:
	cd ${WRKSRC}/config/bin && rm -f make && ln -s ${TOOLS_PATH.gmake} make
	cd ${WRKSRC} && cp -pf GNUmakefile Makefile

MAKE_FLAGS+=	PREFIX=${LOCALBASE}
MAKE_FLAGS+=	PYTHON=${PYTHONBIN}
MAKE_FLAGS+=	MANDIR=${DESTDIR}${PREFIX}/${PKGMANDIR}

# Even if converters/pandoc is installed, pretend as if it weren't.
MAKE_FLAGS+=	PANDOC=

REPLACE_BASH+=		lib/cmd/bup-import-rdiff-backup
REPLACE_BASH+=		dev/checksum
REPLACE_BASH+=		dev/compare-trees
REPLACE_BASH+=		dev/configure-sampledata
REPLACE_BASH+=		dev/force-delete
REPLACE_BASH+=		dev/git-cat-tree
REPLACE_BASH+=		dev/perf-glance
REPLACE_BASH+=		dev/prep-for-debianish-build
REPLACE_BASH+=		dev/prep-for-macos-build
REPLACE_BASH+=		dev/refresh
REPLACE_BASH+=		dev/sync-tree
REPLACE_BASH+=		dev/system-info
REPLACE_BASH+=		dev/update-checkout-info
REPLACE_BASH+=		dev/update-doc-branches
REPLACE_BASH+=		dev/validate-python
REPLACE_BASH+=		pylint
REPLACE_BASH+=		test/ext/test-cat-file
REPLACE_BASH+=		test/ext/test-command-without-init-fails
REPLACE_BASH+=		test/ext/test-comparative-split-join
REPLACE_BASH+=		test/ext/test-compression
REPLACE_BASH+=		test/ext/test-drecurse
REPLACE_BASH+=		test/ext/test-fsck
REPLACE_BASH+=		test/ext/test-fuse
REPLACE_BASH+=		test/ext/test-gc
REPLACE_BASH+=		test/ext/test-help
REPLACE_BASH+=		test/ext/test-import-duplicity
REPLACE_BASH+=		test/ext/test-import-rdiff-backup
REPLACE_BASH+=		test/ext/test-index
REPLACE_BASH+=		test/ext/test-index-check-device
REPLACE_BASH+=		test/ext/test-index-clear
REPLACE_BASH+=		test/ext/test-index-save-type-change
REPLACE_BASH+=		test/ext/test-list-idx
REPLACE_BASH+=		test/ext/test-ls
REPLACE_BASH+=		test/ext/test-ls-remote
REPLACE_BASH+=		test/ext/test-main
REPLACE_BASH+=		test/ext/test-meta
REPLACE_BASH+=		test/ext/test-misc
REPLACE_BASH+=		test/ext/test-on
REPLACE_BASH+=		test/ext/test-packsizelimit
REPLACE_BASH+=		test/ext/test-redundant-saves
REPLACE_BASH+=		test/ext/test-release-archive
REPLACE_BASH+=		test/ext/test-restore-map-owner
REPLACE_BASH+=		test/ext/test-restore-single-file
REPLACE_BASH+=		test/ext/test-rm
REPLACE_BASH+=		test/ext/test-rm-between-index-and-save
REPLACE_BASH+=		test/ext/test-save-creates-no-unrefs
REPLACE_BASH+=		test/ext/test-save-data-race
REPLACE_BASH+=		test/ext/test-save-errors
REPLACE_BASH+=		test/ext/test-save-restore
REPLACE_BASH+=		test/ext/test-save-restore-excludes
REPLACE_BASH+=		test/ext/test-save-smaller
REPLACE_BASH+=		test/ext/test-save-strip-graft
REPLACE_BASH+=		test/ext/test-save-symlink-race
REPLACE_BASH+=		test/ext/test-save-with-valid-parent
REPLACE_BASH+=		test/ext/test-sparse-files
REPLACE_BASH+=		test/ext/test-split-join
REPLACE_BASH+=		test/ext/test-tz
REPLACE_BASH+=		test/ext/test-web
REPLACE_BASH+=		test/ext/test-xdev

DOCDIR=			share/doc/${PKGBASE}

INSTALLATION_DIRS+=	${PKGMANDIR}/man1 ${DOCDIR}

post-install:
	${INSTALL_DATA} ${DIST_MANPAGES}/*.1 ${DESTDIR}${PREFIX}/${PKGMANDIR}/man1
	${INSTALL_DATA} ${WRKSRC}/DESIGN ${DESTDIR}${PREFIX}/${DOCDIR}
	${INSTALL_DATA} ${WRKSRC}/README ${DESTDIR}${PREFIX}/${DOCDIR}

.include "options.mk"

# \todo Investigate "bup ftp" crash with NetBSD editline and resolve.
.include "../../devel/readline/buildlink3.mk"
.include "../../lang/python/application.mk"
.include "../../mk/bsd.pkg.mk"
@


1.74
log
@sysutils/bup: TEST_DEPEND on py-test-xdist

This enables "gmake -j8 check" to run the (lengthy) bup tests in
parallel.

It remains to pass -j automatically from MAKE_JOBS, but this
dependency enables manual test runs to be parallelized.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.73 2025/09/13 00:33:37 gdt Exp $
d3 1
a3 2
DISTNAME=	bup-0.33.9
PKGREVISION=	1
d20 1
a20 1
MAN_TAG=		0d2bd796c937f347dd830753f82eedd2b7ad6595
@


1.73
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
@d1 1
a1 1
# $NetBSD: Makefile,v 1.72 2025/08/30 19:41:46 gdt Exp $
d46 1
d60 1
@


1.72
log
@sysutils/bup: Update to 0.33.9

Upstream lacks NEWS, but the intent is bugfixes and minor improvements.

0.33.9 adds non-portable script usage, breaking tests on NetBSD 9 and
likely other systems.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.71 2025/06/07 11:27:28 gdt Exp $
d4 1
@


1.71
log
@sysutils/bup: Remove inexplicable .sh from REPLACE_BASH

Noticed in macOS 12 arm64 bulk build.

There is no ".sh" in the sources, and I can't explain
  - why I added it in 2023-12
  - why the package builds for me and in other bulk builds

but clearly it's a bug to replace anything in files that aren't there,
so just don't.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.70 2025/01/11 01:50:31 gdt Exp $
d3 1
a3 1
DISTNAME=	bup-0.33.7
d55 2
@


1.70
log
@sysutils/bup: Fix PREFIX/LOCALBASE conflation

(Thanks to pkglint for pointing this out.)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.69 2025/01/11 01:48:17 gdt Exp $
a133 1
REPLACE_BASH+=		.sh
@


1.69
log
@sysutils/bup: Update to 0.33.7

Notable changes in 0.33.7 since 0.33.6
======================================

Bugs
----

* When `FILE` has no directory component, i.e. no `/`, `bup midx
  --check FILE` should now look in the current directory for the
  constituent indexes, rather than `/`.

* `bup` should no longer crash when opening a midx file with missing
  indexes.


Thanks to (at least)
====================

Greg Troxel, Johannes Berg, Michał Karol, and Rob Browning
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.68 2025/01/03 00:38:37 gdt Exp $
d68 1
a68 1
MAKE_FLAGS+=	PREFIX=${PREFIX}
@


1.68
log
@sysutils/bup: Update to 0.33.6

packaging:
  Advance along man page branch to catch up with previous
  releases. (Upstream uses non-portable tools, so we use built
  manpages.)

upstream NEWS:
  bugfixes
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.67 2024/12/11 01:19:15 gdt Exp $
d3 1
a3 1
DISTNAME=	bup-0.33.6
d20 1
a20 1
MAN_TAG=		e1ed3d645eadc9b01a69fbd4d11bbb03682a0d17
@


1.67
log
@sysutils/bup: Update to 0.33.5

This is a micro but it fixes serious bugs so if you use get/gc you
really need to update!

Summary of upstream NEWS:

Notable changes in 0.33.5 since 0.33.4 (incomplete)
===================================================

May require attention
---------------------

* Problems have been discovered that could have allowed the creation
  of incomplete trees or commits, for example `bup save` or `bup get`
  could have created saves with missing data.  This should no longer
  be possible, but any existing incomplete trees might also be re-used
  by `bup get` (for example), and so represent a continuing hazard.
  Note that if you've never used `bup gc` or `bup get`, then we don't
  currently believe your repositories could have been affected.

  You can detect whether you've been affected by running
  `bup-validate-object-links(1)`.  If it doesn't report any broken
  links (as `no HASH for PARENT_HASH`), then you can stop here, the
  repository should be fine.  You can also run `bup midx -af` first,
  which may speed up the validation.

  If it does report broken links, then you should run `bup gc --ignore
  missing` to completion before making any further additions to the
  repository.  But first, if you have other repositories that might
  still contain the missing objects, then you may want to try to
  retrieve them.  See "repopulate missing objects" below for details.
  `bup gc --ignore-missing` will eliminate some of the hazards and
  report at least one of the paths to each missing object.

  If `gc` doesn't report any broken paths (missing objects), then you
  can stop here, the repository should be fine.

  If `gc` does report broken paths, then you should clear the related
  indexes, e.g. `bup index --clear` or `bup on HOST index --clear`,
  etc.

  If you don't rely on `bup get` (e.g. if you only `save`) then
  clearing the index(es) should ensure that new saves will be complete
  (though existing broken saves will remain structurally broken for
  now).

  If you do rely on `bup get`, and if `gc` reports broken paths, then
  there's not yet an easy way to ensure `get` won't continue to re-use
  incomplete trees when building new saves.  For now, you could start
  a new repository (and save the old one for future repairs).

  You can try to repopulate missing objects from the source (or some
  other) repository.  To do so, you can collect a list of missing
  objects via `bup validate-object-links`:

    bup validate-object-links | tee validate-out
    grep -E '^no ' validate-out | cut -d' ' -f 2 | sort -u > missing-objects
    sed -e 's/^/--unnamed git:/' missing-objects > unnamed-objects

  and then try to retrieve the missing objects from another repository
  via `bup get`.  For example, perhaps:

    xargs bup get --source repo --unnamed --ignore-missing < unnamed-objects

  or

    xargs bup on HOST get --unnamed --ignore-missing < unnamed-objects

  After that, you can run `bup validate-object-links` to see whether
  you were able to fix all of the broken references (i.e. whether it
  still reports missing objects).

  If you have enough missing objects, it's possible xargs might split
  the argument list between `--unnamed` and its argument, causing
  `get` to fail.  If so, you can just specify an even numbered value
  for `xargs -n`, for example `xargs -n 64 bup get ...`.
  On most systems, you can choose a much larger `n`.

  If you would just like to validate some saves, you can now run `bup
  validate-ref-links SAVE...` which should be much more efficient than
  attempting a restore or joining the saves to /dev/null.

  We're also working on a command that will repair the structure of
  any existing broken trees so that commands like restore will still
  be able to work with them.

  See issue/missing-objects.md for a detailed explanation of the
  problem.  If you have pandoc and graphviz dot installed, this will
  be rendered to issue/missing-objects.html which you can open in a
  browser, or you can find it
  [here](https://bup.github.io/issue/missing-objects.html).

General
-------

* `bup validate-object-links` has been added.  This command scans the
  objects in the repository and reports any "broken links" it finds,
  i.e. any links from a tree or commit in the repository to an object
  that doesn't exist.

* `bup validate-ref-links` has been added.  This command traverses
  repository references (e.g. saves) and logs paths to missing
  objects, i.e. references from a tree or commit to an object that
  doesn't exist in the repository.  At the moment, it will report at
  least one path to each missing object; it does not attempt to find
  all of the paths.

* `bup gc` now provides `--ignore-missing` which allows a `gc`
  operation to continue after encountering objects that are missing
  from the repository.

* `bup join` now reports the path to any missing object it encounters.

Bugs
----

* `bup gc` should no longer risk leaving the repository with
  incomplete tree or commit objects -- trees or commits with
  references to objects that are no longer in the repository.

  Previously this could happen because the collection was
  probabilistic with respect to all object types, and so it could
  leave (completely orphaned) vestigial commits or trees that referred
  to objects that had been removed.  It could also do this if the
  `--threshold` caused it to keep a parent in one "live enough" pack,
  while discarding a descendant in a pack that doesn't cross the
  threshold.

  These objects can cause serious trouble because they can be re-used
  as-is (without noticing that they are incomplete) by other commands
  like `bup get`.

* `bup get` should no longer be able to leave the repository with
  incomplete trees or commits if it's interrupted at the wrong time.
  Previously it fetched objects "top down", and so if it was
  interrupted after the parent tree/commit was written to the
  repository, but before all the children were written, then the
  repository would be left with an incomplete tree.

* `bup` should always ignore midx files that refer to missing indexes.
  Previously it might not notice when objects had disappeared (via
  `gc`) which could, in particular, cause remote/client operations
  like a remote save to decide that the repository already contained
  data that it did not.

* `bup midx` `--auto` and `--force` now delete midx files that refer
  to missing indexes.

* `bup gc` should no longer throw bloom close-related exceptions when
  interrupted.

Build system
------------

* [Graphviz](https://graphviz.org) `dot` is optional, but must be
  available in order to render the figures referred to by
  issue/missing-objects.md.

Thanks to (at least)
====================

Greg Troxel, Johannes Berg, and Rob Browning
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.66 2024/08/26 13:57:02 gdt Exp $
d3 1
a3 1
DISTNAME=	bup-0.33.5
d20 1
a20 1
MAN_TAG=		fca676714d8fc3c4c76add0a5d30b4bd951e1c2f
@


1.66
log
@sysutils/bup: Update to 0.33.4

Notable changes in 0.33.4 since 0.33.3 (incomplete)
===================================================

May require attention
---------------------

* The `par2` command (invoked by `bup fsck -g`) may generate empty
  recovery files if interrupted (say via C-c).  To mitigate this, bup
  now runs `par2` in a temporary directory, and only moves the
  recovery files into place if the generation succeeds.  It will also
  look for any empty par2 files, or incomplete sets, associated with
  packfiles that it has been asked to examine.  If found, they will
  provoke an error.  See also
  https://github.com/Parchive/par2cmdline/issues/84

* Previously, any `bup on REMOTE ...` commands that attempted to read
  from standard input (for example `bup on HOST split < something` or
  `bup on HOST split --git-ids ...`) would read nothing instead of the
  original content of standard input.  Now those commands will either
  reject the invocation, or just crash when they attempt to read a
  closed stream.

* When building bup, if your version of GNU make is not named `make`,
  prefer invoking it directly (e.g. `gmake -j4 check`) instead of
  relying on the ./Makefile to redirect to GNU make.  Some non-GNU
  makes now break this redirection.  For example, if you include a
  `-j` option in your build command one of them adds a `-J` to
  `MAKEFLAGS` that GNU make rejects.  In future releases, we're likely
  to drop the redirection entirely.

Bugs
----

* `bup-config(5)` has been added, and mentions that at the moment `bup
  on REMOTE ...` incorrectly reads the `pack.packSizeLimit` from the
  `REMOTE` repository.

* `bup fsck` no longer requires a repository via `BUP_DIR`, `-d`,
  etc. when paths are provided on the command line.

Thanks to (at least)
====================

Ed Maste, Greg Troxel, Johannes Berg, and Rob Browning
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.65 2024/08/12 17:45:52 gdt Exp $
d3 1
a3 1
DISTNAME=	bup-0.33.4
@


1.65
log
@sysutils/bup: Pass explicit reference to python-config

Otherwise, if python 3.11 and 3.12 are both installed, and pkgsrc is
building for 3.12, bup's configure might find 3.11.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.64 2023/12/30 15:34:49 gdt Exp $
d3 1
a3 1
DISTNAME=	bup-0.33.3
d20 1
a20 1
MAN_TAG=		a9757d6fe3509130622a636d35e92049f9e20fce
@


1.64
log
@sysutils/bup: Update to 0.33.3

Upstream NEWS:

  bugfixes

  performance improvements (significant, but in specific
  circumstances, and low risk)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.63 2023/12/09 01:46:30 gdt Exp $
d51 2
@


1.63
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
@d1 1
a1 1
# $NetBSD: Makefile,v 1.62 2023/08/14 05:25:13 wiz Exp $
d3 1
a3 1
DISTNAME=	bup-0.33.2
@


1.62
log
@*: recursive bump for Python 3.11 as new default
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.61 2023/06/18 22:35:59 gdt Exp $
d3 1
a3 2
DISTNAME=	bup-0.32.1
PKGREVISION=	1
d20 1
a20 1
MAN_TAG=		2fe35faff1fb9c5e7b0ea357de371ac219f2cc38
d34 1
d49 1
a49 1
DOCDIR=		${WRKDIR}/${MAN_UNPACK}
d54 11
d73 60
a132 3
USE_TOOLS+=		bash gmake perl:run

CONFIGURE_ENV+=		MAKE=${TOOLS_PATH.gmake}
d134 1
a134 15
REPLACE_BASH+=		cmd/import-rdiff-backup-cmd.sh
REPLACE_BASH+=		t/compare-trees
REPLACE_BASH+=		t/configure-sampledata
REPLACE_BASH+=		t/force-delete
REPLACE_BASH+=		t/subtree-hash
REPLACE_BASH+=		t/test-cat-file.sh
REPLACE_BASH+=		t/test-command-without-init-fails.sh
REPLACE_BASH+=		t/test-index-check-device.sh
REPLACE_BASH+=		t/test-meta.sh
REPLACE_BASH+=		t/test-redundant-saves.sh
REPLACE_BASH+=		t/test-restore-single-file.sh
REPLACE_BASH+=		t/test-rm-between-index-and-save.sh
REPLACE_BASH+=		t/test-save-creates-no-unrefs.sh
REPLACE_BASH+=		t/test.sh
REPLACE_BASH+=		wvtest-bup.sh
d136 1
a136 1
INSTALLATION_DIRS+=	${PKGMANDIR}/man1 share/doc/${PKGBASE}
d139 3
a141 3
	${INSTALL_DATA} ${DOCDIR}/*.1 ${DESTDIR}${PREFIX}/${PKGMANDIR}/man1
	${INSTALL_DATA} ${WRKSRC}/DESIGN ${DESTDIR}${PREFIX}/share/doc/bup
	${INSTALL_DATA} ${WRKSRC}/README ${DESTDIR}${PREFIX}/share/doc/bup
@


1.61
log
@sysutils/bup: Update to 0.32.1

This is a bug-fix micro update.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.60 2022/06/30 11:18:49 nia Exp $
d4 1
@


1.60
log
@*: Revbump packages that use Python at runtime without a PKGNAME prefix
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.59 2022/06/28 11:35:54 wiz Exp $
d3 1
a3 2
DISTNAME=	bup-0.32
PKGREVISION=	5
@


1.59
log
@*: recursive bump for perl 5.36
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.58 2022/02/05 09:05:42 adam Exp $
d4 1
a4 1
PKGREVISION=	4
@


1.58
log
@bup: mark as not for Python 2.7
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.57 2021/11/30 05:31:56 pho Exp $
d4 1
a4 1
PKGREVISION=	3
@


1.57
log
@bup now supports Python 3

sysutils/py-fuse-bindings was the only dependency that required Python
2, which is now ported to Python 3.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.56 2021/10/26 00:19:27 gdt Exp $
d44 2
d47 1
a47 3
# TEST_DEPENDS
BUILD_DEPENDS+=	rsync-[0-9]*:../../net/rsync
PYTHON_VERSIONED_DEPENDENCIES=		test
a93 1
.include "../../lang/python/versioned_dependencies.mk"
@


1.56
log
@bup: Wrap bup's build system slightly better

Note that bup fails to build on macOS 10.13 with cwrappers (not really
understood).
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.55 2021/05/24 19:54:09 wiz Exp $
d4 1
a4 1
PKGREVISION=	2
a48 2
PYTHON_VERSIONS_ACCEPTED=	27	# py-fuse-bindings

@


1.55
log
@*: recursive bump for perl 5.34
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.54 2021/03/21 13:04:49 gdt Exp $
d4 1
a4 1
PKGREVISION=	1
d34 7
d65 2
a66 1
REPLACE_PERL+=		wvtest
@


1.54
log
@sysutils/bup: Use VERSIONED_DEPENDENCIES for py-test
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.53 2021/03/15 16:02:12 gdt Exp $
d4 1
@


1.53
log
@sysutils/bup: Update to 0.32

(This commit message rides a trivial comment change, and is what
should have been on the 0.32 update earlier.  Thanks again to wiz who
amazingly reads all the commit messages carefully.)

Notable changes in 0.32 since 0.31)
===================================

* Python 3 is now preferred.  Python 2 support is deprecated, and 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.

  At the moment, ./configure doesn't explicitly look for any python
  newer than python3.8 by default (though one might be selected by the
  eventual python3 fallback).  If desired, you can explicitly select a
  version like this:

      PYTHON=python3.9 ./configure

* With Python 3.9, the command line reported in tools like `ps` and
  `top` will be `python...` rather than `bup...`.  This was caused by
  an upstream change that appears to have been reverted.  We're likely
  to avoid the issue entirely in a future relese.

Bugs
----

* A number of Python 3 compatibility problems have been fixed.

* `bup web` should no longer crash when attempting to listen on IPV6
  interfaces.

* `bup restore -vv` should no longer crash when printing paths with
  Python 3.

* `bup --prune-older --pretend` should format the plus/minus lines
  correctly now.

* The `TTY_WIDTH` should now be correctly propagated to subprocesses
  and remotes..

* Errors encountered while writing packfiles should be handled more
  carefully.

* Some issues with the handling of integral type signs and sizes on
  the C side have been fixed.

Build and install
-----------------

* The tests are now handled by pytest.  See the
  [README](../README#getting-started) for the additional dependency
  information and further instructions.

Thanks to (at least)
====================

Christian Brabandt, Greg Troxel, Gustavo Goretkin, Jean-Paul Marmorat,
Johannes Berg, Karl-Philipp Richter, Rob Browning, and danpawlik
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.52 2021/03/15 13:35:42 gdt Exp $
d39 1
a39 1
BUILD_DEPENDS+=	${PYPKGPREFIX}-test-[0-9]*:../../devel/py-test
d87 1
@


1.52
log
@sysutils/bup: Add py-test as pseudo-TEST_DEPENDS
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.51 2021/03/15 13:32:35 gdt Exp $
d13 1
a13 1
# (Note to future updating self) We would like to fetch the following files:
@


1.51
log
@=> Bootstrap dependency digest>=20010302: found digest-20190127
=> Checksum SHA1 OK for bup-0.32.tar.gz
=> Checksum RMD160 OK for bup-0.32.tar.gz
=> Checksum SHA512 OK for bup-0.32.tar.gz
=> Checksum SHA1 OK for bup-man-3ba5796ca63d291c8389ffae8db9e69c65787b36.tar.gz
=> Checksum RMD160 OK for bup-man-3ba5796ca63d291c8389ffae8db9e69c65787b36.tar.gz
=> Checksum SHA512 OK for bup-man-3ba5796ca63d291c8389ffae8db9e69c65787b36.tar.gz
work -> /tmp/work/sysutils/bup/work
===> Installing dependencies for bup-0.32
==========================================================================
The supported build options for bup are:

	fuse

You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or the following variable.  Its current value is shown:

	PKG_OPTIONS.bup (not defined)

==========================================================================
==========================================================================
The following variables will affect the build process of this package,
bup-0.32.  Their current value is shown below:

        * PYTHON_VERSION_DEFAULT = 38

Based on these variables, the following variables have been set:

        * PYPACKAGE = python27
        * TERMCAP_TYPE = termcap

You may want to abort the process now with CTRL-C and change the value
of variables in the first group before continuing.  Be sure to run
`/usr/bin/make clean' after the changes.
==========================================================================
=> Tool dependency bash-[0-9]*: found bash-5.1.4
=> Tool dependency gmake>=3.81: found gmake-4.2.1nb1
=> Tool dependency ccache-[0-9]*: found ccache-3.7.12
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency rsync-[0-9]*: found rsync-3.2.3
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
=> Full dependency par2-[0-9]*: found par2-0.8.1
=> Full dependency py27-tornado-[0-9]*: found py27-tornado-5.1.1
=> Full dependency git-base-[0-9]*: found git-base-2.30.1
=> Full dependency perl>=5.0: found perl-5.32.1
=> Full dependency readline>=6.0: found readline-8.1
=> Full dependency python27>=2.7.1nb2: found python27-2.7.18nb3
===> Checking for vulnerabilities in bup-0.32
===> Overriding tools for bup-0.32
===> Extracting for bup-0.32
===> Patching for bup-0.32
=> Applying pkgsrc patches for bup-0.32
=> Verifying /home/n0/gdt/pkgsrc-current/pkgsrc/sysutils/bup/patches/patch-lib_bup_bupsplit.h
**************************************
Ignoring patch file /home/n0/gdt/pkgsrc-current/pkgsrc/sysutils/bup/patches/patch-lib_bup_bupsplit.h: no checksum found
**************************************
=> Verifying /home/n0/gdt/pkgsrc-current/pkgsrc/sysutils/bup/patches/patch-lib_bup_hashsplit.py
**************************************
Ignoring patch file /home/n0/gdt/pkgsrc-current/pkgsrc/sysutils/bup/patches/patch-lib_bup_hashsplit.py: no checksum found
**************************************
===> Creating toolchain wrappers for bup-0.32
===> Configuring for bup-0.32
=> Replacing bash interpreter in cmd/import-rdiff-backup-cmd.sh t/compare-trees t/configure-sampledata t/force-delete t/subtree-hash t/test-cat-file.sh t/test-command-without-init-fails.sh t/test-index-check-device.sh t/test-meta.sh t/test-redundant-saves.sh t/test-restore-single-file.sh t/test-rm-between-index-and-save.sh t/test-save-creates-no-unrefs.sh t/test.sh wvtest-bup.sh.
WARNING: [replace-interpreter] Skipping non-existent file "t/compare-trees".
WARNING: [replace-interpreter] Skipping non-existent file "t/configure-sampledata".
WARNING: [replace-interpreter] Skipping non-existent file "t/force-delete".
WARNING: [replace-interpreter] Skipping non-existent file "t/subtree-hash".
WARNING: [replace-interpreter] Skipping non-existent file "t/test-cat-file.sh".
WARNING: [replace-interpreter] Skipping non-existent file "t/test-command-without-init-fails.sh".
WARNING: [replace-interpreter] Skipping non-existent file "t/test-index-check-device.sh".
WARNING: [replace-interpreter] Skipping non-existent file "t/test-meta.sh".
WARNING: [replace-interpreter] Skipping non-existent file "t/test-redundant-saves.sh".
WARNING: [replace-interpreter] Skipping non-existent file "t/test-restore-single-file.sh".
WARNING: [replace-interpreter] Skipping non-existent file "t/test-rm-between-index-and-save.sh".
WARNING: [replace-interpreter] Skipping non-existent file "t/test-save-creates-no-unrefs.sh".
WARNING: [replace-interpreter] Skipping non-existent file "t/test.sh".
INFO: [replace-interpreter] Nothing changed in wvtest-bup.sh.
=> Replacing Perl interpreter in wvtest.
WARNING: [replace-interpreter] Skipping non-existent file "wvtest".
=> Checking for portability problems in extracted files
===> Building for bup-0.32
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Warning: pandoc not found; skipping manpage generation
MAKE="/usr/pkg/bin/gmake" ./configure
Makefile:67: warning: undefined variable 'bup_readline_ldflags'
Configuring for [bup]
Looking for cpp (/tmp/work/sysutils/bup/work/.cwrapper/bin/cpp) ok
checking for install (/tmp/work/sysutils/bup/work/.tools/bin/install)
checking the C compiler (gcc) ok
ignoring bogus LDFLAGS="-L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib "
checking for make (/usr/pkg/bin/gmake)
checking for git (/usr/pkg/bin/git)
checking for header sys/stat.h (found)
checking for header sys/types.h (found)
checking for header unistd.h (found)
checking for header sys/mman.h (found)
checking for header linux/fs.h (not found)
checking for header sys/ioctl.h (found)
checking for the utimensat function (found)
checking for the utimes function (found)
checking for the lutimes function (found)
checking for __builtin_mul_overflow (found)
checking for the mincore function (found)
checking for MINCORE_INCORE (not found)
checking mincore buf type (char)
checking for readline (yes)
checking that struct stat has a st_atim field (yes)
checking that struct stat has a st_mtim field (yes)
checking that struct stat has a st_ctim field (yes)
checking that struct stat has a st_atimensec field (yes)
checking that struct stat has a st_mtimensec field (yes)
checking that struct stat has a st_ctimensec field (yes)
checking that struct tm has a tm_gmtoff field (yes)
checking for libacl (yes)
checking for header sys/acl.h (not found)
checking for header acl/libacl.h (not found)
checking for the acl_get_file function (not found)
checking for the acl_from_text function (not found)
checking for the acl_set_file function (not found)
checking for the acl_extended_file function (not found)
checking for the acl_to_any_text function (not found)
checking for complete acl support (no)
looking for sed (/tmp/work/sysutils/bup/work/.tools/bin/sed)
generating config.vars

found: python (/usr/pkg/bin/python2.7, Python 2.7.18)
found: git (/usr/pkg/bin/git, (git version 2.30.1)
found: readline support (e.g. bup ftp)
not found: POSIX ACL support

fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Warning: pandoc not found; skipping manpage generation
cd lib/bup && /tmp/work/sysutils/bup/work/bup-0.32/config/bin/python csetup.py build "-D_FILE_OFFSET_BITS=64  -Wno-unknown-pragmas -Wsign-compare -O2 -Wall -Werror -Wformat=2 -O2 -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include" "-L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib -lreadline"
running build
running build_ext
building '_helpers' extension
creating build
creating build/temp.netbsd-9.1_STABLE-amd64-2.7
gcc -fno-strict-aliasing -O2 -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -I/usr/pkg/include -DNDEBUG -O2 -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -I/usr/pkg/include -D_FILE_OFFSET_BITS=64 -Wno-unknown-pragmas -Wsign-compare -O2 -Wall -Werror -Wformat=2 -O2 -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include -I/usr/include -fPIC -I/usr/pkg/include/python2.7 -c _helpers.c -o build/temp.netbsd-9.1_STABLE-amd64-2.7/_helpers.o -D_FILE_OFFSET_BITS=64 -Wno-unknown-pragmas -Wsign-compare -O2 -Wall -Werror -Wformat=2 -O2 -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include
gcc -fno-strict-aliasing -O2 -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -I/usr/pkg/include -DNDEBUG -O2 -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -I/usr/pkg/include -D_FILE_OFFSET_BITS=64 -Wno-unknown-pragmas -Wsign-compare -O2 -Wall -Werror -Wformat=2 -O2 -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include -I/usr/include -fPIC -I/usr/pkg/include/python2.7 -c bupsplit.c -o build/temp.netbsd-9.1_STABLE-amd64-2.7/bupsplit.o -D_FILE_OFFSET_BITS=64 -Wno-unknown-pragmas -Wsign-compare -O2 -Wall -Werror -Wformat=2 -O2 -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include
creating build/lib.netbsd-9.1_STABLE-amd64-2.7
gcc -shared -L/tmp/work/lang/python27/work/Python-2.7.18 -pthread -L/usr/lib -Wl,-R/usr/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/X11R7/lib -Wl,-R/usr/X11R7/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib -lreadline -D_FILE_OFFSET_BITS=64 -Wno-unknown-pragmas -Wsign-compare -O2 -Wall -Werror -Wformat=2 -O2 -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include -I/usr/include build/temp.netbsd-9.1_STABLE-amd64-2.7/_helpers.o build/temp.netbsd-9.1_STABLE-amd64-2.7/bupsplit.o -L/usr/pkg/lib -lpython2.7 -o build/lib.netbsd-9.1_STABLE-amd64-2.7/_helpers.so -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib -lreadline -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib -lreadline
ld: /tmp/work/sysutils/bup/work/.buildlink/lib/libpython2.7.so: warning: warning: tmpnam() possibly used unsafely, use mkstemp() or mkdtemp()
ld: /tmp/work/sysutils/bup/work/.buildlink/lib/libpython2.7.so: warning: warning: tempnam() possibly used unsafely, use mkstemp() or mkdtemp()
/tmp/work/sysutils/bup/work/bup-0.32/config/bin/python -c \
  "import glob; assert(len(glob.glob('lib/bup/build/*/_helpers*.so')) == 1)"
cp lib/bup/build/*/_helpers*.so "lib/bup/_helpers.so"
rm -f cmd/bup-get
ln -s get-cmd.py cmd/bup-get
rm -f cmd/bup-tag
ln -s tag-cmd.py cmd/bup-tag
rm -f cmd/bup-gc
ln -s gc-cmd.py cmd/bup-gc
rm -f cmd/bup-ls
ln -s ls-cmd.py cmd/bup-ls
rm -f cmd/bup-random
ln -s random-cmd.py cmd/bup-random
rm -f cmd/bup-fsck
ln -s fsck-cmd.py cmd/bup-fsck
rm -f cmd/bup-version
ln -s version-cmd.py cmd/bup-version
rm -f cmd/bup-ftp
ln -s ftp-cmd.py cmd/bup-ftp
rm -f cmd/bup-features
ln -s features-cmd.py cmd/bup-features
rm -f cmd/bup-meta
ln -s meta-cmd.py cmd/bup-meta
rm -f cmd/bup-fuse
ln -s fuse-cmd.py cmd/bup-fuse
rm -f cmd/bup-margin
ln -s margin-cmd.py cmd/bup-margin
rm -f cmd/bup-on--server
ln -s on--server-cmd.py cmd/bup-on--server
rm -f cmd/bup-index
ln -s index-cmd.py cmd/bup-index
rm -f cmd/bup-memtest
ln -s memtest-cmd.py cmd/bup-memtest
rm -f cmd/bup-import-duplicity
ln -s import-duplicity-cmd.py cmd/bup-import-duplicity
rm -f cmd/bup-restore
ln -s restore-cmd.py cmd/bup-restore
rm -f cmd/bup-daemon
ln -s daemon-cmd.py cmd/bup-daemon
rm -f cmd/bup-midx
ln -s midx-cmd.py cmd/bup-midx
rm -f cmd/bup-help
ln -s help-cmd.py cmd/bup-help
rm -f cmd/bup-server
ln -s server-cmd.py cmd/bup-server
rm -f cmd/bup-web
ln -s web-cmd.py cmd/bup-web
rm -f cmd/bup-xstat
ln -s xstat-cmd.py cmd/bup-xstat
rm -f cmd/bup-join
ln -s join-cmd.py cmd/bup-join
rm -f cmd/bup-rm
ln -s rm-cmd.py cmd/bup-rm
rm -f cmd/bup-bloom
ln -s bloom-cmd.py cmd/bup-bloom
rm -f cmd/bup-damage
ln -s damage-cmd.py cmd/bup-damage
rm -f cmd/bup-split
ln -s split-cmd.py cmd/bup-split
rm -f cmd/bup-list-idx
ln -s list-idx-cmd.py cmd/bup-list-idx
rm -f cmd/bup-save
ln -s save-cmd.py cmd/bup-save
rm -f cmd/bup-tick
ln -s tick-cmd.py cmd/bup-tick
rm -f cmd/bup-init
ln -s init-cmd.py cmd/bup-init
rm -f cmd/bup-prune-older
ln -s prune-older-cmd.py cmd/bup-prune-older
rm -f cmd/bup-cat-file
ln -s cat-file-cmd.py cmd/bup-cat-file
rm -f cmd/bup-drecurse
ln -s drecurse-cmd.py cmd/bup-drecurse
rm -f cmd/bup-on
ln -s on-cmd.py cmd/bup-on
rm -f cmd/bup-mux
ln -s mux-cmd.py cmd/bup-mux
rm -f cmd/bup-import-rdiff-backup
ln -s import-rdiff-backup-cmd.sh cmd/bup-import-rdiff-backup
rm -f cmd/bup-import-rsnapshot
ln -s import-rsnapshot-cmd.sh cmd/bup-import-rsnapshot
dev/configure-sampledata --setup
*** Please use pkgtools/verifypc to sanity check dependencies.
===> Installing for bup-0.32
=> Generating pre-install file lists
=> Creating installation directories
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Warning: pandoc not found; skipping manpage generation
install -d /tmp/work/sysutils/bup/work/.destdir/usr/pkg/bin \
	/tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/bup /tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/cmd \
	/tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/web /tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/web/static
test -z "" || install -d /tmp/work/sysutils/bup/work/.destdir/tmp/work/sysutils/bup/work/.destdir/usr/pkg/man/man1
test -z "" || install -m 0644  /tmp/work/sysutils/bup/work/.destdir/tmp/work/sysutils/bup/work/.destdir/usr/pkg/man/man1
test -z "" || install -d /tmp/work/sysutils/bup/work/.destdir/usr/pkg/share/doc/bup
test -z "" || install -m 0644  /tmp/work/sysutils/bup/work/.destdir/usr/pkg/share/doc/bup
dev/install-python-script lib/cmd/bup "/tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/cmd/bup"
set -e; \
for cmd in $(ls cmd/bup-*); do \
  dev/install-python-script "$cmd" "/tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/$cmd"; \
done
cd "/tmp/work/sysutils/bup/work/.destdir/usr/pkg/bin" && \
  ln -sf "$(/usr/pkg/bin/python2.7 -c 'import os; print(os.path.relpath("/tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/cmd/bup"))')"
set -e; \
install -pm 0644 \
	lib/bup/*.py \
	/tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/bup
install -pm 0755 \
	lib/bup/*.so \
	/tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/bup
install -pm 0644 \
	lib/web/static/* \
	/tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/web/static/
install -pm 0644 \
	lib/web/*.html \
	/tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/web/
if test -e lib/bup/checkout_info.py; then \
    install -pm 0644 lib/bup/checkout_info.py \
        /tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/bup/source_info.py; \
else \
    ! grep -qF '$Format' lib/bup/source_info.py; \
    install -pm 0644 lib/bup/source_info.py /tmp/work/sysutils/bup/work/.destdir/usr/pkg/lib/bup/bup/; \
fi
/usr/bin/install -c -o gdt -g users -m 644 /tmp/work/sysutils/bup/work/bup-3ba5796ca63d291c8389ffae8db9e69c65787b36/*.1 /tmp/work/sysutils/bup/work/.destdir/usr/pkg/man/man1
/usr/bin/install -c -o gdt -g users -m 644 /tmp/work/sysutils/bup/work/bup-0.32/DESIGN /tmp/work/sysutils/bup/work/.destdir/usr/pkg/share/doc/bup
/usr/bin/install -c -o gdt -g users -m 644 /tmp/work/sysutils/bup/work/bup-0.32/README /tmp/work/sysutils/bup/work/.destdir/usr/pkg/share/doc/bup
=> Automatic manual page handling
=> Generating post-install file lists
=> Checking file-check results for bup-0.32
=> Checking for non-existent script interpreters in bup-0.32
=> Checking file permissions in bup-0.32
=> Checking for missing run-time search paths in bup-0.32
=> Checking for work-directory references in bup-0.32
=> Creating binary package /tmp/work/sysutils/bup/work/.packages/bup-0.32.tgz
===> Building binary package for bup-0.32
=> Creating binary package /home/n0/gdt/pkgsrc-current/pkgsrc/packages/All/bup-0.32.tgz
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.50 2020/12/04 20:45:41 nia Exp $
d39 1
@


1.50
log
@Revbump packages with a runtime Python dep but no version prefix.

For the Python 3.8 default switch.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.49 2020/09/20 22:28:00 gdt Exp $
d3 1
a3 2
DISTNAME=	bup-0.31
PKGREVISION=	2
d20 1
a20 1
MAN_TAG=		3ba5796ca63d291c8389ffae8db9e69c65787b36
@


1.49
log
@sysutils/bup: Update man page tarball for 0.31
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.48 2020/09/20 18:33:13 gdt Exp $
d4 1
a4 1
PKGREVISION=	1
@


1.48
log
@sysutils/bup: Directly include GNU readline

I was thinking of this as "needs a readline and happens to need GNU
this minute" but mk/readline.buildlink3.mk is clear that it should not
be used this way.  NFCI.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.47 2020/09/20 16:46:08 gdt Exp $
d4 1
d18 1
a18 1
# \todo Update man pages to 0.31.
d21 1
a21 1
MAN_TAG=		bd52b8fffc37788fc00071a8e46842e60ef30926
@


1.47
log
@sysutils/bup: Add todo notes

- man pages
- resolve 'bup ftp' crash with NetBSD editline
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.46 2020/09/20 16:44:54 gdt Exp $
d84 1
a84 2
READLINE_DEFAULT=	readline
.include "../../mk/readline.buildlink3.mk"
@


1.46
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
# $NetBSD: Makefile,v 1.45 2020/08/31 18:11:24 wiz Exp $
d17 1
d83 1
@


1.45
log
@*: bump PKGREVISION for perl-5.32.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.44 2020/08/19 13:42:52 pho Exp $
d3 1
a3 2
DISTNAME=	bup-0.30.1
PKGREVISION=	1
a32 1
DEPENDS+=	${PYPKGPREFIX}-readline-[0-9]*:../../devel/py-readline
d82 2
@


1.44
log
@Fix a build failure that occurs when converters/pandoc is installed

When it's installed the Makefile builds and installs HTML files too, and therefore the PLIST test doesn't pass.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.43 2020/06/16 21:12:53 gdt Exp $
d4 1
@


1.43
log
@sysutils/bup: Whitespace hygiene

As noticed by pkglint.  NFCI.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.42 2020/06/16 21:09:36 gdt Exp $
d52 3
@


1.42
log
@sysutils/bup: Update to 0.30.1

(0.30.1 is a bug fix release)


Notable changes in 0.30.1 as compared to 0.30
=============================================

May require attention
---------------------

* Previous versions of bup might have saved filesystem directories
  with incorrect metadata, but the file contents should be fine.  This
  could have happened if bup encountered an error while trying to read
  the metadata for one of the files in a directory, or if bup were
  asked to save two different files with the same name to the same
  destination directory (e.g. via the strip/graft options).  In cases
  where this has happened bup may present either generic or incorrect
  metadata for some of the paths in the affected directory.

* The way `bup index --fake-valid` works has been made to match the
  documentation in the man page so that it can actually be used for
  the stated purpose (of avoiding 'boring' files.)

General
-------

* bup should more accurately recognize git versions.  Previously, for
  example, it would reject relase candidates like "1.5.2-rc3"
  or (apparently) "1.5.2-rc3 (something ...)".

* When `BUP_ASSUME_GIT_VERSION_IS_FINE` is set to true, yes or 1 in
  the environment,  bup will assume the version of git that's
  available in the `PATH` is acceptable, and skip the version check.

Bugs
----

(several)

Build system
------------

* The automated tests have moved from FreeBSD 11.2 to 12.1.

* t/test-fuse should be more portable.  In particular, a compatibility
  issue with Fedora 31 has been fixed, and it should be less affected
  by local timezone variances.

* Some internal build dependencies have been fixed.

Thanks to (at least)
====================

Aidan Hobson Sayers, Greg Troxel, Johannes Berg, Luca Carlon, Reinier
Maas, Rob Browning, and Wyatt Alt
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.41 2019/11/23 21:25:12 gdt Exp $
d17 6
a22 9
# EXTRACT_SUFX is set too late, so using it in SITES.* fails.
EXTRACT_SUFX=  .tar.gz
MAN_TAG=	bd52b8fffc37788fc00071a8e46842e60ef30926
MAN_UNPACK=	bup-${MAN_TAG}
MAN_DISTFILE=	bup-man-${MAN_TAG}${EXTRACT_SUFX}
SITES.${MAN_DISTFILE}= -${MASTER_SITE_GITHUB:=bup/bup/archive/}${MAN_TAG}${EXTRACT_SUFX}

DISTFILES=     ${DEFAULT_DISTFILES} ${MAN_DISTFILE}

d24 2
a25 1
#HTML_TARBALL=	66eccb7eb49575d006d193276018d9551ac5b4d4
@


1.41
log
@sysutils/bup: Deal with sha1-named distfile better

Use a reasonable local name to deal with ${sha1}.tar.gz, instead of
DISTDIR.  Thanks to rillig@@ for the hint.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.40 2019/11/21 17:34:06 gdt Exp $
d3 1
a3 1
DISTNAME=	bup-0.30
d19 1
a19 1
MAN_TAG=	28876cde4a3dac518e773860aa7969c106f5390d
@


1.40
log
@sysutils/bup: Resolve man tarball fetching

Define EXTRACT_SUFX explicitly, so that it is set when setting
SITES.*.

Thanks to tnn@@ for explaining this and rillig@@ for other hints.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.39 2019/11/21 16:19:05 gdt Exp $
a15 4
# We use a subdir to isolate the man distfile that is named with a
# SHA1, so that one can readily understand to which package the file
# belongs (and the main file, which is not necessary but not harmful).
DIST_SUBDIR=	bup		
d21 2
a22 2
MAN_DISTFILE=	${MAN_TAG}${EXTRACT_SUFX}
SITES.${MAN_DISTFILE}= -${MASTER_SITE_GITHUB:=bup/bup/archive/}${MAN_DISTFILE}
@


1.39
log
@sysutils/bup: Workarounds for dealing with haskell, github, github.mk

github.mk presumes that there is one distfile, but bup has two because
it uses pandoc which uses haskell.  Set variables that should result
in fetching both of them.  Because this does not work, I have put a
copy of the man tarball at MASTER_SITE_BACKUP.

(No PKGREVISION++ because if you had the distfiles before you'll get
the same binary package now.)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.38 2019/11/19 15:01:25 gdt Exp $
d13 1
a13 1
# We would like to fetch the following files:
d18 1
a18 1
# belongs.
d21 2
a22 8
# This should not be necessary, as it is defaulted by github.mk, but
# that only works if DISTFILES is empty.
DISTFILES+=	${DISTNAME}${EXTRACT_SUFX}

# The SITES assignment does not work, perhaps because it is overridden
# elsewhere.  As a workaround, the distfile is at
# ${MASTER_SITE_BACKUP}.
# \todo Fix fetching.
d26 3
a28 2
SITES.${MAN_DISTFILE}=	${MASTER_SITES:=${GITHUB_PROJECT}/archive/${MAN_DISTFILE}}
DISTFILES+=	${MAN_DISTFILE}
@


1.38
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
# $NetBSD: Makefile,v 1.37 2019/11/04 21:28:42 rillig Exp $
d10 2
a11 2
# in bup's git which has autogenerated man pages.
DISTFILES=	${DISTNAME}${EXTRACT_SUFX}
d13 21
a33 4
# Upstream's 0.30 docs do not have a tag.
MAN_TARBALL=	28876cde4a3dac518e773860aa7969c106f5390d
MAN_UNPACK=	bup-${MAN_TARBALL}
DISTFILES+=	${MAN_TARBALL}${EXTRACT_SUFX}
@


1.37
log
@sysutils: align variable assignments

pkglint -Wall -F --only aligned --only indent -r

Manually excluded consolekit and dc-tools since pkglint didn't get the
formatting correct.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.36 2019/09/12 00:28:47 gdt Exp $
d3 1
a3 1
DISTNAME=	bup-0.29.3
d10 1
a10 3
# in bup's git which has autogenerated man pages.  For now, we created
# a bup-man tarball that contains the built man pages in a bup-man
# directory, and host it at MASTER_SITES_LOCAL.
d12 8
a19 3
# Upstream has not created bup-man-0.29.3
#DISTFILES+=	${DISTNAME:S/bup/bup-man/}${EXTRACT_SUFX}
DISTFILES+=	bup-man-0.28.1${EXTRACT_SUFX}
d34 1
a34 1
PYTHON_VERSIONS_ACCEPTED=	27 # py-fuse-bindings
d36 1
a36 1
DOCDIR=		${WRKDIR}/bup-man
d38 2
@


1.36
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
# $NetBSD: Makefile,v 1.35 2019/09/02 13:20:09 adam Exp $
d31 1
a31 1
PYTHON_VERSIONS_ACCEPTED=	 27 # py-fuse-bindings
@


1.35
log
@Changed PYTHON_VERSIONS_INCOMPATIBLE to PYTHON_VERSIONS_ACCEPTED; needed for future Python 3.8
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.34 2019/08/11 13:23:03 wiz Exp $
d3 1
a3 2
DISTNAME=	bup-0.28.1
PKGREVISION=	3
d13 4
a16 1
DISTFILES=	${DISTNAME}${EXTRACT_SUFX} ${DISTNAME:S/bup/bup-man/}${EXTRACT_SUFX}
@


1.34
log
@Bump PKGREVISIONs for perl 5.30.0
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.33 2019/04/26 13:14:14 maya Exp $
d29 1
a29 1
PYTHON_VERSIONS_INCOMPATIBLE=	 36 37 # py-fuse-bindings
@


1.33
log
@Omit mentions of python 34 and 35, after those were removed.

- Includes some whitespace changes, to be handled in a separate commit.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.32 2019/04/25 07:33:17 maya Exp $
d4 1
a4 1
PKGREVISION=	2
@


1.32
log
@PKGREVISION bump for anything using python without a PYPKGPREFIX.

This is a semi-manual PKGREVISION bump.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.31 2018/08/22 09:46:31 wiz Exp $
d29 1
a29 1
PYTHON_VERSIONS_INCOMPATIBLE=	34 35 36 37 # py-fuse-bindings
@


1.31
log
@Recursive bump for perl5-5.28.0
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.30 2018/07/03 05:03:33 adam Exp $
d4 1
a4 1
PKGREVISION=	1
@


1.30
log
@extend PYTHON_VERSIONS_ for Python 3.7
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.29 2017/07/30 22:32:22 wiz Exp $
d4 1
@


1.29
log
@Switch github HOMEPAGEs to https.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.28 2017/01/01 14:43:57 wiz Exp $
d28 1
a28 1
PYTHON_VERSIONS_INCOMPATIBLE=	34 35 36 # py-fuse-bindings
@


1.28
log
@Add python-3.6 to incompatible versions.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.27 2016/09/19 08:52:24 wiz Exp $
d16 1
a16 1
HOMEPAGE=	http://github.com/bup/bup
@


1.27
log
@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.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.26 2016/09/18 23:02:48 gdt Exp $
d28 1
a28 1
PYTHON_VERSIONS_INCOMPATIBLE=	34 35 # py-fuse-bindings
@


1.26
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: Makefile,v 1.25 2016/07/09 13:04:05 wiz Exp $
d25 3
d38 2
a39 49
USE_TOOLS+=		bash gmake perl
REPLACE_PERL=		format-subst.pl wvtestrun

# In 0.28.1, there is "bup-python" which calls the python found by
# configure.  Arguably many of these are no longer necessary.
REPLACE_PYTHON+=	cmd/bloom-cmd.py
REPLACE_PYTHON+=	cmd/cat-file-cmd.py
REPLACE_PYTHON+=	cmd/daemon-cmd.py
REPLACE_PYTHON+=	cmd/damage-cmd.py
REPLACE_PYTHON+=	cmd/drecurse-cmd.py
REPLACE_PYTHON+=	cmd/fsck-cmd.py
REPLACE_PYTHON+=	cmd/ftp-cmd.py
REPLACE_PYTHON+=	cmd/fuse-cmd.py
REPLACE_PYTHON+=	cmd/help-cmd.py
REPLACE_PYTHON+=	cmd/import-duplicity-cmd.py
REPLACE_PYTHON+=	cmd/index-cmd.py
REPLACE_PYTHON+=	cmd/init-cmd.py
REPLACE_PYTHON+=	cmd/join-cmd.py
REPLACE_PYTHON+=	cmd/list-idx-cmd.py
REPLACE_PYTHON+=	cmd/ls-cmd.py
REPLACE_PYTHON+=	cmd/margin-cmd.py
REPLACE_PYTHON+=	cmd/memtest-cmd.py
REPLACE_PYTHON+=	cmd/meta-cmd.py
REPLACE_PYTHON+=	cmd/midx-cmd.py
REPLACE_PYTHON+=	cmd/mux-cmd.py
REPLACE_PYTHON+=	cmd/newliner-cmd.py
REPLACE_PYTHON+=	cmd/on--server-cmd.py
REPLACE_PYTHON+=	cmd/on-cmd.py
REPLACE_PYTHON+=	cmd/random-cmd.py
REPLACE_PYTHON+=	cmd/restore-cmd.py
REPLACE_PYTHON+=	cmd/save-cmd.py
REPLACE_PYTHON+=	cmd/server-cmd.py
REPLACE_PYTHON+=	cmd/split-cmd.py
REPLACE_PYTHON+=	cmd/tag-cmd.py
REPLACE_PYTHON+=	cmd/tick-cmd.py
REPLACE_PYTHON+=	cmd/version-cmd.py
REPLACE_PYTHON+=	cmd/web-cmd.py
REPLACE_PYTHON+=	cmd/xstat-cmd.py
REPLACE_PYTHON+=	main.py
REPLACE_PYTHON+=	wvtest.py

REPLACE_PYTHON+=	t/cleanup-mounts-under
REPLACE_PYTHON+=	t/hardlink-sets
REPLACE_PYTHON+=	t/id-other-than
REPLACE_PYTHON+=	t/mksock
REPLACE_PYTHON+=	t/ns-timestamp-resolutions
REPLACE_PYTHON+=	t/root-status
REPLACE_PYTHON+=	t/test-ls.sh
REPLACE_PYTHON+=	t/unknown-owner
@


1.25
log
@Remove python33: adapt all packages that refer to it.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.24 2016/07/09 06:38:58 wiz Exp $
d3 1
a3 2
DISTNAME=	bup-0.27
PKGREVISION=	2
d5 9
a13 3
MASTER_SITES=	# https://github.com/bup/bup/releases/
# doc: switch to "man" branch before downloading
DISTFILES=	${DISTNAME}${EXTRACT_SUFX} ${DISTNAME:S/bup/bup-man/}.zip
d15 1
a15 1
MAINTAINER=	pkgsrc-users@@NetBSD.org
d37 3
a84 8
SUBST_CLASSES+=		python-c
SUBST_SED.python-c+=	-e 's,python -c,${PYTHONBIN} -c,'
SUBST_STAGE.python-c=	pre-configure
SUBST_FILES.python-c+=	t/lib.sh
SUBST_FILES.python-c+=	t/test-ls.sh
SUBST_FILES.python-c+=	t/test-meta.sh
SUBST_MESSAGE.python-c=	Fixing python executable in tests.

d101 2
@


1.24
log
@Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.23 2016/03/09 23:53:17 wiz Exp $
d20 1
a20 1
PYTHON_VERSIONS_INCOMPATIBLE=	33 34 35 # py-fuse-bindings
@


1.23
log
@Drop maintainership.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.22 2015/12/05 21:25:58 adam Exp $
d4 1
a4 1
PKGREVISION=	1
@


1.22
log
@Extend PYTHON_VERSIONS_INCOMPATIBLE to 35
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.21 2015/06/12 10:51:11 wiz Exp $
d10 1
a10 1
MAINTAINER=	wiz@@NetBSD.org
@


1.21
log
@Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.20 2015/04/27 09:17:17 wiz Exp $
d20 1
a20 1
PYTHON_VERSIONS_INCOMPATIBLE=	33 34 # py-fuse-bindings
@


1.20
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
@d1 1
a1 1
# $NetBSD: Makefile,v 1.19 2014/09/06 21:29:45 wiz Exp $
d4 1
@


1.19
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
# $NetBSD: Makefile,v 1.18 2014/05/29 23:37:27 wiz Exp $
d3 1
a3 1
DISTNAME=	bup-0.26
d6 2
a7 2
# doc tarball: switch to "man" branch before downloading
DISTFILES=	${DISTNAME}${EXTRACT_SUFX} ${DISTNAME:S/bup/bup-man/}${EXTRACT_SUFX}
d21 1
a21 1
DOCDIR=		${WRKDIR}/bup-0.26
d40 1
@


1.18
log
@Bump for perl-5.20.0.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.17 2014/05/09 07:37:18 wiz Exp $
d3 1
a3 2
DISTNAME=	bup-0.25
PKGREVISION=	4
d5 1
a5 3
MASTER_SITES=	# manually packaged since master site is git repository
# and only available via https
# https://github.com/bup/bup/releases/
d7 1
a7 1
DISTFILES=	${DISTNAME}${EXTRACT_SUFX} ${DISTNAME:S/bup/bup-man/}.zip
d16 1
d21 1
a21 1
DOCDIR=		${WRKDIR}/bup-man
a62 18
REPLACE_PYTHON+=	lib/tornado/__init__.py
REPLACE_PYTHON+=	lib/tornado/auth.py
REPLACE_PYTHON+=	lib/tornado/autoreload.py
REPLACE_PYTHON+=	lib/tornado/database.py
REPLACE_PYTHON+=	lib/tornado/escape.py
REPLACE_PYTHON+=	lib/tornado/httpclient.py
REPLACE_PYTHON+=	lib/tornado/httpserver.py
REPLACE_PYTHON+=	lib/tornado/httputil.py
REPLACE_PYTHON+=	lib/tornado/ioloop.py
REPLACE_PYTHON+=	lib/tornado/iostream.py
REPLACE_PYTHON+=	lib/tornado/locale.py
REPLACE_PYTHON+=	lib/tornado/options.py
REPLACE_PYTHON+=	lib/tornado/s3server.py
REPLACE_PYTHON+=	lib/tornado/template.py
REPLACE_PYTHON+=	lib/tornado/test/test_ioloop.py
REPLACE_PYTHON+=	lib/tornado/web.py
REPLACE_PYTHON+=	lib/tornado/websocket.py
REPLACE_PYTHON+=	lib/tornado/wsgi.py
d66 1
d70 1
d72 1
d79 1
@


1.17
log
@Mark packages that are not ready for python-3.3 also not ready for 3.4,
until proven otherwise.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.16 2014/03/19 17:50:00 gdt Exp $
d4 1
a4 1
PKGREVISION=	3
@


1.16
log
@Add patch to avoid buggy utimensat on NetBSD 6.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.15 2014/03/19 13:15:13 gdt Exp $
d21 1
a21 1
PYTHON_VERSIONS_INCOMPATIBLE=	33 # py-fuse-bindings
@


1.15
log
@Add patch from upstream to avoid failures due to clang warnings.

Resolves failure to build on OS X 10.9.

ok wiz@@ (as MAINTAINER).
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.14 2014/03/19 12:54:02 gdt Exp $
d4 1
a4 1
PKGREVISION=	2
@


1.14
log
@Move fuse support into a default-off option.

Fuse support being on breaks the build on mac, where our wrappers for
OSXFUSE seem not quite right, and fuse support doesn't work on NetBSD.
ok wiz@@ (as MAINTAINER).
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.13 2014/01/25 10:30:21 wiz Exp $
d4 1
a4 1
PKGREVISION=	1
@


1.13
log
@Mark packages as not ready for python-3.x where applicable;
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE=  33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE=  33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.

Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.

Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.

Whitespace cleanups and other nits corrected, where necessary.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.12 2013/12/31 11:03:12 wiz Exp $
d4 1
d120 2
a121 1
.include "../../filesystems/py-fuse-bindings/buildlink3.mk"
@


1.12
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: Makefile,v 1.11 2013/12/18 23:48:22 wiz Exp $
d20 2
@


1.11
log
@Pick up maintainership.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.10 2013/09/09 14:07:59 wiz Exp $
d3 1
a3 2
DISTNAME=	bup-0.25rc1
PKGREVISION=	3
d7 1
a7 1
# https://github.com/apenwarr/bup/tarball/
d9 1
a9 5
# latest apenwarr doc tarball is for 0.24b
# bup-man-0.24b.tar.gz
# use lelutin one instead
DISTFILES=	${DISTNAME}${EXTRACT_SUFX} lelutin-bup-7e0bc2e.zip
# ${DISTNAME:S/bup/bup-man/}${EXTRACT_SUFX}
d12 1
a12 1
HOMEPAGE=	http://github.com/apenwarr/bup
d20 1
a20 3
# needs changing on each update
DOCDIR=		${WRKDIR}/lelutin-bup-7e0bc2e
WRKSRC=		${WRKDIR}/apenwarr-bup-4525252
d28 1
a28 1
USE_TOOLS+=		gmake perl
d31 1
d83 29
@


1.10
log
@Finish git rename from scmgit to git.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.9 2013/05/31 12:41:59 wiz Exp $
d16 1
a16 1
MAINTAINER=	pkgsrc-users@@NetBSD.org
@


1.9
log
@Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package

Like last time, where this caused no complaints.
@
text
@d1 1
a1 2
# $NetBSD: Makefile,v 1.8 2012/10/23 19:50:54 asau Exp $
#
d4 1
a4 1
PKGREVISION=	2
d23 1
a23 1
DEPENDS+=	scmgit-base-[0-9]*:../../devel/scmgit-base
@


1.8
log
@Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.7 2012/10/03 21:57:36 wiz Exp $
d5 1
a5 1
PKGREVISION=	1
@


1.7
log
@Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.6 2012/09/04 13:43:14 wiz Exp $
a25 2
PKG_DESTDIR_SUPPORT=	user-destdir

@


1.6
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
@d1 1
a1 1
# $NetBSD: Makefile,v 1.5 2012/03/15 11:53:38 obache Exp $
d5 1
@


1.5
log
@Bump PKGREVISION from default python to 2.7.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.4 2011/12/15 00:58:14 gdt Exp $
d4 1
a4 2
DISTNAME=	bup-0.24b
PKGREVISION=	3
d10 5
a14 1
DISTFILES=	${DISTNAME}${EXTRACT_SUFX} ${DISTNAME:S/bup/bup-man/}${EXTRACT_SUFX}
d22 1
d28 2
a29 2
DOCDIR=		${WRKDIR}/apenwarr-bup-1783a57
WRKSRC=		${WRKDIR}/apenwarr-bup-d8d6406
d31 1
a31 1
INSTALLATION_DIRS=	${PKGMANDIR}/man1 share/doc/bup
d33 3
a35 1
TEST_TARGET=	test
d54 1
d69 1
@


1.4
log
@Depend on fuse bindings.

Now, "bup fuse dir", assuming ~/.bup is one's bup repository, will
create a fuse mount on dir, in which one can see the backups (with
lots of rought edges).
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.3 2011/09/08 21:57:55 wiz Exp $
d5 1
a5 1
PKGREVISION=	2
@


1.3
log
@Reset maintainer.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.2 2011/05/31 12:01:18 wiz Exp $
d5 1
a5 1
PKGREVISION=	1
d88 1
@


1.2
log
@Install README and design document. Bump PKGREVISION.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.1.1.1 2011/05/16 13:52:56 wiz Exp $
d13 1
a13 1
MAINTAINER=	wiz@@NetBSD.org
@


1.1
log
@Initial revision
@
text
@d1 1
a1 1
# $NetBSD$
d5 1
d27 1
a27 1
INSTALLATION_DIRS=	${PKGMANDIR}/man1
d85 2
@


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
@@