10 More Discussions You Might Find Interesting
1. AIX
I am trying to install an rpm : libiconv-1.14-1.aix5.1.ppc.rpm which is a dependency to install GIT.
While I gave the command I got the foll message:
root:user-> $ rpm -i -v libiconv-1.14-1.aix5.1.ppc.rpm
libiconv-1.14-1
ar: Cannot open or remove a file containing a running program.... (2 Replies)
Discussion started by: gaugeta
2 Replies
2. AIX
I am attempting to install an rpm of Apache from perzl.org on an AIX 6100-07-03-1207 server and it is failing. I think I have all of the dependencies installed. Can anyone help? Any help would be appreciated.
It fails with the following error:
# rpm -Uvh httpd-2.4.2-2.aix5.1.ppc.rpm ... (3 Replies)
Discussion started by: lbholde
3 Replies
3. Red Hat
hi,
i am try to install a package in centos 6.2 x86-64 but unable to find any package in centos media iso.
In RHEL we have a product folder which contain all the list of rpm but in centos i cant found that.
I have use yum command but it also cant work show me the message no module named yum.... (1 Reply)
Discussion started by: zeeshan047
1 Replies
4. Red Hat
Hi,
I would like to know is it possible to install rpm along its depedable rpm from mounted .iso image on Redhat Linux
while installing rpm it is showing so many depandancy, so I would like to know with single command wheather it will take all depedable rpm from mounted iso image. (1 Reply)
Discussion started by: manoj.solaris
1 Replies
5. Programming
Hello,
I want to read a rpm database through my program in c ,I searched for it and found there is one library openly available that is rpmlib thorugh which we can access rpm databse but I want to use it from windows is it possible to read one rpm database from windows,I want to read the... (4 Replies)
Discussion started by: pradiptart
4 Replies
6. Red Hat
Hi guys, I am trying to install some packages for my oracle 11g r2 installation, the below error shows up when I try below:
warning: glibc-devel-2.5-24.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed dependencies:
glibc-headers is needed by... (8 Replies)
Discussion started by: messi777
8 Replies
7. Shell Programming and Scripting
How to make RPM not write to RPM database if RPM fails to deploy?
IE I create an rpm spec file that contains the following
if
then
exit 1
fi
My rpm will fail at deployment, but if I do rpm -qa , I can see the rpm in the rpm db (3 Replies)
Discussion started by: 3junior
3 Replies
8. Shell Programming and Scripting
Hi,
I have an application to be installed and I want a user to be able to install it.
But I meet the following issues:
Removing MyApp
error: cannot get exclusive lock on /var/lib/rpm/Packages
error: cannot open Packages index using db3 - Operation not permitted (1)
error: cannot open... (1 Reply)
Discussion started by: potro
1 Replies
9. HP-UX
I am working on a HP-UX PARISC 64 architecture.
I am trying to install RPM but without success.
Has any body successfully installed RPM on the above architecture.
I couldnt find a compatible depot file.
I tried to compile the source code for rpm-4.0 package.
All the dependencies are... (3 Replies)
Discussion started by: sjcekk
3 Replies
10. UNIX for Dummies Questions & Answers
Ok when i try to run the install the is what i get
How can i fix this can anyone help (8 Replies)
Discussion started by: Blackrose
8 Replies
BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
NAME
bundle-update - Update your gems to the latest available versions
SYNOPSIS
bundle update *gems [--source=NAME]
DESCRIPTION
Update the gems specified (all gems, if none are specified), ignoring the previously installed gems specified in the Gemfile.lock. In gen-
eral, you should use bundle install(1) bundle-install.1.html to install the same exact gems and versions across machines.
You would use bundle update to explicitly update the version of a gem.
OPTIONS
--source=<name>
The name of a :git or :path source used in the Gemfile(5). For instance, with a :git source of http://github.com/rails/rails.git,
you would call bundle update --source rails
UPDATING ALL GEMS
If you run bundle update with no parameters, bundler will ignore any previously installed gems and resolve all dependencies again based on
the latest versions of all gems available in the sources.
Consider the following Gemfile(5):
source "http://rubygems.org"
gem "rails", "3.0.0.rc"
gem "nokogiri"
When you run bundle install(1) bundle-install.1.html the first time, bundler will resolve all of the dependencies, all the way down, and
install what you need:
Fetching source index for http://rubygems.org/
Installing rake (0.8.7)
Installing abstract (1.0.0)
Installing activesupport (3.0.0.rc)
Installing builder (2.1.2)
Installing i18n (0.4.1)
Installing activemodel (3.0.0.rc)
Installing erubis (2.6.6)
Installing rack (1.2.1)
Installing rack-mount (0.6.9)
Installing rack-test (0.5.4)
Installing tzinfo (0.3.22)
Installing actionpack (3.0.0.rc)
Installing mime-types (1.16)
Installing polyglot (0.3.1)
Installing treetop (1.4.8)
Installing mail (2.2.5)
Installing actionmailer (3.0.0.rc)
Installing arel (0.4.0)
Installing activerecord (3.0.0.rc)
Installing activeresource (3.0.0.rc)
Installing bundler (1.0.0.rc.3)
Installing nokogiri (1.4.3.1) with native extensions
Installing thor (0.14.0)
Installing railties (3.0.0.rc)
Installing rails (3.0.0.rc)
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
As you can see, even though you have just two gems in the Gemfile(5), your application actually needs 25 different gems in order to run.
Bundler remembers the exact versions it installed in Gemfile.lock. The next time you run bundle install(1) bundle-install.1.html, bundler
skips the dependency resolution and installs the same gems as it installed last time.
After checking in the Gemfile.lock into version control and cloning it on another machine, running bundle install(1) bundle-install.1.html
will still install the gems that you installed last time. You don't need to worry that a new release of erubis or mail changes the gems you
use.
However, from time to time, you might want to update the gems you are using to the newest versions that still match the gems in your Gem-
file(5).
To do this, run bundle update, which will ignore the Gemfile.lock, and resolve all the dependencies again. Keep in mind that this process
can result in a significantly different set of the 25 gems, based on the requirements of new gems that the gem authors released since the
last time you ran bundle update.
UPDATING A LIST OF GEMS
Sometimes, you want to update a single gem in the Gemfile(5), and leave the rest of the gems that you specified locked to the versions in
the Gemfile.lock.
For instance, in the scenario above, imagine that nokogiri releases version 1.4.4, and you want to update it without updating Rails and all
of its dependencies. To do this, run bundle update nokogiri.
Bundler will update nokogiri and any of its dependencies, but leave alone Rails and its dependencies.
OVERLAPPING DEPENDENCIES
Sometimes, multiple gems declared in your Gemfile(5) are satisfied by the same second-level dependency. For instance, consider the case of
thin and rack-perftools-profiler.
source "http://rubygems.org"
gem "thin"
gem "rack-perftools-profiler"
The thin gem depends on rack >= 1.0, while rack-perftools-profiler depends on rack ~> 1.0. If you run bundle install, you get:
Fetching source index for http://rubygems.org/
Installing daemons (1.1.0)
Installing eventmachine (0.12.10) with native extensions
Installing open4 (1.0.1)
Installing perftools.rb (0.4.7) with native extensions
Installing rack (1.2.1)
Installing rack-perftools_profiler (0.0.2)
Installing thin (1.2.7) with native extensions
Using bundler (1.0.0.rc.3)
In this case, the two gems have their own set of dependencies, but they share rack in common. If you run bundle update thin, bundler will
update daemons, eventmachine and rack, which are dependencies of thin, but not open4 or perftools.rb, which are dependencies of
rack-perftools_profiler. Note that bundle update thin will update rack even though it's also a dependency of rack-perftools_profiler.
In short, when you update a gem using bundle update, bundler will update all dependencies of that gem, including those that are also depen-
dencies of another gem.
In this scenario, updating the thin version manually in the Gemfile(5), and then running bundle install(1) bundle-install.1.html will only
update daemons and eventmachine, but not rack. For more information, see the CONSERVATIVE UPDATING section of bundle install(1) bun-
dle-install.1.html.
RECOMMENDED WORKFLOW
In general, when working with an application managed with bundler, you should use the following workflow:
o After you create your Gemfile(5) for the first time, run
$ bundle install
o Check the resulting Gemfile.lock into version control
$ git add Gemfile.lock
o When checking out this repository on another development machine, run
$ bundle install
o When checking out this repository on a deployment machine, run
$ bundle install --deployment
o After changing the Gemfile(5) to reflect a new or update dependency, run
$ bundle install
o Make sure to check the updated Gemfile.lock into version control
$ git add Gemfile.lock
o If bundle install(1) bundle-install.1.html reports a conflict, manually update the specific gems that you changed in the Gemfile(5)
$ bundle update rails thin
o If you want to update all the gems to the latest possible versions that still match the gems listed in the Gemfile(5), run
$ bundle update
June 2012 BUNDLE-UPDATE(1)