Bug 280987
| Summary: | Update sysutils/zfs-replicate port to version 1.0 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Victor <tschetter.victor> | ||||
| Component: | Individual Port(s) | Assignee: | Larry Rosenman <ler> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Many People | CC: | ler, vvd | ||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
take Committed, thanks! A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=b3cf46924d9855b5275b1d3275c1947b6756f124 commit b3cf46924d9855b5275b1d3275c1947b6756f124 Author: Larry Rosenman <ler@FreeBSD.org> AuthorDate: 2024-08-22 00:56:55 +0000 Commit: Larry Rosenman <ler@FreeBSD.org> CommitDate: 2024-08-22 00:58:36 +0000 sysutils/zfs-replicate: update to 1.0 This version includes enhancements and features such as - supports PUSH or PULL replication - supports LOCAL or REMOTE replication - supports multiple pool/dataset pairs to replicate - everything is logged to `${SCRIPTPATH}/logs` by default (can be set to custom location using $LOGBASE variable) but its better to keep it together with the scripts - runs off a well documented `config.sh` file (see below) - can be run on any schedule using cron with `bash zfs-replicate.sh -config.sh` - (for XigmaNAS) includes a `status-report.sh` that can be used to email latest replication status, which will email the latest replication status at your preferred schedule. Simply add it as a custom script in the email settings under "System > Advanced > Email Reports" - includes ALLOW_REPLICATE_FROM_SCRATCH option (see below, or `config.sh` file for details) PR: 280987 Reported by: Victor <tschetter.victor@gmail.com> (Maintainer) sysutils/zfs-replicate/Makefile | 9 ++++----- sysutils/zfs-replicate/distinfo | 6 +++--- sysutils/zfs-replicate/pkg-descr | 2 +- 3 files changed, 8 insertions(+), 9 deletions(-) Is this the preferred way to maintain this port? Or should I push the changes myself. Also, will this now work with pkg install zfs-replicate? Unless you get a commit bit, this is the preferred way. When the package builders build this package, a pkg install zfs-replicate will work. It's NOT instant. Better remove GH_TAGNAME and add DISTVERSIONPREFIX=v. Then make makesum. Done - thanks! Do I need to do anything for the package to be built besides wait? Nope. It'll get built eventually... |
Created attachment 252997 [details] diff file for requested changes Update sysutils/zfs-replicate to version 1.0 This version includes enhancements and features such as - supports PUSH or PULL replication - supports LOCAL or REMOTE replication - supports multiple pool/dataset pairs to replicate - everything is logged to `${SCRIPTPATH}/logs` by default (can be set to custom location using $LOGBASE variable) but its better to keep it together with the scripts - runs off a well documented `config.sh` file (see below) - can be run on any schedule using cron with `bash zfs-replicate.sh -config.sh` - (for XigmaNAS) includes a `status-report.sh` that can be used to email latest replication status, which will email the latest replication status at your preferred schedule. Simply add it as a custom script in the email settings under "System > Advanced > Email Reports" - includes ALLOW_REPLICATE_FROM_SCRATCH option (see below, or `config.sh` file for details)