borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
15
57
Fork 40
Code Issues 53 Pull Requests 1 Actions Packages Releases 121 Activity

Offer distro packages #302

New Issue
Closed
opened 2020-04-28 09:23:13 +00:00 by aardbol · 11 comments
aardbol commented 2020-04-28 09:23:13 +00:00
Copy Link

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...

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...
sdellenb commented 2020-04-28 12:07:55 +00:00
Copy Link

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.

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.
witten commented 2020-04-28 16:04:30 +00:00
Owner
Copy Link

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?

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?
aardbol commented 2020-04-28 18:07:39 +00:00
Author
Copy Link

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

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
witten commented 2020-04-28 19:45:56 +00:00
Owner
Copy Link

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).

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).
kaechele commented 2020-05-16 02:30:09 +00:00
Contributor
Copy Link

The situation was similar on CentOS 7 and that's why I moved to the pip packages in a virtualenv.

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 situation was similar on CentOS 7 and that's why I moved to the pip packages in a virtualenv. 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.
witten commented 2020-05-18 16:05:57 +00:00
Owner
Copy Link

borgmatic sometimes sees releases in such quick succession

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.)

> borgmatic sometimes sees releases in such quick succession 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.)
Firesphere commented 2022-02-07 01:50:11 +00:00
Copy Link

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.)

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.)
witten commented 2022-02-07 03:08:08 +00:00
Owner
Copy Link

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:

  1. Use pip to install a recent version of borgmatic and then subscribe to the releases page, so you're notified of new releases.
  2. Use an alternate installation method for borgmatic such as a Docker image. (Although you may encounter platform issues with certain images on a Raspberry Pi.)
  3. Upgrade to a more recent version of Debian that contains a more recent (but still outdated) version of borgmatic.
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: 1. Use `pip` to install a recent version of borgmatic and then subscribe to the releases page, so you're notified of new releases. 2. Use an [alternate installation method](https://torsion.org/borgmatic/docs/how-to/set-up-backups/#other-ways-to-install) for borgmatic such as a Docker image. (Although you may encounter platform issues with certain images on a Raspberry Pi.) 3. Upgrade to a more recent version of Debian that contains a more recent (but still outdated) version of borgmatic.
Firesphere commented 2022-02-08 05:33:14 +00:00
Copy Link

Use 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.

> Use 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.
witten commented 2022-02-08 05:36:19 +00:00
Owner
Copy Link

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.

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](https://archlinux.org/packages/extra/any/borgmatic/) there.
witten added the
new feature area
 label 2023-06-28 18:52:49 +00:00
witten commented 2023-09-12 04:28:43 +00:00
Owner
Copy Link

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.

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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
spot-check
1.8.10
1.8.9
1.8.8
1.8.7
1.8.6
1.8.5
1.8.4
1.8.3
1.8.2
1.8.1
1.8.0
1.7.15
1.7.14
1.7.13
1.7.12
1.7.11
1.7.10
1.7.9
1.7.8
1.7.7
1.7.6
1.7.5
1.7.4
1.7.3
1.7.2
1.7.1
1.7.0
1.6.6
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.24
1.5.23
1.5.22
1.5.21
1.5.20
1.5.19
1.5.18
1.5.17
1.5.16
1.5.15
1.5.14
1.5.13
1.5.12
1.5.11
1.5.10
1.5.9
1.5.8
1.5.7
1.5.7.dev0
1.5.6
1.5.5
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.22
1.4.21
1.4.20
1.4.19
1.4.18
1.4.17
1.4.16
1.4.15
1.4.14
1.4.13
1.4.12
1.4.11
1.4.10
1.4.9
1.4.8
1.4.7
1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.26
1.3.25
1.3.24
1.3.23
1.3.22
1.3.21
1.3.20
1.3.19
1.3.18
1.3.17
1.3.16
1.3.15
1.3.14
1.3.13
1.3.12
1.3.11
1.3.10
1.3.9
1.3.8
1.3.7
1.3.6
1.3.5
1.3.4
1.3.3
1.3.2
1.3.1
1.3.0
1.2.18
1.2.17
1.2.16
1.2.15
1.2.14
1.2.13
1.2.12
1.2.11
1.2.10
1.2.9
1.2.8
1.2.7
1.2.6
1.2.5
1.2.4
1.2.3
1.2.2
1.2.1
1.2.0
1.1.15
1.1.14
1.1.13
1.1.12
1.1.11
1.1.10
1.1.9
1.1.7
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.3
1.0.2
1.0.1
1.0.0
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
0.0.7
0.0.6
0.0.5
0.0.4
0.0.3
0.0.2
Labels
Clear labels   
bug

   
data loss

   
design finalized

   
good first issue

   
new feature area

   
question / support

   
security

   
waiting for response
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#302
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?