Hi folks,
Was able to update the gems without any problem, but when I try to
upgrade my app I’m getting the following error:
…/ruby/gems/1.8/gems/radiant-0.5.2/bin/radiant:281:in `popen’: No
such file or directory - radiant-0.5.0/script/version (Errno::ENOENT)
Note I had recently upgrade to 0.5.1. I’m running rails 1.1.6.
If I rename the script/version file to script/version.bak, the upgrade
seems to proceed ok, but it upgraded to 0.5.1 then 0.5.2. All is OK
in the end, but maybe there’s a certain upgrade path bug?
Thanks,
Chris
Chris Brooks wrote:
Was able to update the gems without any problem, but when I try to
upgrade my app I’m getting the following error:
…/ruby/gems/1.8/gems/radiant-0.5.2/bin/radiant:281:in `popen’: No
such file or directory - radiant-0.5.0/script/version (Errno::ENOENT)
That error is caused when you can’t execute script/version from the
command-line. Typically this is because script/version is not
executable.
Note I had recently upgrade to 0.5.1. I’m running rails 1.1.6.
If I rename the script/version file to script/version.bak, the upgrade
seems to proceed ok, but it upgraded to 0.5.1 then 0.5.2. All is OK
in the end, but maybe there’s a certain upgrade path bug?
You should be fine now. All the upgrade stuff does right now is copy
files from the new gem over your existing install. Running 0.5.1 to
0.5.2 won’t hurt anything.
Can you run script/version now?
–
John L.
http://wiseheartdesign.com
On 8/11/06, John W. Long [email protected] wrote:
…/ruby/gems/1.8/gems/radiant-0.5.2/bin/radiant:281:in `popen’: No
such file or directory - radiant-0.5.0/script/version (Errno::ENOENT)
That error is caused when you can’t execute script/version from the
command-line. Typically this is because script/version is not executable.
Ah. Likely a Windows issue then… no, can’t execute script/version
directly. It would have to be executed as “ruby script\version” or
something similar.
-Chris
Chris Brooks wrote:
On 8/11/06, John W. Long [email protected] wrote:
…/ruby/gems/1.8/gems/radiant-0.5.2/bin/radiant:281:in `popen’: No
such file or directory - radiant-0.5.0/script/version (Errno::ENOENT)
That error is caused when you can’t execute script/version from the
command-line. Typically this is because script/version is not executable.
Ah. Likely a Windows issue then… no, can’t execute script/version
directly. It would have to be executed as “ruby script\version” or
something similar.
My fault. Of course it wouldn’t work right on Windows. Please file a
ticket for this.
–
John L.
http://wiseheartdesign.com