File tarsnap.changes of Package tarsnap

-------------------------------------------------------------------
Sun Aug  1 20:25:39 UTC 2021 - Sebastian Wagner <sebix+novell.com@sebix.at>

- more precise description
- install bash-completion to /usr/, not /etc/
- spec-cleaner run

-------------------------------------------------------------------
Sat Nov 11 23:49:19 UTC 2017 - dmacvicar@suse.de

- Update to version 1.0.39
- Changes since 1.0.38
  * Fix a division-by-zero crash when reading corrupt password-encrypted tarsnap
    key files.
  * Fix a crash in reading corrupt "cpio newc" format archives included via the
    tarsnap @archive directive, on 32-bit systems.
  * Fix a bug in the handling of corrupt "ar" format archives included via the
    tarsnap @archive directive.
  * Fix an abort trap which complained about files with a negative modification
    time.  (This assertion occured after the archive is stored, so no user data
    was at risk.)
- Changes since 1.0.37
  * tarsnap now accepts an --initialize-cachedir command, which is intended for
    the GUI and is not needed for command-line usage.
  * tarsnap now applies --humanize-numbers to the SIGINFO "progress" output.
  * tarsnap now gives a warning for --configfile /nosuchfile.
  * tarsnap now accepts --iso-dates, which prints file and directory dates as
    yyyy-mm-dd hh:mm:ss in "list archive" mode.  This can be cancelled with
    --no-iso-dates.
  * the ./configure --with-conf-no-sample flag causes in the sample config file
    to be installed as tarsnap.conf instead of tarsnap.conf.sample.  This may
    result in overwriting an existing tarsnap.conf file.
  * tarsnap now accepts --force-resources to force the decryption of a
    passphrase-encrypted key file to proceed even if it is anticipated to require
    an excessive amount of memory or CPU time.  This can be cancelled with
    --no-force-resources.
  * tarsnap now supports OpenSSL 1.1.
  * tarsnap now displays 'Deleting archive "foo"' when deleting a single archive
    in verbose mode.  (The former behaviour was to print that message only when
    multiple archives were being deleted by a single tarsnap command.)
  * tarsnap now accepts --archive-names filename, which reads a list of
    archive names from a file in addition to any -f options.

-------------------------------------------------------------------
Sun Jul 31 09:26:12 UTC 2016 - dmacvicar@suse.de

- Update to version 1.0.37
- Changes since 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.
- Changes since 1.0.35
  * A theoretically exploitable one-byte buffer overflow when
    archiving objects with long path names is fixed.
  * A vulnerability which allowed a corrupt archive to cause
    tarsnap to allocate a large amount of memory upon listing
    archives or reading the corrupt archive is fixed.
  * Tarsnap no longer crashes if its first DNS lookup fails.
  * Tarsnap no longer exits with "Callbacks uninitialized" when
    running on a dual-stack network if the first IP stack it
    attempts fails to connect.
  * tarsnap -c --dry-run can now run without a keyfile,
    allowing users to predict how much Tarsnap will cost before
    signing up.
  * Tarsnap now includes bash completion scripts.
  * Tarsnap now automatically detects and uses AESNI and SSE2
    cpu features.
- clean spec file

-------------------------------------------------------------------
Mon Oct 21 16:23:05 UTC 2013 - crrodriguez@opensuse.org

- Tarsnap 1.0.35 
* 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.
* deal with pseudofilesystems such as proc more gracefully.
* support IPV6
* other bugfixes

-------------------------------------------------------------------
Mon Aug 13 23:03:24 UTC 2012 - gregkh@opensuse.org

- update to version 1.0.33, many bugfixes

-------------------------------------------------------------------
Sun Oct  2 20:00:09 UTC 2011 - crrodriguez@opensuse.org

- Explicit BuildRequires on libbz2-devel 

-------------------------------------------------------------------
Mon Sep  5 19:21:08 UTC 2011 - crrodriguez@opensuse.org

- Update to version 1.0.30, many bugfixes

-------------------------------------------------------------------
Wed Mar 30 16:12:44 UTC 2011 - crrodriguez@opensuse.org

- make it a i686 package right away 

-------------------------------------------------------------------
Fri Mar 18 20:14:43 UTC 2011 - crrodriguez@opensuse.org

- remove SSE2 hackish spec file detection, just tell the
  compiler to enable it. 

-------------------------------------------------------------------
Thu Mar  3 02:43:14 UTC 2011 - crrodriguez@opensuse.org

- enable sse2 code 

-------------------------------------------------------------------
Sat Feb 12 20:23:07 UTC 2011 - cristian.rodriguez@opensuse.org

- Version 1.0.29 

-------------------------------------------------------------------
Sat Jan 22 19:15:59 UTC 2011 - gregkh@suse.de

- 1.0.28 release

openSUSE Build Service is sponsored by