# Radiant upgrade to 0.5.2 failing **URL:** \ **Category:** Radiant CMS\ **Created:** [August 15, 2006, 2:16pm UTC](https://www.ruby-forum.com/t/radiant-upgrade-to-0-5-2-failing/102404 "2006-08-15T14:16:49Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Chris\_Brooks](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9de053/32.png) [@Chris\_Brooks](https://www.ruby-forum.com/u/Chris_Brooks)\ **Post date:** [August 15, 2006, 2:16pm UTC](https://www.ruby-forum.com/t/radiant-upgrade-to-0-5-2-failing/102404/1 "2006-08-15T14:16:49Z")
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 ---
**Author:** ![Chris\_Brooks](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9de053/32.png) [@Chris\_Brooks](https://www.ruby-forum.com/u/Chris_Brooks)\ **Post date:** [August 15, 2006, 2:17pm UTC](https://www.ruby-forum.com/t/radiant-upgrade-to-0-5-2-failing/102404/2 "2006-08-15T14:17:11Z")
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](http://wiseheartdesign.com) ---
**Author:** ![Chris\_Brooks](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9de053/32.png) [@Chris\_Brooks](https://www.ruby-forum.com/u/Chris_Brooks)\ **Post date:** [August 15, 2006, 2:17pm UTC](https://www.ruby-forum.com/t/radiant-upgrade-to-0-5-2-failing/102404/3 "2006-08-15T14:17:12Z")
On 8/11/06, John W. Long [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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 ---
**Author:** ![Chris\_Brooks](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9de053/32.png) [@Chris\_Brooks](https://www.ruby-forum.com/u/Chris_Brooks)\ **Post date:** [August 15, 2006, 2:17pm UTC](https://www.ruby-forum.com/t/radiant-upgrade-to-0-5-2-failing/102404/4 "2006-08-15T14:17:28Z")
Chris Brooks wrote: > On 8/11/06, John W. Long [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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](http://wiseheartdesign.com)