Bug 240239
| Summary: | sysutils/py-pyznap: Update to 1.4.2 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Dries Michiels <driesm> | ||||
| Component: | Individual Port(s) | Assignee: | Steve Wills <swills> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
A commit references this bug: Author: swills Date: Mon Sep 2 13:42:46 UTC 2019 New revision: 510787 URL: https://svnweb.freebsd.org/changeset/ports/510787 Log: sysutils/py-pyznap: Update to 1.4.2 PR: 240239 Submitted by: Dries Michiels <driesm.michiels@gmail.com> (maintainer) Changes: head/sysutils/py-pyznap/Makefile head/sysutils/py-pyznap/distinfo Committed, thanks! |
Created attachment 207051 [details] svn diff to update Changelog from previous version: [1.4.2] - 2019-08-30 Fixed Catch DatasetNotFoundError if dataset was destroyed after starting pyznap. [1.4.1] - 2019-08-27 Fixed Close stderr to detect broken pipe. Raise CalledProcessError if there is any error during zfs receive. [1.4.0] - 2019-08-27 Added You can now exclude datasets when sending using Unix shell-type wildcards. Use the exclude keyword in the config or the -e flag for pyznap send. [1.3.0] - 2019-08-22 Added pyznap can now pull data over ssh, i.e. you can now send form local to local, local to remote, remote to local and remote to remote. Note that remote to remote is not direct, but via the local machine. pv now outputs status once per minute when stdout is redirected (e.g. to a file). Changed Rewrote local/remote 'zfs send' commands in a more uniform manner. Fixed Enforce python>=3.5 in setup.py.