Offer distro packages #302
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Is it possible to offer distro packages, for example for Debian? To do this efficiently, you could use SUSE's OBS at https://build.opensuse.org.
That would be a great win because the current support version of borgmatic is 1.2.x and is very old...
The same applies for the
borgbackup
package on Debian. Even Buster is on 1.1.9, which is more than a year old.The situation was similar on CentOS 7 and that's why I moved to the pip packages in a virtualenv.
Thanks for filing this!
If someone contributes Debian packaging, I'd be happy to kick it off as part of the existing build process. Although the current build is on Alpine, so there may have to be some tweaks there..
It's worth asking though: I assume you've considered using one of the existing borgmatic installation methods like pip install? Is it just that a native Debian package would be easier to apt upgrade as part of the rest of your system? Or is there another reason I'm not considering for a Debian package?
Tbh, I wasn't aware of pip being a possibility. I also don't know if pip handles dependencies properly like the distro package management does. I'll check it out though
Pip does indeed handle installing Python dependencies as well. The one thing borgmatic doesn't declare a direct dependency on however is Borg, which you'll also need to install (whether via pip or apt).
Current packages for borgmatic for Fedora and RHEL/CentOS can be found at https://copr.fedorainfracloud.org/coprs/heffer/borgmatic/
If you prefer the most recent version this would be the place to go. The versions there are exactly the same that go into the official repositories with the only difference being that they are available immediately instead of after 7 days of ripening in updates-testing.
borgmatic sometimes sees releases in such quick succession that due to the way Fedora deals with new updates obsoleting pending updates in Bodhi there may be weeks between seeing a new release in the official repos, hence the COPR for people that like to stay current with the upstream versions.
I am also the maintainer of borgmatic in Fedora. I do have an EPEL7 and EPEL8 branch set up for borgmatic but I cannot currently build it for EL7 because the maintainer of pykwalify is not responding on this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1763554
For EL8 I'll have to look but I recall colorama being too old in EL8.
The most recent release notwithstanding, I've been trying to slow releases down a bit.. especially after feedback from packagers! So they hopefully won't be quite as a rapid-fire. (Side note: I've been spoiled by working on SaaS software, where releases can happen as frequently as you can push code and run tests.)
Is there any status update on the possibility of a repository?
I've run in to the same issue with a Raspberry Pi on RPi OS Buster. Borgmatic (and Borg) are basically so old, none of my normal provisioning works and I'd have to do it all by hand (which is a pain, because I will forget about it, and end up with even more trouble when trying to restore, etc.)
The current status is pretty much unchanged.. I'd be happy to look at a pull request for this feature, but thus far I don't believe anyone has worked on the packaging or the build/hosting changes to support Debian packages for borgmatic.
In terms of your immediate issue, a few options:
pip
to install a recent version of borgmatic and then subscribe to the releases page, so you're notified of new releases.That's what I ended up doing. It's a bit a PITA, but the problem is on Debian, I guess.
Yeah, it's a thorny issue. This is a gap that some rolling release distros like Arch or Manjaro try to solve, perhaps at the cost of some stability. borgmatic is pretty up-to-date there.
Given that a solution for this hasn't materialized in the past few years (e.g. via a PR), I'm closing this for now. However I'd be happy to revisit and reopen if someone wants to work on this.