Hi everybody, I run into these kind of problems (see thread history) a lot with bundled gems in Typo. I solve this by getting rid of any bundled gems in vendor/gems and install them manually. That fixes most problems I seem to have after doing a git pull. Is this the intended way?
regards, Tobias W. On Sun, Jun 28, 2009 at 3:55 PM, Tobias Weisserth < tobias.weisse...@gmail.com> wrote: > Hi Matijs, > > I moved the gem out of the way. The only thing missing now was the > bluecloth gem which for some reason is not on the list of gems in the Wiki > documentation. Installing this in its newest version did the trick. > > Everything seems to work now, I cannot detect any weird behaviour. > > What do I need to do to run unit tests in Typo edge? > > regards, > > Tobias > > On Sun, Jun 28, 2009 at 3:41 PM, Matijs van Zuijlen <mat...@matijs.net>wrote: > >> Tobias Weisserth wrote: >> > Hi everybody, >> > >> > I am running Typo locally for testing and Ruby/Rails learning purposes. >> > I am using Ruby Enterprise with a local mongrel for this. >> > >> > Recently, I bumped the version from Ruby Enterprise from >> > ruby-enterprise-1.8.6-20090201 to ruby-enterprise-1.8.6-20090610 and >> > used the documentation from the Wiki to pull the gems needed for Typo >> edge. >> > >> > However, since some gems moved up in versions, I am running into this, >> > when invoking script/server: >> > >> > [...] >> > >> /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/site_ruby/1.8/rubygems.rb:258:in >> > `activate': can't activate json (= 1.1.6, runtime) for [], already >> > activated json-1.1.3 for [] (Gem::Exception) >> >> Don't you just love how rubygems fixes all versioning problems for you? >> </sarcasm> >> >> I'm not sure what depends on json-1.1.6. >> >> > The problem is, that in that new Ruby installation, the json gem only >> > exists in version 1.1.6 whereas in the old, working Ruby installation >> > the same gem existed in version 1.1.3 and 1.1.6. >> >> Can you post the output of gem list? >> >> > I noticed that this gem also exists in vendor/gems. Why is that? >> >> Not sure ... probably an attempt to avoid this or some other dependency >> problem. >> >> > Should that be like this? >> >> I would like to get rid of the entire contents of vendor/gems, but then >> again >> I'm not sure if there would be any problems using json 1.1.6. >> >> Can you try moving the json version in vendor/gems out of the way and see >> what >> happens? >> >> -- >> Matijs >> >> >> _______________________________________________ >> Typo-list mailing list >> Typo-list@rubyforge.org >> http://rubyforge.org/mailman/listinfo/typo-list >> > >
_______________________________________________ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
