<havenwood>
ws2k3: Yes, all versions before 0.7.0 were yanked.
<ws2k3>
havenwood damn
<ws2k3>
havenwood already working the entire day to get it work again
<ws2k3>
but ruby is kinda of nightmare
<ws2k3>
havenwood i still got the english 0.6.3.gem on another box. so i added it into ansible and im installing the gem that way. but when i run the commands as root it works just fine. but when i do it with ansible ruby cannot find the english 0.6.3 :S
<havenwood>
ws2k3: Ruby ships with "English" in the stdlib. Why is your code using this gem? It seems totally unnecessary.
<havenwood>
ws2k3: Your problem of old weird deps hardly seems specific to Ruby. ¯\_(ツ)_/¯
<ws2k3>
havenwood i use a package that is build on this. and its pretty old. so its not my choice to use it or not
<havenwood>
ws2k3: Just drop this gem dep if you can.
<ws2k3>
cant unfortunaly
<ws2k3>
havenwood still its kinda related to ruby
<havenwood>
ws2k3: Bump it to 0.7.0?
<ws2k3>
gem list shows the gem installed just fine
<havenwood>
ws2k3: It's cached.
<ws2k3>
what do you mean
<havenwood>
ws2k3: That's really not specific to Ruby, since most package managers cache downloaded packages locally.
<ws2k3>
i know but i just run gem install mygem.gem
<ws2k3>
gem list shows its installed just fine
<ws2k3>
but still when i run my application it says not found
<havenwood>
ws2k3: It's bad form to yank packages in any package manager unless there's a real good reason - since it causes trouble like this.
<ws2k3>
but i i manualy start my application as root. then it find the gem just fine
<ws2k3>
i dont have another choice since they suddenly pulled the english 0.6.3 offline
<havenwood>
ws2k3: Folk can probably help you get it sorted in the #ruby channel.