| 1 |
walt <w41ter@×××××.com> [12-04-15 17:24]: |
| 2 |
> On 04/14/2012 07:46 PM, meino.cramer@×××.de wrote: |
| 3 |
> > Running |
| 4 |
> > |
| 5 |
> > glsa-check -p affected |
| 6 |
> > |
| 7 |
> > |
| 8 |
> > produces: |
| 9 |
> > |
| 10 |
> > solfire:/root>glsa-check -p affected |
| 11 |
> > zsh: /usr/bin/glsa-check: bad interpreter: /usr/local/bin/python: no such file or directory |
| 12 |
> |
| 13 |
> On my machines glsa-check returns nothing, but I don't have zsh installed. |
| 14 |
> Maybe zsh installs its own config files that set a hard-coded path for the |
| 15 |
> python interpreter? Dunno. What happens if you run glsa-check from a bash |
| 16 |
> prompt instead of zsh? |
| 17 |
> |
| 18 |
> |
| 19 |
In the meanwhile I found: |
| 20 |
|
| 21 |
The reason was the first lines in the effected scripts: |
| 22 |
#! /usr/local/bin/python |
| 23 |
|
| 24 |
Fixing this to |
| 25 |
#! /usr/bin/python |
| 26 |
|
| 27 |
fixed that problem. |
| 28 |
|
| 29 |
Best regards, |
| 30 |
mcc |
Archives