The NetBSD Project

CVS log for pkgsrc/sysutils/tarsnap/Makefile

[BACK] Up to [cvs.NetBSD.org] / pkgsrc / sysutils / tarsnap

Request diff between arbitrary revisions


Keyword substitution: kv
Default branch: MAIN


Revision 1.21: download - view: text, markup, annotated - select for diffs
Sat Mar 22 12:24:06 2025 UTC (19 months, 3 weeks ago) by nia
Branches: MAIN
CVS tags: pkgsrc-2026Q3-base, pkgsrc-2026Q3, pkgsrc-2026Q2-base, pkgsrc-2026Q2, pkgsrc-2026Q1-base, pkgsrc-2026Q1, pkgsrc-2025Q4-base, pkgsrc-2025Q4, pkgsrc-2025Q3-base, pkgsrc-2025Q3, pkgsrc-2025Q2-base, pkgsrc-2025Q2, pkgsrc-2025Q1-base, pkgsrc-2025Q1, HEAD
Diff to: previous 1.20: preferred, colored
Changes since revision 1.20: +5 -1 lines
tarsnap: Requires e2fsprogs on Linux.

Identified by drecklypkg ci on CentOS 7 and recent Ubuntu.

Revision 1.20: download - view: text, markup, annotated - select for diffs
Fri Mar 21 17:11:46 2025 UTC (19 months, 3 weeks ago) by wiz
Branches: MAIN
Diff to: previous 1.19: preferred, colored
Changes since revision 1.19: +2 -3 lines
tarsnap: update to 1.0.41.

### Tarsnap 1.0.41 (March 21, 2025)

- tarsnap now has mitigations to defend against information leakage via
  chunking: Chunks are padded using the PADME scheme, and small-alphabet
  cycles are prohibited in chunking to block a chosen-plaintext attack.
- tarsnap -c now accepts --dry-run-metadata, which simulates creating an
  archive without reading any file data.  This is significantly faster than a
  regular --dry-run, and is suitable for checking which filesystem entries
  will be archived (with -v) or checking the total archive size (with --totals
  or --progress-bytes).
- tarsnap now accepts --noatime with -c mode, which requests that the
  operating system does not update atime when reading files or directories.
  Not supported by all operating systems or filesystems.
- If the server-side state was modified and tarsnap exits with an error, it
  will now have an exit code of 2.
- tarsnap will read a config file in $XDG_CONFIG_HOME/tarsnap/tarsnap.conf;
  or ~/.config/tarsnap/tarsnap.conf if $XDG_CONFIG_HOME is not set.  The
  previous config file ~/.tarsnaprc is still supported, and will not be
  deprecated.
- tarsnap now accepts --null-input as a synonym for --null.  For compatibility
  reasons, --null is still supported, and will not be deprecated.
- tarsnap now accepts --null-output, which causes --list-archives to separate
  each archive name with a null character (like `find -print0`).  If one or
  more -v arguments are specified, multiple null characters are used to
  separate fields; see the man page for details.
- tarsnap now accepts --null-output with -x and -t, which causes them to
  separate each filename with a null character.  If there are multiple fields
  on a line, null characters are used instead of spaces; see the man page for
  details.
- tarsnap now accepts --null-output with --print-stats, which causes it to
  separate fields and lines with null character(s); see the man page for
  details.
- tarsnap now accepts --hashes, which causes --list-archives to print hashes
  of archive names.  If one or more -v arguments are specified, it will print
  other metadata (as per --list-archives).  This option is intended for the
  GUI and is not needed for command-line usage.
- tarsnap now accepts -f TAPEHASH with --list-archives --hashes, which prints
  metadata about the specified archive(s).  Multiple -f options may be
  specified.  This option is intended for the GUI and is not needed for
  command-line usage.
- Fixed a problem with strict aliasing if somebody compiled with gcc11 or
  higher using -O3, does not have SSE2, and is using a passphrase-protected
  keyfile.

