Summary: | eselect binutils list - !!! Error: Pattern does not match any installed version of binutils! | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Mark Knecht <markknecht> |
Component: | eselect | Assignee: | Gentoo eselect Team <eselect> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch for binutils.eselect |
Description
Mark Knecht
2012-06-25 20:05:40 UTC
Confirmed (on a system with a great variety of binutils versions/targets installed). Since Mike Frysinger appears reluctant to commit to eselect modules, this one should probably be deprecated in favour of sys-devel/binutils-config. OK, it does appears that binutils-config is at least functional here. As I'm just an end user type I only have one package installed so I can't do much testing. I suppose maybe other users will run across this one day or possibly Mike will do some updates when he gets time. If he does then I'll get a response to this report I suppose. Thanks for confirming. What is the output of "echo -*" (in the same directory where you executed eselect)? Interesting. On one of the machines that's failing: mark@c2stable ~ $ su - Password: c2stable ~ # eselect binutils list !!! Error: Pattern does not match any installed version of binutils! exiting c2stable ~ # echo -* --help -q c2stable ~ # whereas on a machine that's working it only reports -q and give 2.21.1 as the version that's set. Created attachment 316441 [details, diff]
Patch for binutils.eselect
Attached patch should fix it.
Please test.
That seems to have worked for me, at least on this one machine: c2stable modules # patch <~mark/Downloads/binselect.patch patching file binutils.eselect c2stable modules # vi binutils.eselect c2stable modules # eselect binutils list Installed binutils for target x86_64-pc-linux-gnu [1] 2.21.1 * c2stable modules # Fixed in Git: <http://git.overlays.gentoo.org/gitweb/?p=proj/eselect.git;a=commit;h=d1b1a4320db209587216626fa744e6e5fcd0e43d> (In reply to comment #4) > c2stable ~ # echo -* > --help -q As a workaround until the next eselect release, you could remove these files whose names start with a hyphen, or execute the eselect command from a different directory. Thanks. It's funny that those files were even there. I suppose they were left over from some mistyped CLI execution or something. Once I removed them eselect worked fine there just as it did in other directories. Thanks for looking into this and good to know future users won't have to go through this confusion. Fixed in eselect-1.3.2. Thanks for reporting. |