summarylogtreecommitdiffstats
path: root/0001-re-route-dependencies-not-available-on-crates.io-to-.patch
AgeCommit message (Collapse)Author
2024-04-25update to 3.2.2Thomas Lamprecht
Signed-off-by: Thomas Lamprecht <thomas@lamprecht.org>
2024-04-25disable link type optimization for nowThomas Lamprecht
causes package build failures with e.g. zstd linkage Signed-off-by: Thomas Lamprecht <thomas@lamprecht.org>
2023-11-30update to 3.1.2Thomas Lamprecht
Signed-off-by: Thomas Lamprecht <thomas@lamprecht.org>
2023-06-28bump version to 3.0.1Thomas Lamprecht
Signed-off-by: Thomas Lamprecht <thomas@lamprecht.org>
2023-03-29update patches for 2.4.1Thomas Lamprecht
Signed-off-by: Thomas Lamprecht <thomas@lamprecht.org>
2022-11-29update re-routing of dependencies for 2.3Thomas Lamprecht
Signed-off-by: Thomas Lamprecht <thomas@lamprecht.org>
2022-05-18update cargo dependency re-route patchThomas Lamprecht
Signed-off-by: Thomas Lamprecht <thomas@lamprecht.org>
2021-12-12bump version to 2.1.2, simpler proxmox dependency patchingThomas Lamprecht
Instead of updating the hdozens of places manually, or investing time into automating that, just use the `[patch.crates-io]` mechanism cargo provides and clone the main depednecy repos too, which would have be done anyway by cargo. Patching out most of the workspace-lib stayed the same. Also patch our proxmox crate to avoid a glob-import on anyhow, as that breaks resolbing `Ok()` to te Result tuple, as anyhow added an Ok helper function in 1.0.49 and glob-imports are *always* wrong.. Signed-off-by: Thomas Lamprecht <thomas@lamprecht.org>
2021-09-22update to 2.0.10Thomas Lamprecht
we need to rework the "re-route dependencies to git" approach a bit as PBS reorganized the source code drastically into workspaces, and cargo build/fetch always wants to download every dependency of all workspace-crates, so we need to remove some of the top-level workspace. But, the reorg makes also quite some things better, less linkage cruft, no need to patch the api anymore and faster build time Signed-off-by: Thomas Lamprecht <thomas@lamprecht.org>