simple wrapper around bup index and save designed to be ran in cron jobs, with support for filesystem snapshots, logging and configuration files.
options can also be specified, without –, in %s. an arbitrary configuration file may also be supplied on the commandline with a @ prefix (e.g. @foo.conf).
at least path and repo need to be specified.
1 maintainer
Metadata
1 maintainer
Release files for bup_cron 1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| bup_cron-1.3.tar.gz | 16.7 kB | Without provenance | Details |
Release files / bup_cron-1.3.tar.gz
| Download URL | bup_cron-1.3.tar.gz |
|---|---|
| Size | 16.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
211d103b654d8f6a139da1910176d93241af5a1d4d4a60f10a172191870a572b
|
|
BLAKE2b-256 checksum How to use checksums |
d7ecd390289f75801c4981fff392a6b5e2cc9ae3c917e79996abf2285568d170
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bup_cron 1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