Revision 1.19: download - view: text, markup, annotated - select for diffs
Tue Oct 24 22:11:15 2023 UTC (3 years ago) by wiz
Branches: MAIN
CVS tags: pkgsrc-2024Q4-base, pkgsrc-2024Q4, pkgsrc-2024Q3-base, pkgsrc-2024Q3, pkgsrc-2024Q2-base, pkgsrc-2024Q2, pkgsrc-2024Q1-base, pkgsrc-2024Q1, pkgsrc-2023Q4-base, pkgsrc-2023Q4
Diff to: previous 1.18: preferred, colored
Changes since revision 1.18: +2 -1 lines
*: bump for openssl 3

Revision 1.18: download - view: text, markup, annotated - select for diffs
Sat Feb 12 22:58:08 2022 UTC (4 years, 9 months ago) by wiz
Branches: MAIN
CVS tags: pkgsrc-2023Q3-base, pkgsrc-2023Q3, pkgsrc-2023Q2-base, pkgsrc-2023Q2, pkgsrc-2023Q1-base, pkgsrc-2023Q1, pkgsrc-2022Q4-base, pkgsrc-2022Q4, pkgsrc-2022Q3-base, pkgsrc-2022Q3, pkgsrc-2022Q2-base, pkgsrc-2022Q2, pkgsrc-2022Q1-base, pkgsrc-2022Q1
Diff to: previous 1.17: preferred, colored
Changes since revision 1.17: +3 -3 lines
tarsnap: update to 1.0.40.

Tarsnap 1.0.40 is now available.  This version brings several improvements
compared to tarsnap 1.0.39:

* tarsnap now accepts a --resume-extract option to skip extracting files whose
  filesize and mtime match existing files on disk.

* tarsnap now accepts --progress-bytes SIZE, which prints a progress message
  after each SIZE bytes are processed, up to once per file.  This can be
  disabled with --no-progress-bytes.

* tarsnap now accepts a --passphrase method:arg option which accepts:
  * --passphrase dev:tty-stdin
  * --passphrase dev:stdin-once
  * --passphrase dev:tty-once
  * --passphrase env:VARNAME
  * --passphrase file:FILENAME

* tarsnap now accepts a --dump-config option to print the command-line and all
    non-blank lines read from config files.

* tarsnap now exits with an error if there are unused command-line arguments.
  (i.e. "tarsnap -d -f a1 a2", where "a2" is unused.)

* Improved performance on some x86, amd64, and arm64 systems by using
  cryptographic instruction set extensions.

* When sent SIGINFO or SIGUSR1, tarsnap now prints the number of files and the
  number of uncompressed bytes processed, in addition to the previous output.

* A zsh completion file can be installed with
  configure --with-zsh-completion=DIR.

As usual, there are also lots of minor build fixes, harmless bug fixes, and
code cleanups.

Revision 1.17: download - view: text, markup, annotated - select for diffs
Mon Apr 6 20:40:28 2020 UTC (6 years, 7 months ago) by schmonz
Branches: MAIN
CVS tags: pkgsrc-2021Q4-base, pkgsrc-2021Q4, pkgsrc-2021Q3-base, pkgsrc-2021Q3, pkgsrc-2021Q2-base, pkgsrc-2021Q2, pkgsrc-2021Q1-base, pkgsrc-2021Q1, pkgsrc-2020Q4-base, pkgsrc-2020Q4, pkgsrc-2020Q3-base, pkgsrc-2020Q3, pkgsrc-2020Q2-base, pkgsrc-2020Q2
Diff to: previous 1.16: preferred, colored
Changes since revision 1.16: +3 -2 lines
Support PKG_SYSCONFDIR. Bump PKGREVISION.

Revision 1.16: download - view: text, markup, annotated - select for diffs
Sat Jan 18 21:50:59 2020 UTC (6 years, 9 months ago) by jperkin
Branches: MAIN
CVS tags: pkgsrc-2020Q1-base, pkgsrc-2020Q1
Diff to: previous 1.15: preferred, colored
Changes since revision 1.15: +2 -1 lines
*: Recursive revision bump for openssl 1.1.1.

