Typo 5.1.1 to 5.2 upgrade


#1

Hello,

When I follow the upgrade instructions for “gem install typo” I seem
to get the edge 5.2.98 version which gives me install gripes like this:

lib/rails-installer.rb:689:in in_directory' from /usr/local/lib/ruby/gems/1.8/gems/typo-5.2.98/bin/typo:93 from /usr/local/bin/typo:19:inload’
from /usr/local/bin/typo:19
[dag@dag typo-5.2.98]$

Do I have a gem setting or ENV wrong that puts me on the edge track?
How do I tell gem that I want the stable 5.2? Sorry for the novice
question.

Regards,
Chris


#2

On Thu, Mar 26, 2009 at 9:47 AM, Chris D. removed_email_address@domain.invalid
wrote:

specification file. Run ‘rake gems:refresh_specs’ to fix this.
`migrate’
/usr/local/lib/ruby/gems/1.8/gems/rails-app-installer-0.2.0/lib/rails-installer.rb:646:in
Regards,
Chris

This sounds like it’s related to one of the things I recently
encountered in
trying to upgrade from 4.1 to 5.2
try

sudo gem install datanoise-actionwebservice --source
http://gems.github.com

Some of what I experienced might be helpful, so you might want to have
a look at

http://talklikeaduck.denhaven2.com/2009/03/25/typo-5-1-with-capistrano-deploy-to-passenger-on-ubuntu-8-10-a-debriefing


Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale


#3

Thanks Rick,

Your advice got me past the install.

Migration worked fine for development and test but I’m hung up on the
production instance …

On Mar 26, 2009, at 9:35 AM, Rick DeNatale wrote:

This sounds like it’s related to one of the things I recently
encountered in trying to upgrade from 4.1 to 5.2

try
sudo gem install datanoise-actionwebservice --source http://gems.github.com

My older typo seemed current to migration #70 so I’m trying each newer
migration one at a time and I immediately get this with #71:

An error has occurred, all later migrations canceled:
66:in transaction' ./db/migrate//071_fix_tags_naming.rb:6:inup_without_benchmarks’
(DELEGATION):2:in migrate' /home/rails-applications/typo-5.2/vendor/rails/activerecord/lib/ /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:612:ineach’
invoke_task' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1977:inrun’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in
standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1974:inrun’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake:31
/usr/local/bin/rake:19:in `load’
/usr/local/bin/rake:19

Anything obvious jump out here?

Regards,
Chris


#4

Hi folks,

I’ve had sort of an epic journey trying to go from 5.1.1 to 5.2 over
the last 2 days …

In order to even get typo back up I had to (this is the short story …)

  1. Follow Rick’s advice to get datanoise-actionwebservice from
    gems.github.com

  2. Hand edit the contents of the tags table in the production database
    to change any tag that had a “.” char in it just so I could get past
    migration #71 (071_fix_tags_naming.rb). The migration that was
    supposed to do this simply did not work for some reason until I
    manually made sure there were no tags with “.” chars in the database.
    50+ edits to SQL table values.

  3. Reorder the migrations because it seemed that migrations prior to
    081_create_cache_informations.rb actually depend on the presence of
    the cache_informations table and bomb out with fatal migration errors
    when the table is not present. Without the reorder I could not get
    past migration 078 on the production database

After jumping through all those hoops I seem to have a working install
but I’m getting nailed up by a fastthread issue that I’m hoping
someone can help me out with.

Using both mongrel and webrick I can reliably crash typo 5.2 with this
error:

ruby: symbol lookup error: /usr/local/lib/ruby/gems/1.8/gems/
fastthread-1.0.5/lib/fastthread.so: undefined symbol:
rb_thread_alive_p

In this case google is my friend and it seems that there is a git fix
for this problem:

http://github.com/mental/fastthread/commits/fastthread-1.0.5

-and-

http://github.com/mental/fastthread/commit/75995d6a097e5b55dc53c39858aea051ce74556e

My main issue is not typo related at this point :slight_smile: I just don’t know
enough about git and/or how it is used with gems and ruby to actually
implement the patch/fix/hotfix whatever that is referenced in the
above URL

Has anyone else run into the “undefined symbol: rb_thread_alive_p” -
any tips on rebuilding fastthread-1.0.5 with the fix that resolves the
“undefined symbol: rb_thread_alive_p” problem?

Regards,
Chris


#5

Le 26 mars 09 à 22:53, Chris D. a écrit :

Thanks Rick,

Your advice got me past the install.

Migration worked fine for development and test but I’m hung up on
the production instance …

Hello,

Sorry for not replying faster, but I’ve been quite busy lately, and I
guess we’re not on the same timezone, which doesn’t help either.

I’ve gathered all your feedbacks on migrating from 5.x to 5.2.98, in
order to have everything to go smoothly when I release 5.3 (tomorrow
or sunday according to my planning).

Regarding actionwebservice and will paginate: both gems are hosted on
github and thus are not compatible with gem dependencies system. I’ve
vendored both of them into Typo, in order to avoid any issue.

The cycling migration issue is fixed as well. If the cache table is
missing, sweeping the cache will just fail silently, and migration
will keep on going.

Tell me if you encounter any other issue during your migration, we’ll
try to solve it as well for the finale release.

Cheers
Frédéric


Frédéric de Villamil
“What’s mine is mine. What’s yours is still unsetteled” – Go player
proverb
removed_email_address@domain.invalid tel: +33 (0)6 62 19 1337
http://t37.net Typo : http://typosphere.org


#6

Disregard my fastthrread.so and git/patch incompetence.

I managed to patch the fastthread.c file so that it would not complain
about the undefined symbol under ruby 1.8.6 and was able to build
the .so cleanly, pass “rake test” and install it in all the proper
places.

-chris


#7

2009/3/27 de Villamil Frédéric removed_email_address@domain.invalid

Thanks.

I seem to be up and operational now. Did you see my debrief article on
my
blog?
http://talklikeaduck.denhaven2.com/2009/03/25/typo-5-1-with-capistrano-deploy-to-passenger-on-ubuntu-8-10-a-debriefing

I’d sent you a separate email asking about how to override views in
themes.
You can ignore it, Je me débrouille. C’était assez facile.


Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale


#8

On Fri, Mar 27, 2009 at 3:11 AM, Chris D. removed_email_address@domain.invalid
wrote:

Disregard my fastthrread.so and git/patch incompetence.

I managed to patch the fastthread.c file so that it would not complain
about the undefined symbol under ruby 1.8.6 and was able to build the .so
cleanly, pass “rake test” and install it in all the proper places.

Chris,

If the system you are deploying to supports it, and most do these days
assuming it’s a posix system rather than windows, I’d really suggest
looking
into replacing mongrel/mongrel cluster with Phusion Passenger.


Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale