-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fzf-make: 0.9.0 -> 0.11.0 #274362
fzf-make: 0.9.0 -> 0.11.0 #274362
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
panic: Any { .. }
when running :<
Just played around with it as well. Do older versions work fine with Makefiles that are now causing issues? Because I quickly realized that this doesn't work well with advanced makefiles. |
This seems to be an issue with the Makefile being too complex to parse? |
I'm sorry about
@Ma27 (EDIT) |
I think this might be fixed in the next release, except from this, seems like it works as intended. |
Fair, sounded like it was a regression to me, but then we can merge this already. |
I released the |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kyu08/fzf-make/releases.
meta.description for fzf-make is: Fuzzy finder for Makefile
meta.homepage for fzf-make is: https://github.com/kyu08/fzf-make
meta.changelog for fzf-make is: https://github.com/kyu08/fzf-make/releases/tag/v0.11.0
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done (click to expand)
passthru.tests
, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-users
list or you can usesudo
since root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-review
run on x86_64-linux 11 package built:
Maintainer pings
cc @figsoda @Sigmanificient for testing.