Revision 1.15: download - view: text, markup, annotated - select for diffs
Sat Jul 29 06:19:28 2017 UTC (9 years, 3 months ago) by wiz
Branches: MAIN
CVS tags: pkgsrc-2019Q4-base, pkgsrc-2019Q4, pkgsrc-2019Q3-base, pkgsrc-2019Q3, pkgsrc-2019Q2-base, pkgsrc-2019Q2, pkgsrc-2019Q1-base, pkgsrc-2019Q1, pkgsrc-2018Q4-base, pkgsrc-2018Q4, pkgsrc-2018Q3-base, pkgsrc-2018Q3, pkgsrc-2018Q2-base, pkgsrc-2018Q2, pkgsrc-2018Q1-base, pkgsrc-2018Q1, pkgsrc-2017Q4-base, pkgsrc-2017Q4, pkgsrc-2017Q3-base, pkgsrc-2017Q3
Diff to: previous 1.14: preferred, colored
Changes since revision 1.14: +2 -2 lines
Updated tarsnap to 1.0.39.

Tarsnap 1.0.39 is now available.  (Yes, just 2 weeks after 1.0.38.)  This
version brings several important bug fixes:

* tarsnap 1.0.38 (but not earlier versions) would exit with an assertion
failure after successfully creating an archive containing a file with a
"last modified" time prior to January 1st, 1970.

* tarsnap 1.0.38 and earlier could crash if instructed to archive the
contents of corrupt cpio or ar archives (via the @archive directive).

* tarsnap 1.0.38 and earlier could crash if passed an invalidly encrypted
key file.

Revision 1.14: download - view: text, markup, annotated - select for diffs
Sat Jul 15 06:11:56 2017 UTC (9 years, 4 months ago) by wiz
Branches: MAIN
Diff to: previous 1.13: preferred, colored
Changes since revision 1.13: +2 -4 lines
Updated tarsnap to 1.0.38.

Tarsnap 1.0.38 is now available.  This version brings several new features
compared to tarsnap 1.0.37:

* Tarsnap now supports OpenSSL 1.1.

* tarsnap accepts an --iso-dates option, which causes times to be printed in
YYYY-MM-DD HH:MM:SS format rather than the traditional unix "ls -l" style.

* tarsnap accepts a --force-resources option to proceed with decryption of a
passphrase-encrypted key file even if it is anticipated to use an excessive
amount of memory or CPU time.  (This may be useful if tarsnap inaccurately
estimates the amount of memory your system has available.)

* tarsnap accepts an --archive-names <file> option, which reads a list of
archive names to operate on when operating in -d and --print-stats modes.
(This should make some scripts simpler; no more need to construct a command
line which has '-f' inserted before each archive name.)

Potentially (but unlikely) breaking changes in this code compared to tarsnap
1.0.37:

* tarsnap now applies the --humanize-numbers option to the "progress" output
printed by SIGINFO / SIGUSR1.  If you have scripts which send signals to
tarsnap and parse its output, they may need to be updated.

* tarsnap -v now prints 'Deleting archive "foo"' even if only one archive is
being deleted.  If you have scripts which parse the output of tarsnap -v,
they may need to be updated.

* tarsnap now prints a warning if you pass '--configfile /nosuchfile'.  If you
have scripts which rely on being able to specify nonexistent configuration
files and not get any warnings from tarsnap, they may need to be updated.
(Also, if you were doing that, I *really* want to know why.)

There are also two changes which most users should not encounter:

* tarsnap now has an --initialize-cachedir mode; this is intended for use by
the GUI.  (The cache directory will be initialized automatically in normal
usage of the tarsnap command-line utility.)

* tarsnap's configure script takes a --with-conf-no-sample option which
results in the sample tarsnap configuration file being installed as
"tarsnap.conf" rather than "tarsnap.conf.sample".  This is intended for use in
some packaging systems which have mechanisms for managing configuration files,
and should probably not be used by hand (since it will overwrite your existing
tarsnap.conf).

