AUR (en) - proxmox-backup-client

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: proxmox-backup-client 3.0.1-1

Package Actions

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:	18
Popularity:	0.51
First Submitted:	2020-07-15 08:23 (UTC)
Last Updated:	2023-06-28 12:53 (UTC)

Dependencies (11)

acl (acl-git)
fuse3 (fuse3-git)
gcc-libs (gccrs-libs-git, gcc-libs-git, gcc11-libs)
openssl (openssl-git, openssl-hardened, quictls-openssl, openssl-static)
cargo (rust-nightly-bin, cargo-git, rustup-git, rust, rustup) (make)
clang (clang8, clang-git, llvm-git, clang-minimal-git) (make)
git (git-vfs, git-run-command-patch-git, git-git, git-fc) (make)
llvm (llvm8, llvm-git, llvm-minimal-git) (make)
patchelf (make)
python-docutils (make)
python-sphinx (python-sphinx-git, python-sphinx71) (make)

Required by (0)

Sources (7)

Latest Comments

1 2 3 4 Next › Last »

OJaksch commented on 2023-06-28 15:03 (UTC)

A great pleasure to see your ongoing support to this package. Again, many thanks for your work!

tommitscheck commented on 2023-03-13 12:32 (UTC)

Then it's space of sonmething else, in any way, the failure happens on fetching the dependencies - so compilation hasn't even started to happen, thus cannot have failed. Can be disk space can be some cargo bug, broken memory, ... need more info for that to tell.

Try calling the failing cargo fetch command manually in the pbs source dir and see if it outputs more info, checking the journal/dmesg for a kernel oops could be helpful too.

astrapi commented on 2023-03-13 10:24 (UTC)

@tommitscheck: I use a VM with 8GB RAM, creating the x86_64 version works without any problems with this equipment.

tommitscheck commented on 2023-03-13 09:08 (UTC)

@astrapi seems rather you run out of memory or the like, as the "Killed" in the log line of:

/home/makepkg/.cache/yay/proxmox-backup-client/PKGBUILD: line 43: 27743 Killed cargo fetch --verbose --target "$CARCH-unknown-linux-gnu"

suggests.

astrapi commented on 2023-03-13 08:02 (UTC) (edited on 2023-03-13 08:03 (UTC) by astrapi)

Compilation fails on aarch64:


==> Starting prepare()...
applying patch '0001-re-route-dependencies-not-available-on-crates.io-to-.patch'
patching file Cargo.toml
Hunk #2 succeeded at 44 with fuzz 2.
applying patch '0002-docs-drop-all-but-client-man-pages.patch'
patching file docs/conf.py
patching file docs/Makefile
warning: /home/makepkg/.cache/yay/proxmox-backup-client/src/proxmox-backup-client-2.3.1/Cargo.toml: unused manifest key: workspace.pbs-api-types
warning: /home/makepkg/.cache/yay/proxmox-backup-client/src/proxmox-backup-client-2.3.1/Cargo.toml: unused manifest key: workspace.pbs-buildcfg
warning: /home/makepkg/.cache/yay/proxmox-backup-client/src/proxmox-backup-client-2.3.1/Cargo.toml: unused manifest key: workspace.pbs-client
warning: /home/makepkg/.cache/yay/proxmox-backup-client/src/proxmox-backup-client-2.3.1/Cargo.toml: unused manifest key: workspace.pbs-config
warning: /home/makepkg/.cache/yay/proxmox-backup-client/src/proxmox-backup-client-2.3.1/Cargo.toml: unused manifest key: workspace.pbs-datastore
warning: /home/makepkg/.cache/yay/proxmox-backup-client/src/proxmox-backup-client-2.3.1/Cargo.toml: unused manifest key: workspace.pbs-tape
warning: /home/makepkg/.cache/yay/proxmox-backup-client/src/proxmox-backup-client-2.3.1/Cargo.toml: unused manifest key: workspace.pbs-tools
warning: /home/makepkg/.cache/yay/proxmox-backup-client/src/proxmox-backup-client-2.3.1/Cargo.toml: unused manifest key: workspace.proxmox-rrd
    Updating crates.io index
  /home/makepkg/.cache/yay/proxmox-backup-client/PKGBUILD: line 43: 27743 Killed                  cargo fetch --verbose --target "$CARCH-unknown-linux-gnu"                                                   
