| 1 |
On Wed, Jun 27, 2012 at 11:26 AM, Paul Hartman |
| 2 |
<paul.hartman+gentoo@×××××.com> wrote: |
| 3 |
> On Wed, Jun 27, 2012 at 9:34 AM, Mark Knecht <markknecht@×××××.com> wrote: |
| 4 |
>> On Tue, Jun 26, 2012 at 8:27 PM, Paul Hartman |
| 5 |
>> <paul.hartman+gentoo@×××××.com> wrote: |
| 6 |
>>> On Sun, Jun 24, 2012 at 1:27 PM, Mark Knecht <markknecht@×××××.com> wrote: |
| 7 |
>>>> Hi, |
| 8 |
>>>> One of my machines is giving an undesired response in eselect: |
| 9 |
>>>> |
| 10 |
>>>> c2stable ~ # eselect binutils list |
| 11 |
>>>> !!! Error: Pattern does not match any installed version of binutils! |
| 12 |
>>>> exiting |
| 13 |
>>>> c2stable ~ # |
| 14 |
>>> |
| 15 |
>>> Mine does the same thing on 1 computer but works on 2 others. All with |
| 16 |
>>> the same versions of all involved packages. Weird. |
| 17 |
>>> |
| 18 |
>> |
| 19 |
>> Hey, at least I'm in good company if my old friend Paul Hartman sees |
| 20 |
>> the same thing. :-) |
| 21 |
>> |
| 22 |
>> There is a patch to the binutils.eselect file here that worked for me: |
| 23 |
>> |
| 24 |
>> https://423525.bugs.gentoo.org/attachment.cgi?id=316441 |
| 25 |
>> |
| 26 |
>> Before patching (if you do at all - I recommend you don't patch unless |
| 27 |
>> you just want to) run this command in the directory you are running |
| 28 |
>> eselect in. (For me it was just /root) |
| 29 |
>> |
| 30 |
>> echo -* |
| 31 |
>> |
| 32 |
>> On a 'good' machine it returns |
| 33 |
>> |
| 34 |
>> -q |
| 35 |
>> |
| 36 |
>> On a 'bad' machine here it returns |
| 37 |
>> |
| 38 |
>> --help -q |
| 39 |
>> |
| 40 |
>> I don't think the machine is really bad. I think eselect was likely |
| 41 |
>> just not being selective enough about how it works with whatever is in |
| 42 |
>> the directory or search path? Not sure. |
| 43 |
>> |
| 44 |
>> If you see something different you might add it to the bug report but |
| 45 |
>> I suspect we've got the same issue. |
| 46 |
> |
| 47 |
> Ah-ha. When I run the command from a directory which does not contain |
| 48 |
> any files or dirs starting with hyphen, it is fine. In my user dir |
| 49 |
> there is ~/- directory for some reason, so that must have been |
| 50 |
> confusing it. |
| 51 |
> |
| 52 |
|
| 53 |
Yes, same here. |
| 54 |
|
| 55 |
rm -- -q |
| 56 |
rm -- --help |
| 57 |
|
| 58 |
and now eselect binutils list works fine. |
| 59 |
|
| 60 |
The devs have now patched eselect in git to fix this in a future |
| 61 |
release. In my case I suspect that I executed some command where I was |
| 62 |
looking for help (--help) but the command was mistyped and I got a |
| 63 |
file as output, etc. Not sure how you got a directory but if there's |
| 64 |
nothing in it you care about then I suppose |
| 65 |
|
| 66 |
rm -- ~/- |
| 67 |
|
| 68 |
would clean it up and eselect would probably work for you also. |
| 69 |
|
| 70 |
Cheers, |
| 71 |
Mark |
Archives