Arch Linux User Repository

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.

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

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.

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

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

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.

The package "fuse" got an update and therefore pbc needs to be recompiled.
Would it be a wise idea just to increment this package to 3.3.2-4 to force people to recompile pbc before they are trusting their now not-working background backups blindly?

@OJaksch: Thanks for your feedback, great to hear that it works now.

The warning is expected with newer rustc versions, but nothing to worry about and also happens on x86-64, we will improve the code style here probably soonish to avoid the warning.

Of course, friend. Just compiled it on my RPi400 w/o any problems now.
There is a security warning that I don't know if it is relevant.

   Compiling pxar v0.12.1 (/var/cache/pacman/pkg/yaourt/proxmox-backup-client/src/pxar)
warning: creating a mutable reference to mutable static is discouraged
  --> /var/cache/pacman/pkg/yaourt/proxmox-backup-client/src/pxar/src/decoder/mod.rs:35:21
   |
35 |     unsafe { &mut (*SCRATCH_BUFFER.as_mut_ptr())[..] }
   |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
   |
   = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/static-mut-references.html>
   = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives
   = note: `#[warn(static_mut_refs)]` on by default

warning: `pxar` (lib) generated 1 warning

@OJaksch: argh, I made a stupid mistake, can you please retry the just pushed 3.3.2-3 version?