lastpass-cli: fix build failure with cmake 4#452443
Conversation
|
|
@NixOS/nixpkgs-merge-bot merge |
466d082 to
a012871
Compare
|
|
@drawbu Have you consider vendoring this pr? |
a012871 to
232d467
Compare
|
Fair point @Sigmanificient! I haven't seen it, actually! Just modified the pr to integrate this fix instead of the |
232d467 to
20b66a0
Compare
- CMake 4 is no longer retro compatible with versions < 3.5
20b66a0 to
02f2321
Compare
smancill
left a comment
There was a problem hiding this comment.
No need to add the patch to the tree.
Use fetchpatch to get it directly from:
https://github.com/lastpass/lastpass-cli/commit/31a4ad5f735933ff8e96403103d5b4f61faee945.patch
From what I understood it was actually preferred to vendor the patches to avoid GitHub garbage collecting the commit. But I can change it if you prefer! |
|
@smancill When a pr is made to upstream, the patch should be venderored until resolution, see: |
|
ok, I didn't realize it wasn't merged into upstream repo. I am merging this then. |
Fix
lastpass-clibuild failure on newer cmake 4.Applied patch from PR upstream.
curl -L https://patch-diff.githubusercontent.com/raw/lastpass/lastpass-cli/pull/716.patch > pkgs/by-name/la/lastpass-cli/716-bump-cmake-minimum-version.patchThings done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.