I used RailsInstaller (for Windows) to set up my environment for my Rails 3 app. I recently installed Pik so that I can update my ruby version as well.
According to the Pik docs https://github.com/vertiginous/pik/wiki/Usage, running 'pik install ruby 1.9.3' should install lastest version of ruby (or atleast the latest patch level for the version I am specifying).
However, this only installs ruby 1.9.3p429, but I understand that 1.9.3p545 is available.
Does anyone know how I can install 1.9.3p545?
Thanks!
Looks like you went with Pik from your previous question. I read on another thread that Pik only supports some of the 1.9.3 patch levels, but unfortunately nothing verifiable. The project has also been abandoned, no longer maintained, which might explain why that latest patch isn't supported...
Might just be my perspective, but seems like Windows is very poorly supported in the Rails/Ruby world? Our project requires Windows and Linux support which is causing us lots of grief. If you find a solid & reliable upgrade solution for Windows I would be very interested!
Related
Today I tried to upgrade the "icu" pacman package, because I need it for NodeJS to work.
After I installed the newest version my system completely broke, I can't even start it up anymore.
Does anybody know how to fix the problem with Node or how to correctly upgrade the "icu" package?
You shouldn't upgrade individual packages. Instead, you should upgrade the entire system. The reason for this is that the dependencies that exist between packages will break sooner or later if you perform partial upgrades.
If you can't boot your system any more, try booting on the installation media, mount the installed disk, arch-chroot into it and run pacman -Syu.
The proper way to upgrade Arch linux is described here:
https://wiki.archlinux.org/title/System_maintenance#Upgrading_the_system
I'm trying to understand why the easy_install of pyicu works and pip install doesn't (see below). also trying to understand "What is the difference between a PyPi project with a universal wheel and one without?" Will installs be "easier?". If so, will this merge request solve the problem of polyglot not installing on an Anaconda machine?
Need help/advice/solutions on how to best resolve python project install issue that is tied to underlying dependencies. I have two local fixes in GitHub Gists but would like to know the best way to have this fix "out there" so people like me can find it. What is the normal Python Community approach? The problem centers around three projects:
polyglot - a python multilingual NLP toolkit
pyicu - Python extension wrapping IBM's International Components for Unicode C++ library (ICU).
pycld2 - CLD (Compact Language Detection) library as maintained by Dick Sites
The goal:
Install polyglot on a MacOSX computer running Python Anaconda Distribution
Make the fix I found available to everyone; lots of issues published about the problem.
Here's the error trace:
The Problem (Lots of them):
Core polyglot dependency, pyicu, does not properly install when you use pip install. Discovered you must use easy_install for it build properly and work on MacOSX. If you don't use the easy_install, you get:
polyglot requires icu 54.1.1 to run in Anaconda, but...
Homebrew, the MacOSX tool to install icu, only installs version 58.1. That version is too new. Old stackoverflows advise brew install icu4c to fix problem, but Homebrew evolution makes that advice obsolete now.
pyicu does not have a universal wheel; but I created a merge request to add one to pyicu. Only way to fix this is with this channel's icu, https://anaconda.org/ccordoba12/icu. conda install icu will not work, but that's the normal conda way of doing things.
*pycld2 - CLD (Compact Language Detection) becomes a problem because after I build the wheel file locally, have to download the project and run setup.py install locally. There has to be a better way to do this right?
What I've Done to Solve the problem (should I do more, what should I do next?)
Created two Gists that can successfully install polyglot on a Mac running Anaconda for Python 2.7 or Python 3.5
Python 2.7 fix
Python 3.5 fix
created the merge request for pyicu
Both Gist fixes work. But, is this error in install tied to the wheel? If I installed pyicu with easy_install, the install works. But, with pip, it doesn't?
What are the steps to take in the Python community to fix it so people can find the solution or just pip install with no problems?
I did a test, and if the wheel file is built, the pip works with no issues.
I am trying to run my pharo2.0 application on CentoOS which was previously been installed in a mac. The original version is pharo2.0 so I need to run the same image CentoOS too, but I get an error which says this below :
/lib/libc.so.6: version `GLIBC_2.15' not found (required by xxxxx)
Should I be trying to upgrade the CentoOS and see if pharo2.0 works or port my whole application to a later version of pharo?
There is now a VM build especially for systems with an older libc version. In fact there is a build for Centos specifically (which has a slight variation in linkages from Debian), the latest version of which is permalinked here. See http://pharo.org/download#custom for more info.
Just installed Yosemite and when I run brew doctor I get:
Warning: Your Xcode (6.0.1) is outdated
Please update to Xcode 6.1.
Xcode can be updated from the App Store.
But in the AppStore it looks like XCode 6.0.1 is the latest version. What's the best way to correct this?
Tis that slight lag between 10.10 being Avail and xcode getting updated. If you read the top of brew doctor output it says
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!
So if everything is working, then you should do what it suggests and ignore it. The command line tools / compilers where updated for 10.10 (software update should have picked them up for you). Are you running into any issues with compiling? or just that warning.
pulling up from the comments. Your ruby and postgresql issues are from the upgrade, but it isn't really brews fault, or that compiler error warning.
with rvm just reinstall your ruby. My main dev is done with ruby-2.1.3 so
rvm reinstall ruby-2.1.3
rebuilt ruby and all my gems. The problem is that the ssl libs (maybe others) that ruby was linked to were removed / replaced in the upgrade to 10.10. The reinstall will rebuild and relink to the newer correct libs.
postgresql is slightly different. Apparently during the upgrade a couple of empty directories in /usr/local/var/postgres get removed. No idea why.
see this SO answer for how to fix that.
`pg_tblspc` missing after installation of latest version of OS X (Yosemite or El Capitan)
also if you are use pow (http://pow.cx) you will need to upgrade it to the latest version as 10.10 removed ipfw completely and only leaves pf as the firewall. so you will need to the new version which uses pf anchors.
The above steps where all I needed to do it in order to get my dev back to working.
Looks like developer.apple.com does show an XCode 6.1 as "Available Shortly" as of Fri, Oct 17, at 10pm central time. Not yet available from the AppStore. I guess I'm just too eager for an update.
I have an old laptop which runs OSX 10.4 Tiger where I'd like to run git, rvm, Ruby 1.9.2 and Rails 3.1.
At the moment I have git installed (using MacPorts), but rvm seems to require a newer version of bash. This I realized because the install script complains and I googled the error. Anyhow, I installed a newer bash with MacPorts and that helped me with getting rvm installed. However, it of course didn't replace the default bash version on the system and all rvm scripts point to the system one. This simply results in failures when I try to run any rvm commands.
Before I totally mess up the system I'd like to know does anyone have git, rvm, Ruby 1.9.2 and Rails 3.1 installed on OSX 10.4 Tiger? How did you install each part and what versions do you use?
Thanks for all help!
I never got this to work, but I decided to upgrade to OSX Snow Leopard. After this it was very easy to get things set up. This is what I recommend.