Standalone package (tarball?) #514
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#514
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
Install the same (or very close) version of borgmatic on Debian 10 and 11, when pip3 is not an option to use for installation.
Steps to reproduce (if a bug)
Include (sanitized) borgmatic configuration files if applicable.
Actual behavior (if a bug)
Debian 10 contain borgmatic 1.2.11
Debian 11 contain borgmatic 1.5.12
I want to install 1.5.x (ideally 1.5.20+) on both Debian versions.
We have an installation for borgbackup 1.1.17 on both Debian 10 and 11.
Expected behavior (if a bug)
Not able to use pip3 to install a more recent package.
Other notes / implementation ideas
With apt/deb being to old, pip3 not possible in this case, I'm looking at any offline installation option available. Tarball?
Is PyInstaller an option?
Our solution was to use pyinstaller and build specific packages for each os and version.