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

D

DerEnderKeks

Member
Jun 3, 2022
9
14
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.
 
  • Like
Reactions: in-famous-raccoon, Johannes S, gyptazy and 8 others
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
DerEnderKeks said:
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)
Click to expand...
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
sterzy said:
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.
Click to expand...
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
Hello,

thanks for your work on an rpm package!
Would it also be possible to create/support a package for opensuse?
 
Last edited:
Installation has worked. :D

Here are the steps I took:
# Added the Key
Code: 
sudo rpm --import https://download.copr.fedorainfracloud.org/results/derenderkeks/proxmox-backup-client/pubkey.gpg
# Added Repo
Code: 
sudo zypper ar -cfg https://copr.fedorainfracloud.org/coprs/derenderkeks/proxmox-backup-client/repo/opensuse-tumbleweed/derenderkeks-proxmox-backup-client-opensuse-tumbleweed.repo
# Refresh
Code: 
sudo zypper ref
Warning: File 'repomd.xml' from repository 'Copr repo for proxmox-backup-client owned by derenderkeks' is unsigned.

    Note: Signing data enables the recipient to verify that no modifications
    occurred after the data were signed. Accepting data with no, wrong or
    unknown signature can lead to a corrupted system and in extreme cases even
    to a system compromise.

    Note: File 'repomd.xml' is the repositories master index file. It ensures
    the integrity of the whole repo.

    Warning: We can't verify that no one meddled with this file, so it might not
    be trustworthy anymore! You should not continue unless you know it's safe.

File 'repomd.xml' from repository 'Copr repo for proxmox-backup-client owned by derenderkeks' is unsigned.
Continue? [yes/no] (no):

Is that something you can activate/fix?
Otherwise, the installation is fine and I have already been able to perform a first benchmark test. I will test a backup this evening.

Thanks again for the package and the quick response!

Edit: I've found this Link which said: gpg signature must exist in the remote repository under repodata/repomd.xml.asc - would it be possible that you add this to your repo? then there would be no warning when adding your repo.

Edit2: The backup of my pc also ran without any problems! Thank you!
 
Last edited:
You must log in or register to reply here.
Top Bottom