Revision 1.13: download - view: text, markup, annotated - select for diffs
Thu Mar 10 22:54:13 2016 UTC (10 years, 8 months ago) by wiz
Branches: MAIN
CVS tags: pkgsrc-2017Q2-base, pkgsrc-2017Q2, pkgsrc-2017Q1-base, pkgsrc-2017Q1, pkgsrc-2016Q4-base, pkgsrc-2016Q4, pkgsrc-2016Q3-base, pkgsrc-2016Q3, pkgsrc-2016Q2-base, pkgsrc-2016Q2, pkgsrc-2016Q1-base, pkgsrc-2016Q1
Diff to: previous 1.12: preferred, colored
Changes since revision 1.12: +2 -3 lines
Update tarsnap to 1.0.37.

First the new release: Tarsnap 1.0.37 is now available.  This version brings
the following substantive changes compared to tarsnap 1.0.36:

 * tarsnap-key(gen|mgmt|regen) now accept a --passphrase-time option,
which specifies the duration to be spent on computing the derived keys
used for encrypting the tarsnap key file.

 * tarsnap now accepts a --keep-going option when deleting or printing
statistics about multiple archives.

 * tarsnap-keymgmt now accepts a --print-key-permissions option for
listing the permissions contained in a key file.

 * tarsnap --print-stats now accepts a --csv-file option for printing
statistics in comma-separated-value format.

 * tarsnap now accepts a --verify-config command which exits silently
after checking the configuration file(s) for syntax errors.

 * tarsnap now looks for a server named "v1-0-0-server.tarsnap.com"
instead of the historic "betatest-server.tarsnap.com" hostname.  This
should have no user-visible effect in most configurations.

 * tarsnap now correctly warns if a sparse extract fails due to hardlinks.

 * tarsnap now prints a warning if creating an empty archive.

As usual, there are also many minor build fixes, harmless bug fixes, and code
refactoring / cleanup changes.  For a full listing of changes, consult the
tarsnap git repository: https://github.com/Tarsnap/tarsnap

Revision 1.12: download - view: text, markup, annotated - select for diffs
Sat Mar 5 11:29:32 2016 UTC (10 years, 8 months ago) by jperkin
Branches: MAIN
Diff to: previous 1.11: preferred, colored
Changes since revision 1.11: +2 -1 lines
Bump PKGREVISION for security/openssl ABI bump.

Revision 1.9.8.1: download - view: text, markup, annotated - select for diffs
Mon Aug 24 19:10:29 2015 UTC (11 years, 2 months ago) by tron
Branches: pkgsrc-2015Q2
Diff to: previous 1.9: preferred, colored; next MAIN 1.10: preferred, colored
Changes since revision 1.9: +2 -2 lines
Pullup ticket #4797 - requested by wiz
sysutils/tarsnap: security update

Revisions pulled up:
- sysutils/tarsnap/Makefile                                     1.10-1.11
- sysutils/tarsnap/distinfo                                     1.6-1.7

