pve-manager: 8.2.4 -> 8.2.9

[proxmox-update]

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for pve-manager is: The Proxmox VE Manager API and Web UI repository

meta.homepage for pve-manager is: git://git.proxmox.com/?p=pve-manager.git

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

Impact

Checks done

---

• built on NixOS
• Warning: a test defined in passthru.tests did not pass
• found 8.2.9 with grep in /nix/store/9ydanjrh7qm22cn0v4nrq31ckvbvh1dq-pve-manager-8.2.9
• found 8.2.9 in filename of file in /nix/store/9ydanjrh7qm22cn0v4nrq31ckvbvh1dq-pve-manager-8.2.9

---

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pve-manager

Instructions to test this update (click to expand)

---

Build yourself:

nix-build -A pve-manager https://github.com/proxmox-update/nixpkgs/archive/c236efa0d2aa0cafc7d48cf3cc7c9792559d2820.tar.gz

Or:

nix build github:proxmox-update/nixpkgs/c236efa0d2aa0cafc7d48cf3cc7c9792559d2820#pve-manager

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/9ydanjrh7qm22cn0v4nrq31ckvbvh1dq-pve-manager-8.2.9
ls -la /nix/store/9ydanjrh7qm22cn0v4nrq31ckvbvh1dq-pve-manager-8.2.9/bin

---

Pre-merge build results

NixPkgs review skipped

---

Maintainer pings

cc @camillemndn @JulienMalka for testing.

[JulienMalka]

Looks like all these updates are blocked because we are missing the proxmox::SharedCache package.

[mjm]

I tried looking into this. It seems like it needs an update to pve-rs to get the SharedCache package. I made a few tweaks to the update.py script to try to get that to work, but hit a roadblock.

There's a new proxmox-ve-config dependency, which is kept in a proxmox-ve-rs git repo. I got the update script to set the correct git repo for that in Cargo.toml, but then it can't generate the lockfile because proxmox-ve-config depends on proxmox-schema which is in the proxmox.git repo. We aren't able to update its Cargo.toml to point it at git tho, so it can't find the package.

It seems to be a more general issue of how we can handle transitive proxmox crate dependencies. Maybe that hasn't been an issue before? But it's unclear to me how to get it to work. I might keep poking at it but I'm not an expert in managing Rust dependencies, so idk how far I'll be able to get.