Search Criteria
Package Details: fselect-bin 0.8.4-1
Git Clone URL: | https://aur.archlinux.org/fselect-bin.git (read-only, click to copy) |
---|---|
Package Base: | fselect-bin |
Description: | Find files with SQL-like queries |
Upstream URL: | https://github.com/jhspetersson/fselect |
Licenses: | MIT |
Conflicts: | fselect |
Provides: | fselect |
Submitter: | jtraub |
Maintainer: | jtraub |
Last Packager: | jtraub |
Votes: | 4 |
Popularity: | 0.000944 |
First Submitted: | 2021-03-14 21:35 (UTC) |
Last Updated: | 2023-07-10 19:07 (UTC) |
Latest Comments
4censord commented on 2023-06-19 11:17 (UTC) (edited on 2023-06-19 11:30 (UTC) by 4censord)
I have created a patch for the validation failure as @jtraub and @tee described. Always clearing the caches is not a real option.
Feel free to use that.
tee commented on 2023-05-19 11:58 (UTC)
I get the same issue as @jtraub due to the download file being the same in every release, please read https://wiki.archlinux.org/title/PKGBUILD#Sources:~:text=Warning%3A%20The%20downloaded%20source%20filename%20must%20be%20unique and update your PKGBUILD.
hannula commented on 2021-11-07 08:31 (UTC)
@jtraub Thanks, clearing the
paru
cache for this package finally solved the issue.jtraub commented on 2021-11-04 15:26 (UTC)
@hannula can you please try again. It looks like you either have issues with your internet connection or your drive is failing.
I have tried to install the package with paru in a clean chroot and it works just fine for me.
hannula commented on 2021-10-29 08:24 (UTC)
Hi, when trying to install this package with paru, I receive an error:
What could the underlying issue be? The package worked fine before version 0.7.7.
Batou commented on 2021-04-22 18:33 (UTC)
Thanks jtraub! The issue has been fixed.
jtraub commented on 2021-04-08 08:18 (UTC)
@Batou It seems that the issue has been resolved in 0.7.4. I've updated the package so could you please update
fselect
and test again?Batou commented on 2021-04-06 17:53 (UTC) (edited on 2021-04-06 17:55 (UTC) by Batou)
fselect-bin works fine for regular searches but I get this error if I try to use the interactive mode:
Does anyone know what the issue might be?