---
   Module Name:	pkgsrc
   Committed By:	wiz
   Date:		Fri Aug 21 14:43:17 UTC 2015

   Modified Files:
   	pkgsrc/sysutils/tarsnap: Makefile distinfo

   Log Message:
   Update to 1.0.36:

   1. SECURITY FIX: When constructing paths of objects being archived, a buffer
   could overflow by one byte upon encountering 1024, 2048, 4096, etc. byte
   paths. Theoretically this could be exploited by an unprivileged user whose
   files are being archived; I do not believe it is exploitable in practice,
   but I am offering a $1000 bounty for the first person who can prove me wrong:
   http://www.daemonology.net/blog/2015-08-21-tarsnap-1000-exploit-bounty.html

   2. SECURITY FIX: An attacker with a machine's write keys, or with read keys
   and control of the tarsnap service, could make tarsnap allocate a large
   amount of memory upon listing archives or reading an archive the attacker
   created; on 32-bit machines, tarsnap can be caused to crash under the
   aforementioned conditions.

   3. BUG FIX: Tarsnap no longer crashes if its first DNS lookup fails.

   4. BUG FIX: Tarsnap no longer exits with "Callbacks uninitialized" when
   running on a dual-stack network if the first IP stack it attempts fails to
   connect.

   5. tarsnap now avoids opening devices nodes on linux if it is instructed to
   archive /dev/.  This change may prevent "watchdog"-triggered reboots.

   6. tarsnap -c --dry-run can now run without a keyfile, allowing users to
   predict how much Tarsnap will cost before signing up.

   7. tarsnap now has bash completion scripts.

   8. tarsnap now takes a --retry-forever option.

   9. tarsnap now automatically detects and uses AESNI and SSE2.

   As usual, there are also many minor build fixes, harmless bug fixes, and code
   refactoring / cleanup changes.  For a full listing of changes, consult the
   tarsnap git repository: https://github.com/Tarsnap/tarsnap

---
   Module Name:	pkgsrc
   Committed By:	wiz
   Date:		Fri Aug 21 18:03:22 UTC 2015

   Modified Files:
   	pkgsrc/sysutils/tarsnap: Makefile distinfo

   Log Message:
   Update to 1.0.36.1:
   OS X lacks the POSIX-mandated clock_gettime function, and tarsnap is
   not using libcperciva's "support broken operating systems" compatibility
   mechanism yet.  Add -DPOSIXFAIL_CLOCK_REALTIME to the build.

Revision 1.11: download - view: text, markup, annotated - select for diffs
Fri Aug 21 18:03:22 2015 UTC (11 years, 2 months ago) by wiz
Branches: MAIN
CVS tags: pkgsrc-2015Q4-base, pkgsrc-2015Q4, pkgsrc-2015Q3-base, pkgsrc-2015Q3
Diff to: previous 1.10: preferred, colored
Changes since revision 1.10: +2 -2 lines
Update to 1.0.36.1:
OS X lacks the POSIX-mandated clock_gettime function, and tarsnap is
not using libcperciva's "support broken operating systems" compatibility
mechanism yet.  Add -DPOSIXFAIL_CLOCK_REALTIME to the build.

Revision 1.10: download - view: text, markup, annotated - select for diffs
Fri Aug 21 14:43:17 2015 UTC (11 years, 2 months ago) by wiz
Branches: MAIN
Diff to: previous 1.9: preferred, colored
Changes since revision 1.9: +2 -2 lines
Update to 1.0.36:

1. SECURITY FIX: When constructing paths of objects being archived, a buffer
could overflow by one byte upon encountering 1024, 2048, 4096, etc. byte
paths. Theoretically this could be exploited by an unprivileged user whose
files are being archived; I do not believe it is exploitable in practice,
but I am offering a $1000 bounty for the first person who can prove me wrong:
http://www.daemonology.net/blog/2015-08-21-tarsnap-1000-exploit-bounty.html

2. SECURITY FIX: An attacker with a machine's write keys, or with read keys
and control of the tarsnap service, could make tarsnap allocate a large
amount of memory upon listing archives or reading an archive the attacker
created; on 32-bit machines, tarsnap can be caused to crash under the
aforementioned conditions.

3. BUG FIX: Tarsnap no longer crashes if its first DNS lookup fails.

4. BUG FIX: Tarsnap no longer exits with "Callbacks uninitialized" when
running on a dual-stack network if the first IP stack it attempts fails to
connect.

5. tarsnap now avoids opening devices nodes on linux if it is instructed to
archive /dev/.  This change may prevent "watchdog"-triggered reboots.

6. tarsnap -c --dry-run can now run without a keyfile, allowing users to
predict how much Tarsnap will cost before signing up.

7. tarsnap now has bash completion scripts.

8. tarsnap now takes a --retry-forever option.

