8000 Tags · simonsan/tarsnap · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Tags: simonsan/tarsnap

Tags

1.0.40

Toggle 1.0.40's commit message 
Update packaging metadata for 1.0.40 release

1.0.39.99

Toggle 1.0.39.99's commit message 
pkg/archlinux: remove

This was first added in
    2009-02-03 Tarsnap 1.0.20
    5dcba89

The current Arch maintainer has said that
    In my opinion it can be dropped, we don't use that PKGBUILD for
    building the tarsnap package.
    https://twitter.com/jvdwaa/status/1489281677570580487

Indeed, the "community" package for Tarsnap on Arch Linux is much more
recent (1.0.39-3) than that file (1.0.29-1).
https://archlinux.org/packages/community/x86_64/tarsnap/

1.0.39-deb-2

Toggle 1.0.39-deb-2's commit message 
pkg/deb: use default libssl-dev

- 2016-12-30: we disallowed libssl 1.1.x because the client couldn't
  handle it.
- 2017-06-06: we released tarsnap 1.0.38 (which supported libssl 1.1.x),
  but I forgot to stop the package from disallowing libssl 1.1.x.  Most
  Linux distributions provided a libssl 1.0.2 for compatibility reasons,
  so this flaw went undetected until now.

1.0.39

Toggle 1.0.39's commit message 
pkg: deb: update changelog for 1.0.39

1.0.38

Toggle 1.0.38's commit message 
Merge pull request Tarsnap#276 from Tarsnap/debian1038

Version 1.0.38.

1.0.37-deb-4

Toggle 1.0.37-deb-4's commit message 
pkg: deb: version 1.0.37-4

1.0.37

Toggle 1.0.37's commit message 
Update debian changelog for 1.0.37

This really is 1.0.37, not just an alphatest version.

1.0.36.1

Toggle 1.0.36.1's commit message 
Fix build on OS X

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.

1.0.36

Toggle 1.0.36's commit message 
Update debian pkg changelog for 1.0.36

1.0.35

Toggle 1.0.35's commit message 
Tarsnap 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.
0