GitLab/charlock issues with latest libicui18n #48

Closed
ghost opened this Issue Oct 19, 2013 · 11 comments

Comments

Projects
None yet
10 participants
@ghost

ghost commented Oct 19, 2013

When instaling the gem:
unable to convert "\xD0" from ASCII-8BIT to UTF-8 for lib/charlock_holmes/charlock_holmes.so, skipping

Libs installed:

ls /usr/lib/libicui18n.so*

/usr/lib/libicui18n.so /usr/lib/libicui18n.so.52 /usr/lib/libicui18n.so.52.1

gitlab env info output:

$ bundle exec rake gitlab:env:info RAILS_ENV=production
rake aborted!
libicui18n.so.51: cannot open shared object file: No such file or directory - /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/charlock_holmes-0.6.9.4/lib/charlock_holmes/charlock_holmes.so

charlock_holmes wants libicui18n.so.51 !
If i link .so.51 to the actual .so as following:

ln -s /usr/lib/libicui18n.so /usr/lib/libicui18n.so.51

the output is:

$ bundle exec rake gitlab:env:info RAILS_ENV=production
rake aborted!
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/charlock_holmes-0.6.9.4/lib/charlock_holmes/charlock_holmes.so: undefined symbol: _ZTIN6icu_518ByteSinkE - /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/charlock_holmes-0.6.9.4/lib/charlock_holmes/charlock_holmes.so

Using kernel 3.10.9, qt4 4.8.5-3, icu 52.1-1

NOTE:
if i come back to old ICU lib version:

cd /var/cache/pacman/pkg/

pacman -U icu-51.2-1-x86_64.pkg.tar.xz

It works great.

@joltmode

This comment has been minimized.

Show comment
Hide comment
@joltmode

joltmode Oct 25, 2013

Experiencing the same issue on Arch Linux. Did a full system upgraded, got icu-52.1, sidekiq fails with charlock loading error.

Downgrading to icu-51 solves the issue.

Running Gitlab 6.1.

Experiencing the same issue on Arch Linux. Did a full system upgraded, got icu-52.1, sidekiq fails with charlock loading error.

Downgrading to icu-51 solves the issue.

Running Gitlab 6.1.

@cbrake

This comment has been minimized.

Show comment
Hide comment
@cbrake

cbrake Nov 25, 2013

I was able to get charlock working with icu-52 on arch today. I did have to un-install charlock and re-install it.

bundle exec gem uninstall charlock_holmes
bundle install --deployment --without development test mysql aws

cbrake commented Nov 25, 2013

I was able to get charlock working with icu-52 on arch today. I did have to un-install charlock and re-install it.

bundle exec gem uninstall charlock_holmes
bundle install --deployment --without development test mysql aws

@boeserwolf91

This comment has been minimized.

Show comment
Hide comment
@boeserwolf91

boeserwolf91 Nov 27, 2013

👍 @cbrake thanks. the reinstall worked for me too

👍 @cbrake thanks. the reinstall worked for me too

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 29, 2013

Same. I confirm it works fine now with latest icu.

ghost commented Nov 29, 2013

Same. I confirm it works fine now with latest icu.

@ghost ghost closed this Nov 29, 2013

@mrohnstock

This comment has been minimized.

Show comment
Hide comment
@mrohnstock

mrohnstock Apr 26, 2014

Thanks, removing charlock_holmes and re-executing bundle install helped here, too with icu-53.

Thanks, removing charlock_holmes and re-executing bundle install helped here, too with icu-53.

@mcantsin

This comment has been minimized.

Show comment
Hide comment

@cbrake you win!

@arthur-c

This comment has been minimized.

Show comment
Hide comment

arthur-c commented May 5, 2014

Thanks @cbrake !

@HLFH

This comment has been minimized.

Show comment
Hide comment
@HLFH

HLFH Jun 21, 2014

@cbrake Thanks, issue solved

HLFH commented Jun 21, 2014

@cbrake Thanks, issue solved

@VaiN474

This comment has been minimized.

Show comment
Hide comment
@VaiN474

VaiN474 Jul 3, 2014

upgraded ubuntu server to 14.04 and ran into this issue as well

@cbrake Thanks for the fix

VaiN474 commented Jul 3, 2014

upgraded ubuntu server to 14.04 and ran into this issue as well

@cbrake Thanks for the fix

@nibon

This comment has been minimized.

Show comment
Hide comment
@nibon

nibon Jul 6, 2014

Upgraded to ubuntu server 14.04 here also, and @cbrake comment solved it. Thanks!

cd /home/git/gitlab
sudo -u git -H bundle exec gem uninstall charlock_holmes
sudo -u git -H bundle install --deployment --without development test mysql

nibon commented Jul 6, 2014

Upgraded to ubuntu server 14.04 here also, and @cbrake comment solved it. Thanks!

cd /home/git/gitlab
sudo -u git -H bundle exec gem uninstall charlock_holmes
sudo -u git -H bundle install --deployment --without development test mysql
@brentluna

This comment has been minimized.

Show comment
Hide comment
@brentluna

brentluna Aug 18, 2017

@cbrake I'm getting this error when pushing to my heroku remote, locally everything works fine. Any thoughts on how to resolve for heroku hosted where it handles the bundle install?

@cbrake I'm getting this error when pushing to my heroku remote, locally everything works fine. Any thoughts on how to resolve for heroku hosted where it handles the bundle install?

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment