ruby-1.9.3-rpm icon indicating copy to clipboard operation
ruby-1.9.3-rpm copied to clipboard

Not an issue; works on centos 5.7 x86_64

Open petemounce opened this issue 12 years ago • 2 comments

Hi

I'd email/message, but github says you haven't provided an email address.

I've successfully built a ruby 1.9.3-p0 rpm on CentOS 5.7 x86_64 by following your steps; thanks!

Now to see whether that installs to my Amazon EC2 AMI and works well.

Regards Pete

petemounce avatar Mar 06 '12 09:03 petemounce

The RPM I built does not install on my Amazon AMI (created from EU-West-1's https://aws.amazon.com/amis/4158 I think):

[ec2-user@ip-1-2-3-4 ~]$ sudo yum --enablerepo=epel install ruby-1.9.3p0-2.x86_64.rpm
Loaded plugins: fastestmirror, priorities, security, update-motd
Loading mirror speeds from cached hostfile
 * amzn-main: packages.eu-west-1.amazonaws.com
 * amzn-updates: packages.eu-west-1.amazonaws.com
 * epel: mirror.bytemark.co.uk
280 packages excluded due to repository priority protections
Setting up Install Process
Examining ruby-1.9.3p0-2.x86_64.rpm: ruby-1.9.3p0-2.x86_64
Marking ruby-1.9.3p0-2.x86_64.rpm as an update to ruby-1.8.7.357-1.10.amzn1.x86_64
Resolving Dependencies
--> Running transaction check
---> Package ruby.x86_64 0:1.8.7.357-1.10.amzn1 will be obsoleted
---> Package ruby.x86_64 0:1.8.7.357-1.10.amzn1 will be updated
---> Package ruby.x86_64 0:1.9.3p0-2 will be obsoleting
--> Processing Dependency: libcrypto.so.6()(64bit) for package: ruby-1.9.3p0-2.x86_64
--> Processing Dependency: libdb-4.3.so()(64bit) for package: ruby-1.9.3p0-2.x86_64
--> Processing Dependency: libreadline.so.5()(64bit) for package: ruby-1.9.3p0-2.x86_64
--> Processing Dependency: libssl.so.6()(64bit) for package: ruby-1.9.3p0-2.x86_64
--> Processing Dependency: libtermcap.so.2()(64bit) for package: ruby-1.9.3p0-2.x86_64
--> Processing Dependency: libyaml-0.so.1()(64bit) for package: ruby-1.9.3p0-2.x86_64
---> Package ruby-libs.x86_64 0:1.8.7.357-1.10.amzn1 will be obsoleted
--> Running transaction check
---> Package compat-readline.x86_64 0:5.1-3.13.amzn1 will be installed
---> Package db43.x86_64 0:4.3.29-10.9.amzn1 will be installed
---> Package openssl098e.x86_64 0:0.9.8e-17.7.amzn1 will be installed
---> Package ruby.x86_64 0:1.9.3p0-2 will be obsoleting
--> Processing Dependency: libtermcap.so.2()(64bit) for package: ruby-1.9.3p0-2.x86_64
--> Processing Dependency: libyaml-0.so.1()(64bit) for package: ruby-1.9.3p0-2.x86_64
--> Finished Dependency Resolution
Error: Package: ruby-1.9.3p0-2.x86_64 (/ruby-1.9.3p0-2.x86_64)
           Requires: libtermcap.so.2()(64bit)
Error: Package: ruby-1.9.3p0-2.x86_64 (/ruby-1.9.3p0-2.x86_64)
           Requires: libyaml-0.so.1()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

I'm now going to follow the AMI instructions, but I'd hoped to avoid that because I didn't want to put development tools on a production instance.

(I should mention that I'm very much unfamiliar with 'nix sysadmin so far, being primarily a .NET developer. I'm going to RTFM; I'm just documenting my progress really)

petemounce avatar Mar 06 '12 12:03 petemounce

I was able to successfully follow the AMI instructions.

I was also able to follow them successfully with the recent 1.9.3-p125 release just by changing the %define rubyminorver p125 line at the top of the RPM spec.

petemounce avatar Mar 06 '12 15:03 petemounce