Inofficial proxmox-backup-client RPM builds for RHEL-based distros

DerEnderKeks

Member
Jun 3, 2022
7
13
8
Since there is currently no official RPM build, I created automated builds of the proxmox-backup-client for RHEL based distros on Fedora's COPR.

You can find the builds and further instructions here: https://copr.fedorainfracloud.org/coprs/derenderkeks/proxmox-backup-client/
The source for the builds is here: https://gitlab.com/DerEnderKeks/proxmox-backup-client-rpm

My builds are available for amd64 and aarch64, and are mostly based on the version from the AUR. I'm currently using them on Rocky Linux 9 without any problems.
If you have any issues with the builds or need a build for a RHEL-based distro that is currently not built in COPR, just let me know (here or, preferably, in a Gitlab issue).


Installation:​

First, enable the copr repo:

dnf copr enable derenderkeks/proxmox-backup-client

Now you can install the proxmox-backup-client package:

dnf install proxmox-backup-client

You can now use the proxmox-backup-client and pxar binaries.


If you want to use the SRPMs for some reason, note that they do not actually contain any source code, since for unknown reasons the Proxmox devs don't publish their crates to the crates.io registry. This makes it way harder to do it the proper™ way and I thus just put a script into SRPM that downloads everything from their Git repos during the actual build. This doesn't influence the final RPM though.
 
Amazing work, runs fine on Fedora 40!

It would be great if you could also port the latest 3.2.x client, because it adds new changes detection modes which should significantly improve backup speed.
 
  • Like
Reactions: lpowers-ucsf
I updated my build to 3.2.7.
Unfortunately it no longer builds on aarch64 (x86_64 still works though). This seems to be caused by a change in the proxmox dependency (specifically this commit). Maybe the Proxmox devs could take a look at this. (Blatantly pinging @sterzy, author of the relevant commit)
Hi, we don't really support aarch64 officially, so this probably won't be fixed. However, that commit should only really be relevant for the backend. You can try to revert that commit if you just want to build the client as that change shouldn't be relevant for the client to function.
 
  • Like
Reactions: Johannes S
You can try to revert that commit if you just want to build the client as that change shouldn't be relevant for the client to function.
Thanks for the hint! Instead of reverting the commit I ended up adding a patch to fix the data type in the two problematic lines. My build now also works for aarch64 again.
I'd submit this patch upstream, but I really don't want to bother with the archaic mailing list workflow.. @sterzy maybe you could add this patch to the proxmox repo.
 
  • Like
Reactions: Johannes S

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!