9. tarsnap now automatically detects and uses AESNI and SSE2.

As usual, there are also many minor build fixes, harmless bug fixes, and code
refactoring / cleanup changes.  For a full listing of changes, consult the
tarsnap git repository: https://github.com/Tarsnap/tarsnap

Revision 1.9: download - view: text, markup, annotated - select for diffs
Thu Aug 21 16:02:11 2014 UTC (12 years, 2 months ago) by jperkin
Branches: MAIN
CVS tags: pkgsrc-2015Q2-base, pkgsrc-2015Q1-base, pkgsrc-2015Q1, pkgsrc-2014Q4-base, pkgsrc-2014Q4, pkgsrc-2014Q3-base, pkgsrc-2014Q3
Branch point for: pkgsrc-2015Q2
Diff to: previous 1.8: preferred, colored
Changes since revision 1.8: +3 -1 lines
Fix build on SunOS (needs explicit -lnsl).

Revision 1.8: download - view: text, markup, annotated - select for diffs
Wed Apr 2 12:04:50 2014 UTC (12 years, 7 months ago) by wiz
Branches: MAIN
CVS tags: pkgsrc-2014Q2-base, pkgsrc-2014Q2
Diff to: previous 1.7: preferred, colored
Changes since revision 1.7: +2 -3 lines
Update to 1.0.35:

Changes since version 1.0.34:

   A bug in tarsnap 1.0.34 which could cause tarsnap to crash
   (segmentation fault or bus error) when encountering network
   glitches or outages is fixed.

   When tarsnap encounters "insane" filesystems (procfs and other
   similar synthetic filesystems which are not reasonable to
   archive), it now archives the filesystem mount point but by
   default does not recurse into the filesystem. Previous releases
   (since 1.0.26) did not archive the synthetic filesystem mount
   point.

Changes since version 1.0.33:

   Tarsnap now supports both IPv4 and IPv6.

   Tarsnap is now more resilient against short network glitches
   when it first connects to the Tarsnap server.

   Tarsnap now supports platforms with mandatory structure alignment
   (e.g., ARM OABI).

   Tarsnap now restores terminal settings if killed with ^C while
   reading a password or passphrase.

   Multiple minor bug fixes and cleanups.

Revision 1.7: download - view: text, markup, annotated - select for diffs
Wed Feb 26 18:20:29 2014 UTC (12 years, 8 months ago) by wiedi
Branches: MAIN
CVS tags: pkgsrc-2014Q1-base, pkgsrc-2014Q1
Diff to: previous 1.6: preferred, colored
Changes since revision 1.6: +2 -1 lines
Bulk build wants openssl

Revision 1.6: download - view: text, markup, annotated - select for diffs
Sun Feb 16 15:48:03 2014 UTC (12 years, 9 months ago) by wiedi
Branches: MAIN
Diff to: previous 1.5: preferred, colored
Changes since revision 1.5: +2 -1 lines
Needs zlib

Revision 1.5: download - view: text, markup, annotated - select for diffs
Tue Oct 23 19:51:26 2012 UTC (14 years ago) by asau
Branches: MAIN
CVS tags: pkgsrc-2013Q4-base, pkgsrc-2013Q4, pkgsrc-2013Q3-base, pkgsrc-2013Q3, pkgsrc-2013Q2-base, pkgsrc-2013Q2, pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4
Diff to: previous 1.4: preferred, colored
Changes since revision 1.4: +1 -3 lines
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Revision 1.4: download - view: text, markup, annotated - select for diffs
Sat Sep 1 20:40:54 2012 UTC (14 years, 2 months ago) by riz
Branches: MAIN
CVS tags: pkgsrc-2012Q3-base, pkgsrc-2012Q3
Diff to: previous 1.3: preferred, colored
Changes since revision 1.3: +2 -2 lines
Update tarsnap to version 1.0.33.

