[GH-ISSUE #8] failed to select a version for the requirement pxar = "^0.6.1" #9

Closed
opened 2026-02-27 21:01:09 +03:00 by kerem · 2 comments
Owner

Originally created by @Naolador on GitHub (Feb 15, 2021).
Original GitHub issue: https://github.com/sg4r/proxmox-backup-client/issues/8

OS: CentOS Linux release 7.6.1810 and CentOS Linux release 7.5.1804

After issued bash ./pbs.build.sh, the installation couldn't proceed. Below is the output:

# bash pbs.build.sh
Cloning into 'proxmox'...
remote: Enumerating objects: 5368, done.
remote: Counting objects: 100% (5368/5368), done.
remote: Compressing objects: 100% (2005/2005), done.
remote: Total 5368 (delta 3268), reused 5368 (delta 3268)
Receiving objects: 100% (5368/5368), 929.79 KiB | 382.00 KiB/s, done.
Resolving deltas: 100% (3268/3268), done.
Cloning into 'proxmox-backup'...
remote: Enumerating objects: 29549, done.
remote: Counting objects: 100% (29549/29549), done.
remote: Compressing objects: 100% (6714/6714), done.
remote: Total 29549 (delta 22517), reused 29549 (delta 22517)
Receiving objects: 100% (29549/29549), 6.02 MiB | 2.27 MiB/s, done.
Resolving deltas: 100% (22517/22517), done.
Note: checking out '4dec479d2c46bd8cec28c1faa17aa013307de764'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 4dec479... update d/control
patching file .cargo/config
patching file proxmox/Cargo.toml
patching file proxmox/src/sys/linux/mod.rs
Note: checking out '2d87f2fb73b9629abdfac18aefac213b9130a609'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 2d87f2f... bump version to 1.0.6-1
patching file .cargo/config
patching file Cargo.toml
patching file src/api2/node.rs
patching file src/tools/daemon.rs
patching file src/tools.rs
    Updating crates.io index
    Updating git repository `git://git.proxmox.com/git/pathpatterns.git`
    Updating git repository `git://git.proxmox.com/git/proxmox-fuse.git`
    Updating git repository `git://git.proxmox.com/git/pxar.git`
error: failed to sync

Caused by:
  failed to load pkg lockfile

Caused by:
  failed to select a version for the requirement `pxar = "^0.6.1"`
  candidate versions found which didn't match: 0.8.0
  location searched: Git repository git://git.proxmox.com/git/pxar.git
  required by package `proxmox-backup v1.0.6 (/root/proxmox-backup-client/proxmox-backup)`
error: failed to get `pathpatterns` as a dependency of package `proxmox-backup v1.0.6 (/root/proxmox-backup-client/proxmox-backup)`

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

Caused by:
  Unable to update git://git.proxmox.com/git/pathpatterns.git

Caused by:
  the source git://git.proxmox.com/git/pathpatterns.git requires a lock file to be present first before it can be
  used against vendored source code

  remove the source replacement configuration, generate a lock file, and then
  restore the source replacement configuration to continue the build
error: failed to get `pathpatterns` as a dependency of package `proxmox-backup v1.0.6 (/root/proxmox-backup-client/proxmox-backup)`

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

Caused by:
  Unable to update git://git.proxmox.com/git/pathpatterns.git

Caused by:
  the source git://git.proxmox.com/git/pathpatterns.git requires a lock file to be present first before it can be
  used against vendored source code

  remove the source replacement configuration, generate a lock file, and then
  restore the source replacement configuration to continue the build

My testing machine with the same OS version works.

Originally created by @Naolador on GitHub (Feb 15, 2021). Original GitHub issue: https://github.com/sg4r/proxmox-backup-client/issues/8 OS: CentOS Linux release 7.6.1810 and CentOS Linux release 7.5.1804 After issued bash ./pbs.build.sh, the installation couldn't proceed. Below is the output: ``` # bash pbs.build.sh Cloning into 'proxmox'... remote: Enumerating objects: 5368, done. remote: Counting objects: 100% (5368/5368), done. remote: Compressing objects: 100% (2005/2005), done. remote: Total 5368 (delta 3268), reused 5368 (delta 3268) Receiving objects: 100% (5368/5368), 929.79 KiB | 382.00 KiB/s, done. Resolving deltas: 100% (3268/3268), done. Cloning into 'proxmox-backup'... remote: Enumerating objects: 29549, done. remote: Counting objects: 100% (29549/29549), done. remote: Compressing objects: 100% (6714/6714), done. remote: Total 29549 (delta 22517), reused 29549 (delta 22517) Receiving objects: 100% (29549/29549), 6.02 MiB | 2.27 MiB/s, done. Resolving deltas: 100% (22517/22517), done. Note: checking out '4dec479d2c46bd8cec28c1faa17aa013307de764'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at 4dec479... update d/control patching file .cargo/config patching file proxmox/Cargo.toml patching file proxmox/src/sys/linux/mod.rs Note: checking out '2d87f2fb73b9629abdfac18aefac213b9130a609'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at 2d87f2f... bump version to 1.0.6-1 patching file .cargo/config patching file Cargo.toml patching file src/api2/node.rs patching file src/tools/daemon.rs patching file src/tools.rs Updating crates.io index Updating git repository `git://git.proxmox.com/git/pathpatterns.git` Updating git repository `git://git.proxmox.com/git/proxmox-fuse.git` Updating git repository `git://git.proxmox.com/git/pxar.git` error: failed to sync Caused by: failed to load pkg lockfile Caused by: failed to select a version for the requirement `pxar = "^0.6.1"` candidate versions found which didn't match: 0.8.0 location searched: Git repository git://git.proxmox.com/git/pxar.git required by package `proxmox-backup v1.0.6 (/root/proxmox-backup-client/proxmox-backup)` error: failed to get `pathpatterns` as a dependency of package `proxmox-backup v1.0.6 (/root/proxmox-backup-client/proxmox-backup)` Caused by: failed to load source for dependency `pathpatterns` Caused by: Unable to update git://git.proxmox.com/git/pathpatterns.git Caused by: the source git://git.proxmox.com/git/pathpatterns.git requires a lock file to be present first before it can be used against vendored source code remove the source replacement configuration, generate a lock file, and then restore the source replacement configuration to continue the build error: failed to get `pathpatterns` as a dependency of package `proxmox-backup v1.0.6 (/root/proxmox-backup-client/proxmox-backup)` Caused by: failed to load source for dependency `pathpatterns` Caused by: Unable to update git://git.proxmox.com/git/pathpatterns.git Caused by: the source git://git.proxmox.com/git/pathpatterns.git requires a lock file to be present first before it can be used against vendored source code remove the source replacement configuration, generate a lock file, and then restore the source replacement configuration to continue the build ``` My testing machine with the same OS version works.
kerem closed this issue 2026-02-27 21:01:10 +03:00
Author
Owner

@halo779 commented on GitHub (Feb 17, 2021):

This seems to be caused by cargo only pulling the latest copy of pxar.

Building is possible by setting rev = 4f2d271a9608b576bf2dad22672a930285b5d7dd
Will put a PR in, but probably just as much value to upgrade to 1.0.8 now that it's out

<!-- gh-comment-id:780269594 --> @halo779 commented on GitHub (Feb 17, 2021): This seems to be caused by cargo only pulling the latest copy of pxar. Building is possible by setting rev = 4f2d271a9608b576bf2dad22672a930285b5d7dd Will put a PR in, but probably just as much value to upgrade to 1.0.8 now that it's out
Author
Owner

@halo779 commented on GitHub (Feb 17, 2021):

PR #9 Created to resolve this issue.

<!-- gh-comment-id:780276721 --> @halo779 commented on GitHub (Feb 17, 2021): PR #9 Created to resolve this issue.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/proxmox-backup-client#9
No description provided.