Package Details: proxmox-backup-client 4.1.0-1

Git Clone URL: https://aur.archlinux.org/proxmox-backup-client.git (read-only, click to copy)
Package Base: proxmox-backup-client
Description: Client for Proxmox Backup Server
Upstream URL: https://pbs.proxmox.com
Keywords: backup pbs proxmox pve rust
Licenses: AGPL3
Submitter: flumm
Maintainer: flumm (tommitscheck)
Last Packager: tommitscheck
Votes: 25
Popularity: 0.84
First Submitted: 2020-07-15 08:23 (UTC)
Last Updated: 2025-11-26 12:55 (UTC)

Latest Comments

1 2 3 4 5 6 7 Next › Last »

OJaksch commented on 2025-11-26 13:01 (UTC)

x-mas today! PBS 4.1 released and a fresh, suitable and up2date client for Arch!
As always: Many thanks!

OJaksch commented on 2025-11-26 09:00 (UTC)

Thanks, mate! Meanwhile I'm doing the restore by "mount". Slow but working.

tommitscheck commented on 2025-11-26 08:58 (UTC)

@OJaksch I'll look into doing a bump soon, hopefully later today but in any case still this week.

OJaksch commented on 2025-11-26 08:50 (UTC) (edited on 2025-11-26 08:51 (UTC) by OJaksch)

I beg for pardon but think I have to bump the "out of date" request, because it looks like that I'm stumbling over an existing bug in this old version while restoring some data from PBS:

https://forum.proxmox.com/threads/solved-pve-beta-9-cannot-restore-lxc-from-pbs-works-on-general-release-9-now.168633/post-784494

chrhasse commented on 2025-06-16 09:53 (UTC)

After looking into it, it seems that pxar, pathpatterns, and proxmox-fuse have all updated their version numbers to 1.0. Making them use a specific commit from before the version number change like

    "proxmox-fuse::git://git.proxmox.com/git/proxmox-fuse.git#commit=dc151753b3ef3661b171f0439aa60f59e3568395"
    "pxar::git://git.proxmox.com/git/pxar.git#commit=16773abdda5eb260216e3ed021309cfa32416b38"
    "pathpatterns::git://git.proxmox.com/git/pathpatterns.git#commit=394f6f679a54d014f8a29241b9f03e124f2a7726"

or patching Cargo.toml to use 1.0 instead of the old version numbers fixes the build for me.

chrhasse commented on 2025-06-12 00:22 (UTC)

I'm not sure if this is a personal issue, but the package has been failing to build with the error

    Updating crates.io index
error: failed to select a version for the requirement `pathpatterns = "^0.3"`
candidate versions found which didn't match: 1.0.0, 0.1.2
location searched: crates.io index
required by package `pbs-client v0.1.0 (/home/echo/.cache/paru/clone/proxmox-backup-client/src/proxmox-backup-client-3.3.4/pbs-client)

As far as I can tell the path overrides don't seem to be applying but I have no idea why or if it's limited to my system

tommitscheck commented on 2025-05-31 13:15 (UTC)

Thanks for your report and posting a workaround; I wanted to bump this again since a bit, but due to Debian Bookworm based release using older hyper/http crates with some downstream patches it would have been a bit more involved.

But at Proxmox upstream we get slowly towards the next major release, so it shouldn't be that long anymore.

I might do a simple revision bump to ensure the package gets rebuild with the newer FUSE lib though.

Behem0th commented on 2025-05-31 11:21 (UTC) (edited on 2025-05-31 11:22 (UTC) by Behem0th)

On the latest updated Arch PBC crashes with this error:

proxmox-backup-client: error while loading shared libraries: libfuse3.so.3: cannot open shared object file: No such file or directory
root-> ls -l /usr/lib/libfuse3*
lrwxrwxrwx 1 root root   13 мар 25 08:53 /usr/lib/libfuse3.so -> libfuse3.so.4
-rwxr-xr-x 1 root root 255K мар 25 08:53 /usr/lib/libfuse3.so.3.17.1
lrwxrwxrwx 1 root root   18 мар 25 08:53 /usr/lib/libfuse3.so.4 -> libfuse3.so.3.17.1

For solve this issue i know 2 way

1`st Create link

ln -s usr/lib/libfuse3.so usr/lib/libfuse3.so.3

2`nd Patch elf

patchelf --replace-needed libfuse3.so.3 libfuse3.so /usr/bin/proxmox-backup-client

OJaksch commented on 2025-04-01 13:14 (UTC)

Phantastic work, many thanks - as always!
While being there and testing I did this also on my RPi400/aarch64 which went fine. Yeah!

tommitscheck commented on 2025-04-01 12:16 (UTC)

Thanks for the hint, while at it, I pushed a package update based on 3.3.4, not much changed w.r.t. client feature-wise, but it should not hurt to avoid a too big gap with upstream here.