Changes since version 1.0.32:

	- Tarsnap now caches archive metadata blocks in RAM, typically
	  providing a 5x - 10x speedup and reduction in bandwidth usage
	  in the "fsck" operation and when deleting a large number of
	  archives at once.
	- Tarsnap's internal "chunk" metadata structure is now smaller,
	  providing a ~10% reduction in usage on 32-bit machines and a
	  ~30% reduction in memory usage on 64-bit machines.
	- Tarsnap's --newer* options now correctly descend into old
	  directories in order to look for new files. (But note that
	  tarsnap's snapshotting makes these options unnecessary in
	  most situations.)
	- Multiple minor bug fixes and cleanups.

Changes since version 1.0.31:

	- A bug affecting the handling of the --nodump option on Linux
	  (and in most cases rendering it inoperative) is fixed.
	- A workaround has been added for a compiler bug in OS X 10.7 (Lion).
	- The NetBSD "kernfs" and "ptyfs" filesystems are now excluded
	  from archival by default.

Revision 1.3: download - view: text, markup, annotated - select for diffs
Sat Dec 3 07:09:31 2011 UTC (14 years, 11 months ago) by riz
Branches: MAIN
CVS tags: pkgsrc-2012Q2-base, pkgsrc-2012Q2, pkgsrc-2012Q1-base, pkgsrc-2012Q1, pkgsrc-2011Q4-base, pkgsrc-2011Q4
Diff to: previous 1.2: preferred, colored
Changes since revision 1.2: +2 -2 lines
Update tarsnap to version 1.0.31.

Changes since version 1.0.30:

	- A race condition in key generation has been fixed which could
	  allow a newly-generated key file to be read by another local
	  user if the key file is being generated in a world-readable
	  directory and the user running tarsnap-keygen has a umask other
	  than 0066.
	- A bug in key generation has been fixed which could allow a
	  newly-generated key file to be read by another local user
	  if they key file is being generated in a world-writable
	  directory (e.g., /tmp).
	- Tarsnap now supports Minix.
	- Tarsnap now ignores blank lines in key files; line-buffers
	  its output (which makes tarsnap --list-archives | foo more
	  responsive); and prints a progress indicator during tarsnap --fsck.
	- Multiple minor bug fixes.

Revision 1.2: download - view: text, markup, annotated - select for diffs
Thu Aug 25 15:24:14 2011 UTC (15 years, 2 months ago) by wiz
Branches: MAIN
CVS tags: pkgsrc-2011Q3-base, pkgsrc-2011Q3
Diff to: previous 1.1: preferred, colored
Changes since revision 1.1: +3 -3 lines
Update to 1.0.30. Drop maintainership since I never actually used it...

Changes since version 1.0.29:

    A bug fix in the handling of readdir errors; in earlier versions,
    it was theoretically possible for a failing hard drive or other
    errors in reading directories to result in files being silently
    omitted from an archive.

    Several bug fixes relating to the handling of @archive directives
    with mtree files.

    A bug fix to prevent cache directory corruption resulting in
    tarsnap failing if it was interrupted at exactly the right
    (wrong) moment in its operation.

    A bug fix to correctly handle ~ in tarsnap -s path substitutions.

    Many more minor bug fixes.

Revision 1.1.1.1 (vendor branch): download - view: text, markup, annotated - select for diffs
Sun May 15 11:16:14 2011 UTC (15 years, 6 months ago) by wiz
Branches: TNF
CVS tags: pkgsrc-2011Q2-base, pkgsrc-2011Q2, pkgsrc-20110515
Diff to: previous 1.1: preferred, colored
Changes since revision 1.1: +0 -0 lines
Follow Greg's advice and reimport in a better place, i.e. move
tarsnap from security to sysutils.

Revision 1.1: download - view: text, markup, annotated - select for diffs
Sun May 15 11:16:14 2011 UTC (15 years, 6 months ago) by wiz
Branches: MAIN
Initial revision

Diff request

This form allows you to request diffs between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.

Log view options

CVSweb <webmaster@jp.NetBSD.org>