Skip to content
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

Update fedora repository version (Rawhide and Fedora 40) #3827

Open
3 of 10 tasks
egor-denysenko opened this issue May 31, 2024 · 2 comments
Open
3 of 10 tasks

Update fedora repository version (Rawhide and Fedora 40) #3827

egor-denysenko opened this issue May 31, 2024 · 2 comments

Comments

@egor-denysenko
Copy link

Checklist

  • I have read through the manual page (man fzf)
  • I have searched through the existing issues
  • For bug reports, I have checked if the bug is reproducible in the latest version of fzf

Output of fzf --version

0.44.1 (Fedora)

OS

  • Linux
  • macOS
  • Windows
  • Etc.

Shell

  • bash
  • zsh
  • fish

Problem / Steps to reproduce

Hi, I currently drive FZF on my personal machine, and I'm using Fedora. 

I have noticed from the fedora packages website that the current Rawhide and Fedora 40 versions of fzf are quite behide in comparison to the actual releases. Currently, fedora packages has 0.44.1 as the latest version, and the latest is 0.52.1;

Is there any way I can help and update the current package version, or is it something that a maintainer can do?

@junegunn
Copy link
Owner

junegunn commented Jun 1, 2024

Not sure why the version is so lagging behind. You should probably ask for an update on https://bugzilla.redhat.com/.

With shell integration scripts embedded in the binary (i.e. --bash, --zsh, and --fish), and with native tmux integration and man page inclusion in the upcoming release, it's getting easier to use the latest version of fzf simply by downloading the binary from the releases page and putting it in your $PATH.

@egor-denysenko
Copy link
Author

Thanks I didn't know that fedora tracked packages update on bugzilla.

It seems that it's a stale bug from here

I'm going to try to push it or somehow figure out how to help there.
I specifically pushed for dnf since I didn't want to manage the binary myself but let it be managed by dnf.
I will post some updates if I'm able to figure out something or update the package on the dnf registry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants