I am using OpsWorks. Multiple versions of build-essential cookbook are required because:
mysql cookbook requires 'build-essential', '~> 1.4'
nginx cookbook requires 'build-essential', '~> 2.0' (the version I have in my repo curently)
So when launching instance in OpsWorks, I get this error message:
================================================================================
Error Resolving Cookbooks for Run List:
================================================================================
Missing Cookbooks:
------------------
Could not satisfy version constraints for: build-essential
How could this conflict can be solved?
Thank you.
Update 1
I ran into this thread. The last answer suggested to use role and environment, which cannot be applied in my case because I am using OpsWorks (OpsWorks does not have Chef server to manage multiple cookbook versions, and it also does not have such "role", "environment" concepts).
If you are able to use an older version of the nginx cookbook (v2.4.2, about a month old), that one depends on build-essential ~> 1.4.
Also it sounds like you're using Chef-community cookbooks, It seems that OpsWorks itself has cookbooks for mysql and nginx. (unfortunately named the same as the community ones). Have you evaluated if those are solutions for your situation?
Related
Hello I try to install ruby gem json but it gives following error
`Building native extensions. This could take a while...
ERROR: Error installing json:
ERROR: Failed to build gem native extension.
mkmf.rb can't find header files for ruby at /usr/share/include/ruby.h
Gem files will remain installed in /home/jenkins/.gem/ruby/gems/json-2.0.2 for inspection.
Results logged to /home/jenkins/.gem/ruby/gems/json-2.0.2/ext/json/ext/generator/gem_make.out`
I looked up similar post and was directed to install ruby-devel. But thats also given me a hard time.
yum install ruby-devel
Loaded plugins: addreleaserel, priorities, product-id, search-disabled-repos, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
--> Running transaction check
---> Package ruby-devel.x86_64 0:2.0.0.598-25.el7_1 will be installed
--> Processing Dependency: ruby(x86-64) = 2.0.0.598-25.el7_1 for package: ruby-devel-2.0.0.598-25.el7_1.x86_64
--> Finished Dependency Resolution
Error: Package: ruby-devel-2.0.0.598-25.el7_1.x86_64 (RHN-rhel-x86_64-server-optional-7-1-locked)
Requires: ruby(x86-64) = 2.0.0.598-25.el7_1
Installed: ruby-2.0.0.648-29.el7.x86_64 (#RHN-rhel-x86_64-server-7-latest)
ruby(x86-64) = 2.0.0.648-29.el7
Available: ruby-2.0.0.353-20.el7.x86_64 (RHN-rhel-x86_64-server-7)
ruby(x86-64) = 2.0.0.353-20.el7
Available: ruby-2.0.0.353-22.el7_0.x86_64 (RHN-rhel-x86_64-server-7)
ruby(x86-64) = 2.0.0.353-22.el7_0
Available: ruby-2.0.0.598-24.el7.x86_64 (RHN-rhel-x86_64-server-7)
ruby(x86-64) = 2.0.0.598-24.el7
Available: ruby-2.0.0.598-25.el7_1.x86_64 (RHN-rhel-x86_64-server-7-1-locked)
ruby(x86-64) = 2.0.0.598-25.el7_1
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Can anyone suggest me steps to install ruby-devel using yum?please
Something seems off about your configured repositories.
From your error message, YUM is attempting to install ruby-devel.x86_64 0:2.0.0.598-25.el7_1 from the "RHN-rhel-x86_64-server-optional-7-1-locked" channel, but you currently have ruby-2.0.0.648-29.el7.x86_64 installed from the "#RHN-rhel-x86_64-server-7-latest" channel which will not satisfy the dependency as the release versions do not match.
For YUM to complete the transaction you posted, it would have to install an older version of the RedHat ruby package and I don't think it wants to do that without being explicitly told.
There are a couple options I can think of, depending on how you want to resolve this. My first suggestion is what I would do if I were managing this server, which is to straighten out the repository configuration and discover why yum install ruby-devel is attempting to install an older package (it might have something to do with that locked channel).
The other option is to install that ruby-devel package by any means necessary which may not be good for your RedHat subscription or could break things. You would first replace the installed version of ruby with the older one that matches ruby-devel, then attempt to install ruby-devel:
yum downgrade ruby-2.0.0.598-25
yum install ruby-devel-2.0.0.598-25
I do not have a RedHat machine with a subscription so I would not be able to test if this second suggestion would even work, use at your own risk. I would also recommend again you attempt the first suggestion of fixing your repositories or figure out why one of the channels is locked as that method would be safer and you could get support from RedHat if needed.
Hope that helps
i try to install mysql server 5.7 in my beaglebone black with OS Debian Jessie, i following this instruction http://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/#apt-repo-setup . but when i using apt-get update, it always give me an error.
W: Failed to fetch http://repo.mysql.com/apt/debian/dists/jessie/InRelease Unable to find expected entry 'mysql-apt-config/binary-armhf/Packages' in Release file (Wrong sources.list entry or malformed file)
This error is make me insane, i try to using apt-get clean, deleting mysql.list but still give me that error.
Really appreciate if you can help me, thanks.
I guess this means that this repository doesn't provide ARMv7 hardfloat builds of packages. Probably only meant for i386 and AMD64 machines.
You could install mySQL 5.6 from jessie-backports if that version is enough for your needs. If you need 5.7 you'd either need to rebuild packages (very slow) or dist-upgrade to Debian SID (beware, can be unstable).
I just installed Centos 6.4, and installed MySQL using the version that came with the Centos distribution. To my dismay, it is MySQL 5.1.69 versus the current 5.6.12. As stated on http://dev.mysql.com/doc/refman/5.5/en/linux-installation-native.html, "the MySQL version will often be some way behind the currently available release", but I didn't expect that long.
[root#centosBox ~]# rpm -qa | grep mysql
mysql-5.1.69-1.el6_4.x86_64
mysql-devel-5.1.69-1.el6_4.x86_64
mysql-server-5.1.69-1.el6_4.x86_64
mysql-libs-5.1.69-1.el6_4.x86_64
[root#centosBox ~]# whereis mysql
mysql: /usr/bin/mysql /usr/lib64/mysql /usr/include/mysql /usr/share/mysql /usr/share/man/man1/mysql.1.gz
[root#centosBox ~]#
An alternative is to install by RPM packages which is the "recommended way to install MySQL" per http://dev.mysql.com/doc/refman/5.5/en/linux-installation-rpm.html. I have done so and it wasn't overly complicated, however, I am concerned as I've often been told that I should always install by yum when available. Towards the very end of the documentation, it does describe doing so extremely briefly using yum, however, it is so brief that I question whether it is the way to go.
So.... What is the best way for a not guru Linux user to install/upgrade MySQL on a Centos machine?
Just this week (2013-10-28), MySQL announced official yum repositories for MySQL Community Edition. The packages are intended for use with RHEL-compatible Linux (e.g. CentOS).
All the details including how to set up the yum repo on your system, can be found from the announcement:
http://insidemysql.com/announcing-new-yum-repositories-for-mysql/
A bit off-topic but there we go.
It is recommended to install from the repositories because you can later update your software to a newer version with a simple yum upgrade. The repository takes care of that for you, as well as any dependencies the software may entertain with other libraries.
RPM Packages installed manually (even with yum, which then only acts as an installer) will have to be managed manually as well.
Since the MySQL RPM package shows no dependencies (as far as I can tell from the manual), you are safe from this side.
And to answer your question: the best method is to stick with the versions from the repository. If you need a newer version, then you took the right path.
I am no guru myself but I was happy with the result of the RPM method you mentioned since other times I have seen problems with mysql-libs being a dependency for other packages.
(depending on the 5.6 version you want and cpu)
mkdir MySQL
cd MySQL
wget http://dev.mysql.com/get/Downloads/MySQL-5.6/MySQL-5.6.16-1.el6.x86_64.rpm-bundle.tar
tar -xvf MySQL-5.6.16-1.el6.x86_64.rpm-bundle.tar
yum install MySQL*rpm
installs them in the correct order and removes mysql-libs in one step without conflicts.
http://dev.mysql.com/doc/refman/5.6/en/linux-installation-rpm.html
It doesn't surprise me that MySQL is a bit behind. Why would Oracle make it easy for you to not use pay-for Oracle? </rant>
Anyway, you can get the awkwardly named, but otherwise identical MariaDB to run easily by adding a new YUM repository.
You can install MySQL 5.5 (mysql55-server.x86_64) from IUS repository (currently version 5.5.34 available)
I'm running Mac OSX 10.6.4 and setting up rails for the first time. I've been following a bunch of guides to get set up, specifically these two here and here. Also, I know this question has been asked before, but nothing has helped me and my circumstances are a bit different.
First, let me give you my setup.
I've installed Xcode, but I don't want to use the system ruby so, what I did was, I installed RVM and created two gemsets for different ruby versions (1.8.7#rails2.3.8 and 1.9.2#rails3), cause I also want to try rails 3.
I created a global gemset so that I could install passenger and mysql for 1.8.7 and not have to do it for each project. Then set the global gemset by rvm gemset use global
I had already installed MacPorts in a previous step, so what I've done is install mysql using this command sudo port install mysql5 mysql5-server.
Now I run gem install passenger and then passenger-install-apache2-module. This is where I ran into the first issue. Passenger installed fine, but I got "no definition" errors when it tried to install the documentation.
Finally, I want to install the mysql gem so I followed the steps here by adding rvm_archflags="-arch x86_64" to the ~/.rvmc file and then ran export ARCHFLAGS="-arch x86_64" ; gem install mysql -- --with-mysql-config=/opt/local/lib/mysql5/bin/mysql_config Here is where I ran into the issue again. I got a "Successfully installed mysql-2.8.1" message, but all the documentation returned "no definition" errors!
So, why am I getting these errors when installing gems? What can I do to get them installed without errors and ensure future gem installations don't have this problem?
Note: I'm not using sudo because RVM tells you not to.
Here is a link to your problem. They are saying the same thing and the answer is that it's just noise. Obviously something is not right but there is not and should not be a problem. It's most likely that all is fine and documentation was not created, installed, or linked correctly.
http://www.sitepoint.com/forums/showthread.php?t=629077
A -- alone (as written in step 5) usually means to stop reading options. I expect that this is wrong and doesn't belong here or is incomplete (ie, should be --something).
ah...it is not easy to get started ruby on rails to me..
I am trying to use mysql for ruby on rails development.
When I execute "gem install mysql", I get following error.
error: while generating documentation for mysql-2.8.3-x86-mswin32...message: unhandled special: special: type=17...bla bla...
how do I install mysql for ruby on rails!??!
If you are on windows and want to avoid mysql issues, just use v 2.1.2, just before they removed the mysql connector and put it into the mysql gem. It's better like that, but I ran into MANY issues installing this on the Windows XP machine at my work.
Make sure that your version of gems is the latest.
You should be able to update it using:
gem update --system
Going by your error it failed to generate the documentation for the Gem, though it could have installed it as it was. Firstly check to see if it did install, use:
gem list --local
And check to see if the MySQL driver is in the list already.
If it isn't the make sure you're installing the correct version of the driver, either mswin32, or ruby should do.
That's an error concerning rdoc generation. If you execute the following command you'll get no error:
gem install --no-rdoc mysql
I believe there are some problems generating rdoc for the Japanese localized version of the docs. Anyway, the mysql gem gets installed.
You can easily install the MySQL gem
either install the MySQL in ruby file where all gems are install or you can follow the path:
C:\Ruby192\lib\ruby\gems\1.9.1\gems
execute the below command:
gem install MySQL
hope this helps you!