==> ERROR: A failure occurred in prepare().

youduda commented on 2022-12-23 00:44 (UTC)

Compilation fails in a clean chroot environment due to some linking error to zlib. Any ideas why it does not include zlib into the library list to link against since the last release?

error: linking with `cc` failed: exit status: 1

  = note: "cc" "-m64" "/tmp/rustc26zrXC/symbols.o" <...> "-Wl,--as-needed" "-L" "/build/proxmox-backup-client/src/proxmox-backup-client-2.3.1/target/release/deps" "-L" "/build/proxmox-backup-client/src/proxmox-backup-client-2.3.1/target/release/build/zstd-sys-b2ef5dda1d4a1671/out" "-L" "/usr/lib64/rustlib/x86_64-unknown-linux-gnu/lib" "-Wl,-Bstatic" <...> "/build/proxmox-backup-client/src/proxmox-backup-client-2.3.1/target/release/deps/libzstd-16a1f189c0640886.rlib" "/build/proxmox-backup-client/src/proxmox-backup-client-2.3.1/target/release/deps/libzstd_safe-4e6073ce20f02f26.rlib" "/build/proxmox-backup-client/src/proxmox-backup-client-2.3.1/target/release/deps/libzstd_sys-4854b148300e0a6c.rlib" <...> "-Wl,-Bdynamic" "-lfuse3" "-lssl" "-lcrypto" "-luuid" "-lcrypt" "-lacl" "-lrt" "-lc" "-lcrypto" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-Wl,--eh-frame-hdr" "-Wl,-znoexecstack" "-L" "/usr/lib64/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/build/proxmox-backup-client/src/proxmox-backup-client-2.3.1/target/release/deps/proxmox_backup_client-fd811c9f5f811bc2" "-Wl,--gc-sections" "-pie" "-Wl,-zrelro,-znow" "-Wl,-O1" "-nodefaultlibs"
  = note: /usr/bin/ld: /build/proxmox-backup-client/src/proxmox-backup-client-2.3.1/target/release/deps/libzstd_safe-4e6073ce20f02f26.rlib(zstd_safe-4e6073ce20f02f26.zstd_safe.ac06af16-cgu.6.rcgu.o): in function `zstd_safe::compress_bound':
          zstd_safe.ac06af16-cgu.6:(.text._ZN9zstd_safe14compress_bound17hadae7f4e8f96b03bE+0x2): undefined reference to `ZSTD_compressBound'
          /usr/bin/ld: /build/proxmox-backup-client/src/proxmox-backup-client-2.3.1/target/release/deps/libzstd_safe-4e6073ce20f02f26.rlib(zstd_safe-4e6073ce20f02f26.zstd_safe.ac06af16-cgu.6.rcgu.o): in function `<zstd_safe::CCtx as core::default::Default>::default':
          <...>
          zstd_safe.ac06af16-cgu.6:(.text._ZN9zstd_safe19compress_using_dict17h3457076a503708c1E+0xf): undefined reference to `ZSTD_compress_usingDict'
          /usr/bin/ld: zstd_safe.ac06af16-cgu.6:(.text._ZN9zstd_safe19compress_using_dict17h3457076a503708c1E+0x1f): undefined reference to `ZSTD_isError'
          /usr/bin/ld: /build/proxmox-backup-client/src/proxmox-backup-client-2.3.1/target/release/deps/libzstd_safe-4e6073ce20f02f26.rlib(zstd_safe-4e6073ce20f02f26.zstd_safe.ac06af16-cgu.6.rcgu.o): in function `zstd_safe::dstream_in_size':
          zstd_safe.ac06af16-cgu.6:(.text._ZN9zstd_safe15dstream_in_size17h922f3cdb6ebb6fcdE+0x2): undefined reference to `ZSTD_DStreamInSize'
          collect2: error: ld returned 1 exit status

flumm commented on 2022-12-01 10:10 (UTC)

we updated the package again, and it works (tested on a fresh minimal arch install with only installing base-devel, git and the deps listed in makepkg that were missing)

the missing libssl.so error is probably only an issue when the package is not rebuilt (but i think that's a general issue with aur packages that link against libraries)

<deleted-account> commented on 2022-11-07 13:32 (UTC)

After the latest update of the openssl package, I'm getting the following error:

/usr/bin/proxmox-backup-client: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

Looks, like the openssl package dropped the dependency openssl-1.1 in this commit: https://github.com/archlinux/svntogit-packages/commit/beacb20de03d3412ea721b98ce42e009b2efdd37

I fixed it for me by installing openssl-1.1 but this might be solvable by recompiling the package as well.

tommitscheck commented on 2022-10-23 09:33 (UTC)

@knieselpriem:

Caused by: Read-only file system (os error 30)

Your (build) filesystem is read only, so cargo cannot download any dependencies, iow. seems unrelated to this package...

knieselpriem commented on 2022-10-23 09:22 (UTC) (edited on 2022-10-23 09:24 (UTC) by knieselpriem)

failed to get `anyhow` as a dependency of package `pbs-client v0.1.0` on x86-64 (6.0.2-2-MANJARO) with command pamac install proxmox-backup-client

applying patch '0001-re-route-dependencies-not-available-on-crates.io-to-.patch'
patching file Cargo.toml
warning: /var/cache/private/pamac/proxmox-backup-client/src/proxmox-backup-client-2.2.1/Cargo.toml: unused manifest key: workspace.pbs-api-types
warning: /var/cache/private/pamac/proxmox-backup-client/src/proxmox-backup-client-2.2.1/Cargo.toml: unused manifest key: workspace.pbs-buildcfg
warning: /var/cache/private/pamac/proxmox-backup-client/src/proxmox-backup-client-2.2.1/Cargo.toml: unused manifest key: workspace.pbs-client
warning: /var/cache/private/pamac/proxmox-backup-client/src/proxmox-backup-client-2.2.1/Cargo.toml: unused manifest key: workspace.pbs-config
warning: /var/cache/private/pamac/proxmox-backup-client/src/proxmox-backup-client-2.2.1/Cargo.toml: unused manifest key: workspace.pbs-datastore
warning: /var/cache/private/pamac/proxmox-backup-client/src/proxmox-backup-client-2.2.1/Cargo.toml: unused manifest key: workspace.pbs-tape
warning: /var/cache/private/pamac/proxmox-backup-client/src/proxmox-backup-client-2.2.1/Cargo.toml: unused manifest key: workspace.pbs-tools
warning: /var/cache/private/pamac/proxmox-backup-client/src/proxmox-backup-client-2.2.1/Cargo.toml: unused manifest key: workspace.proxmox-rest-server
warning: /var/cache/private/pamac/proxmox-backup-client/src/proxmox-backup-client-2.2.1/Cargo.toml: unused manifest key: workspace.proxmox-rrd
error: failed to get `anyhow` as a dependency of package `pbs-client v0.1.0 (/var/cache/private/pamac/proxmox-backup-client/src/proxmox-backup-client-2.2.1/pbs-client)`

Caused by:
failed to load source for dependency `anyhow`

Caused by:
Unable to update registry `crates-io`

Caused by:
failed to create directory `/.cargo/registry/index/github.com-1ecc6299db9ec823`

Caused by:
Read-only file system (os error 30)

How can I avoid this?