walt <w41...@gmail.com> [12-04-15 17:24]: > On 04/14/2012 07:46 PM, meino.cra...@gmx.de wrote: > > Running > > > > glsa-check -p affected > > > > > > produces: > > > > solfire:/root>glsa-check -p affected > > zsh: /usr/bin/glsa-check: bad interpreter: /usr/local/bin/python: no > > such file or directory > > On my machines glsa-check returns nothing, but I don't have zsh installed. > Maybe zsh installs its own config files that set a hard-coded path for the > python interpreter? Dunno. What happens if you run glsa-check from a bash > prompt instead of zsh? > > In the meanwhile I found:
The reason was the first lines in the effected scripts: #! /usr/local/bin/python Fixing this to #! /usr/bin/python fixed that problem. Best regards, mcc
