Problem upgrading to Rails 2.3.2

[Larry Hannay]

Hi,



I've been using Netbeans for quite some time and love it - thanks to all of the people who work on it.



I'm setting up a new (Linux) environment. I installed a version of Ruby that had version 2.3.2 of Rails. My current implementation was 2.2.2 and it was in my project's /vendor/rails directory. I use Subversion for source control and have been using the new Netbeans 6.7 (Beta) IDE for a few weeks with no problem.



I figured it was time to upgrade my /vendor/rails from 2.2.2 to 2.3.2, so in Netbeans I did a Run/Debug Rake Task > rails:freeze:gems. It seemed to work fine, as the output from running the rake task shows:




Code:


(in /home/larry/NetBeansProjects/StupidTuesday)

rm -rf vendor/rails

Freezing to the gems for Rails 2.3.2

mkdir -p vendor/rails

cd vendor/rails

mv activesupport-2.3.2 activesupport

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activesupport-2.3.2'

mv activerecord-2.3.2 activerecord

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activerecord-2.3.2'

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/actionpack-2.3.2'

mv actionpack-2.3.2 actionpack

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/actionmailer-2.3.2'

mv actionmailer-2.3.2 actionmailer

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activeresource-2.3.2'

mv activeresource-2.3.2 activeresource

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/rails-2.3.2'

cd -







I figured it was best to commit this before running rails:update, but when I tried doing that I get the following message:


Code:


'/home/larry/NetBeansProjects/StupidTuesday/vendor/rails' is not a working copy

Can't open file '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/.svn/entries': No such file or directory







But I can see the new /vendor/rails directory and all of its subdirectories, and they are marked as [New] in the Netbeans projects window.



Any suggestions on what I can do? I've spent about an hour on something that I thought was going to take 2 minutes, and it's kind of frustrating.



Thanks,

Larry






---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Erno Mononen]

Hi Larry,

I don't know much about subversion, but seems like a bug either in the
svn plugin or in svn itself. Can you please file an issue for this at
http://www.netbeans.org/issues/enter_bug.cgi against the subversion
component?

BTW, can you commit from the command line? Does restarting or running
the IDE with a clean userdir (pls see
http://wiki.netbeans.org/FaqAlternateUserdir) make any difference?

Thanks,
Erno


larry wrote:

> Hi,
>
>
>
> I've been using Netbeans for quite some time and love it - thanks to all of the people who work on it.
>
>
>
> I'm setting up a new (Linux) environment. I installed a version of Ruby that had version 2.3.2 of Rails. My current implementation was 2.2.2 and it was in my project's /vendor/rails directory. I use Subversion for source control and have been using the new Netbeans 6.7 (Beta) IDE for a few weeks with no problem.
>
>
>
> I figured it was time to upgrade my /vendor/rails from 2.2.2 to 2.3.2, so in Netbeans I did a Run/Debug Rake Task > rails:freeze:gems. It seemed to work fine, as the output from running the rake task shows:
>
>
>
>
> Code:
>
>
> (in /home/larry/NetBeansProjects/StupidTuesday)
>
> rm -rf vendor/rails
>
> Freezing to the gems for Rails 2.3.2
>
> mkdir -p vendor/rails
>
> cd vendor/rails
>
> mv activesupport-2.3.2 activesupport
>
> Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activesupport-2.3.2'
>
> mv activerecord-2.3.2 activerecord
>
> Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activerecord-2.3.2'
>
> Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/actionpack-2.3.2'
>
> mv actionpack-2.3.2 actionpack
>
> Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/actionmailer-2.3.2'
>
> mv actionmailer-2.3.2 actionmailer
>
> Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activeresource-2.3.2'
>
> mv activeresource-2.3.2 activeresource
>
> Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/rails-2.3.2'
>
> cd -
>
>
>
>
>
>
>
> I figured it was best to commit this before running rails:update, but when I tried doing that I get the following message:
>
>
> Code:
>
>
> '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails' is not a working copy
>
> Can't open file '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/.svn/entries': No such file or directory
>
>
>
>
>
>
>
> But I can see the new /vendor/rails directory and all of its subdirectories, and they are marked as [New] in the Netbeans projects window.
>
>
>
> Any suggestions on what I can do? I've spent about an hour on something that I thought was going to take 2 minutes, and it's kind of frustrating.
>
>
>
> Thanks,
>
> Larry
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Larry Hannay]

Hi Erno,



Thanks for your interest in this matter. It turns out that is a relative pain in the *&^% to upgrade Rails if you've vendored it in your project directory. The culprit? Subversion.



Most books/forums/blogs simply discuss how to originally freeze Rails. But when you go hunting for problems with upgrading Rails that's under Subversion source control - well, you quickly find out you are not alone.



After reading a bunch of posts, and for a number of my own reasons, I decided to no longer vendor Rails, i.e. I simply use the gems that are located in my Ruby installation.



Thanks again, Erno.



-- Larry






---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Erno Mononen]

Hi Larry,

Thanks for following up on this, and good to know the IDE is off the hook :)

Cheers,
Erno


larry wrote:

> Hi Erno,
>
>
>
> Thanks for your interest in this matter. It turns out that is a relative pain in the *&^% to upgrade Rails if you've vendored it in your project directory. The culprit? Subversion.
>
>
>
> Most books/forums/blogs simply discuss how to originally freeze Rails. But when you go hunting for problems with upgrading Rails that's under Subversion source control - well, you quickly find out you are not alone.
>
>
>
> After reading a bunch of posts, and for a number of my own reasons, I decided to no longer vendor Rails, i.e. I simply use the gems that are located in my Ruby installation.
>
>
>
> Thanks again, Erno.
>
>
>
> -- Larry
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...