Running on OS X 10.6.8. homebrew installed nginx OK.
/usr/local/Cellar/nginx/1.6.0_1
But then:
brew install passenger nginx --with-passenger
as suggested by the passenger documentation (unless there is less recent documentation I should be referring to), I am encountering the following error:
passenger: OS X Mountain Lion or newer is required.
How can this be overcome?
You can't. We (Phusion) do not support OS X versions older than Mountain Lion. You have several alternatives:
Upgrade to the latest OS X version.
Use an older version of Phusion Passenger that still supported Mountain Lion. However be aware that it may contain unresolved bugs or have less features. It also cannot be installed from Homebrew: you have to install it from gem or tarball.
Take the source of the latest version and modify it so that it works with Mountain Lion.
Related
does anyone know how I could install MariaDB 5.5 server with Homebrew on Mac OS? I've tried running brew install mariadb#5.5 but it doesn’t work.
You can also Try Building it from source!
you can use Homebrew to build MariaDB from source.Its helpful if you want to use a different version of the server or enable some different capabilities that are not included in the bottle package or if you are having issues with the bottle package.
To build MariaDB Server with these engines, you must first install boost and judy.
And please can you be specific about the errors you encountered.
You might want to check this site:
Now a bit of background of my current setup:
I have Python3.3 running on Centos 6. I'm currently working on a web application using Flask that runs on Apache 2.2.15 with mode WSGI 4.5.3 and virtualenv 15.0.2.
pip --version pip 8.1.2 from /usr/local/bin/lib/python3.3/site-packages (python 3.3)
I have installed pysvn with pip and when I run pip show pysvn says
Location: /usr/local/bin/lib/python3.3/site-packages
755 permissions recursively set to /usr/local/bin/lib/python3.3/site-packages. And I passed --system-site-packages argument to virtualenv to use the global site packages.
Even when I try to import the package from python interpreter it does not work. So it is not specific to my virtualenv setup but rather a global problem.
I must mention that other packages installed with pip work perfectly fine (i.e. flask).
I've exhausted all other avenues before coming forward to you guys. Any suggestion would be highly appreciated as I ran out of ideas.
L.E.
I did manage to install it in the end. I'm not completly sure yet why and how but I presume is was compatibility issue.
First of all I have uninstalled svn 1.6+ and installed version 1.8.16 instead which seems to be tested against the latest two versions.
Second, I have uninstalled the troublesome pysvn instance and installed pysvn-1.8.0 workbench "sudo /var/www/FlaskApp/FlaskApp/flask/bin/pip install pysvn-1.8.0.tar.gz". In this case I have installed it my local environment. The 1.9.0 version of pysvn did not work.
L.L.E.
False positive, still doesn't work. I'm going to interact with svn via command line from my script.
L.L.L.E.
After installing svn 1.8.16 and svn-devel along with the rest of dependencies described in the readme file I have managed to successfully install it from the source fallowing the instructions.
Thanks for your help Barry.
pysvn is not available from PyPI because PyPI has no way to allow me to upload pysvn for each supported SVN version. Let alone deal with the issues of installing on a Linux distro given the choices for pysvn dependencies.
(APR, SVN, OpenSSL etc).
Fedora packages pysvn for the Fedora release.
I'm assuming that means it is on RHEL and therefore packaged by CentOS.
(But I do not have RHEL or CentOS to check this on)
If you find that a package is not available for your CentOs is not hard
to build pysvn on a linux distro. Get the source kit and follow the readme.html should get you going.
Barry (pysvn maintainer)
I use Debian sid (amd64), rolling updates as often as weekly. I downloaded recently the desktop version 0.99.902 of RStudio from their offical site and issued (as root, of course):
dpkg -i rstudio-0.99.902-amd64.deb
to no avail:
dpkg: dependency problems prevent configuration of rstudio:
rstudio depends on libgstreamer0.10-0; however:
Package libgstreamer0.10-0 is not installed.
rstudio depends on libgstreamer-plugins-base0.10-0; however:
Package libgstreamer-plugins-base0.10-0 is not installed.
Newer versions (1.0-0) of these 2 packages are installed on the system, but those older ones (0.10-0) are not available anymore on the official Debian repos.
What should be done to have RStudio installed and fully operational under
Debian sid? I have, of course, installed R debs, from official Debian
repositories, without any issues...
Thanks for any help!
RStudio 1.0.153, released on July 20th 2017, depends on GStreamer 1.0 instead of GStreamer 0.10. It can be installed on modern Debian/Ubuntu without any additional setup, rendering this question and my answer obsolete.
To be more specific, there are two different DEB packages. One is aimed at Ubuntu 16.04 (or later) and Debian 9 (or later), comes only in 64-bit flavor and depends on newer GStreamer 1.0. Another package supports Ubuntu from 12.04 up to 15.10 and Debian 8 and it comes in both 32-bit and 64-bit flavors. This one still depends on older GStreamer 0.10.
Original answer remains below.
As of mid-2016, RStudio has hard dependency on GStreamer 0.10 and there is no way around it. You have to install libgstreamer0.10-0 and libgstreamer-plugins-base0.10-0 to use RStudio.
These packages can be easily pulled in from Debian Jessie (stable). Just add Jessie repository to your sources.list and use apt-pinning to give it lower priority:
# /etc/apt/sources.list:
deb http://httpredir.debian.org/debian jessie main
# /etc/apt/preferences.d/01_release:
Package: *
Pin: release o=Debian,a=unstable
Pin-Priority: 600
Package: *
Pin: release o=Debian,n=jessie
Pin-Priority: 10
Then issue apt-get update and follow up with apt-get install libgstreamer0.10-0 libgstreamer-plugins-base0.10-0.
If you have happened to put RStudio .deb file into local repository, then use apt-get install rstudio and GStreamer0.10 will be pulled in by dependency resolver. This has additional advantage of marking these libraries as automatically installed - they will be subject to automatic removal once RStudio drop them as dependency.
But will that break my system?
No.
Upstream developers designed GStreamer0.10 and GStreamer1.0 as co-installable and able to run at the same time (source). In fact, both were available in Debian repository since September 2012 up to April 2016.
In this pinning setup, packages from Jessie repository will be pulled in only when Jessie is the only provider of requested package. There is no risk of overwriting any package from unstable with older version from stable.
Why does RStudio depend on obsolete library?
Because GStreamer0.10 is the newest version available in both Debian Jessie and Ubuntu 12.04, two distributions they want to support.
RStudio will eventually have to upgrade their dependency to GStreamer1.0, as it will gradually become the only version available. I guess this change may be introduced in spring 2017. First, support for Ubuntu 12.04 will end in April. Rstudio is likely to bump base system requirement to 14.04 - one that has both GStreamer0.10 and 1.0. Second, Debian Stretch - that will have only GStreamer1.0 available - is expected to be released around that time.
I found Miroslaw's answer to be excellent. But, due to the passage of time you will need one more package: libssl1.0.0, so your setup apt-get will look like
apt-get install libgstreamer0.10-0 libgstreamer-plugins-base0.10-0 libssl1.0.0
Download libgstreamer0.10-0 for your machine from any of the mirrors.
Open terminal in the directory where the file is downloaded.
Install it using the command, sudo dpkg -i file.deb. Example sudo dpkg -i libgstreamer0.10-0_0.10.36-1ubuntu1_amd64.deb.
Now open the directory where rstudio.deb is located and install it in the same way.
Download the libraries
http://ftp.br.debian.org/debian/pool/main/g/gstreamer0.10/libgstreamer0.10-0_0.10.36-1.5_amd64.deb
http://ftp.br.debian.org/debian/pool/main/g/gst-plugins-base0.10/libgstreamer-plugins-base0.10-0_0.10.36-2_amd64.deb
Install them with gdebi or dpkg -i and that is it
I am trying to install iPDC on a Centos unix laptop.
I am getting a make error when I attempt to install the programme - I have attached a screenshot of my problem.
The command run is sudo make install and I am attempting to install as the root user.
Your installed GTK version is probably too old to support this software. GtkBuilder (a component within GTK) showed up at version 2.12. To find out what version you have, run pkg-config --modversion gtk+-2.0 at the command line. But that version has been around for quite some time. What version Centos are you running? I assume 5, which is quite old.
Upgrading GTK can be tricky, as most of your desktop software relies on it. If you're in for an adventure, the "easiest" would be to upgrade your Centos OS (to 6.x). You might be able to compile a more recent GTK from source and keep it separate from your system GTK, but that will take some patience.
It seems that GTK is not installed.
Try something like: yum install gtk2 or yum install gtk2-devel
After Installing Rails 3, I get the following error regarding Sqlite3 when I try to do a migrate:
dlsym(0x1037e5f10,
Init_sqlite3_native): symbol not found
- /Library/Ruby/Gems/1.8/gems/sqlite3-ruby-1.3.0/lib/sqlite3/sqlite3_native.bundle
I am using Snow Leopard, if that makes a difference.
I faced the same issue. The problem is that your sqlite-ruby interface is not installed properly in your snow leopard. To install that , use the following :-
sudo gem install sqlite3-ruby
But before installing that check if a proper gcc is installed in your Mac.Use the below lines to check that :-
ok First of all check if the follwoing is installed:-
$gcc -v
If not then you have to install Mac developers xcode package in your snow leopard first.
You can download using a free registration from this site:- http://developer.apple.com/devcenter/mac
For more reference take a look into my post : How to install ruby interface for sqlite3 in Mac snow leopard?
If you face the problem the problem even after trying these please let me know the error your facing. Because I faced all the error before making my snow leopard work ;). So I 'm familiar to most of the errors and blunders we usually make ;) !!
Hmm, looks like maybe something isn't compiled correctly. Maybe a gem was compiled on an older system or pre-upgrading to snow leopard? It may be that the sqlite binary is 64 bit but the native ruby extension isn't.
I'd try this:
Install RVM (Or create a new gemset if you're already using it.)
Using a fresh rvm gemset, re-install rails 3
Do bundle install to get all your gems loaded
If the problem goes away then it's likely that your libraries aren't all compiled the same way. This can happen when upgrading to snow leopard from a previous version of Mac OS X. The upgrade would have updated the sqlite binary but not any gems you had compiled yourself, like the sqlite bindings for ruby.
I'm not sure how it's done with Snow Leopard but you need to install The sqlite dev package, libsqlite3-dev
Then install the gem, sqlite3-ruby
Just got to the GEMFILE inside you project and comment out the gems that you do not require.