Tag Info

New answers tagged

0

Try this: $ yum install --downloadonly --downloaddir=/pkgs/ `cat pkg_list` You can specify multiple package names on the yum command line. The only caveat here is that your command line may become too long for the shell. Thanks


0

I think it is your rpm install which is somehow off. I would expect on CentOS 5.11 with yum 3.2.22 installed that your rpm version would be 4.4.2.3, not 4.3.3 Specifically the rpm-libs package installs /usr/lib64/librpmdb-4.4.so which yum 3.2.22 requires but I am guessing you have /usr/lib64/librpmdb-4.3.so I suggest you download the new rpm-*4.4.*rpm ...


0

It turns out that the files in /var/lib/rpm with db in their names are not Berkeley database files. The files with no db in their names are Berkeley database files. So trying to open a file named __db.001 is the wrong thing to do. (Thought about just deleting the question, but other people may run into this).


1

I believe you're out of luck if you want to use yum. That's not a feature the yum package supports. yum uses a subset of all the features provided by the rpm command. (It actually uses a python module rpmUtils rather than calling rpm directly.)


2

Since you installed from source code (I'm guessing with ./configure; make; make install), the RPMDB (RPM database) didn't get updated, so RPM thinks you still ahve the old version installed. If you want RPM to know about the new version, find an RPM of the new version (or make one) and install it with RPM (rpm -i).


0

Sadly (or fortunately, depends how you see it) there's no such thing as selective file removal. What I'd propose is to list the files, the config files marked as such, and the documentation for each package in question and go through the list what you want to keep. Use rpm -ql packagename for listing the files rpm -qc packagename for listing the config ...


0

First define a macro e.g: %define runcommand() ( /usr/bin/firefox http://google.com ) Then under the %post section run %runcommand. Since the package requires root access and root the %post macro won't be able to find a DISPLAY. Exporting DISPLAY environment variable should solve this problem. For example ...... %post export DISPLAY=":0.0" ...


0

Short answer: no it can't. There's no guarantee you will have a graphical environment available anywhere to open a browser in - you could be on a system with only a WYSE-60 terminal as console and no network connection. Moreover, if there are errors in the installation, it should not have completed. That's part of what packaging is designed to take care of. ...


0

As @Arthur stated, the problem is the disconnect between what's on the system and what's in the RPMDB. While the RPMDB does indeed have a JDK that it knows is installed, that JDK may not satisfy the package dependencies of the package you're attempting to install - in fact it definitely does not or you wouldn't be getting the particular error message. Where ...


0

It's true that you have a JDK, but it is not in the RPM database, which is used by yum and other similar automatic package managers to know what packages are installed and get there respective versions. The best solution may be running sudo yum install jdk so you can get a version with yum and rpm. You can also consider following its suggestion to add the ...


0

The issue with this was that the package that provided the .so file was not installed. yum provides [.so] yum install [name of providing rpm] alternatively using yum dependencies are resolved on their own, so yum install [package] Should have been sufficient. Basically when possbile, use yum not rpm.


1

It sounds like the package(s) were configured so that the httpd.conf file(s) were not declared to be "config" files. See http://www.rpm.org/max-rpm/s1-rpm-erase-and-config-files.html


2

This error happens because you have some YUM repository configuration in /etc/yum.repos.d/ that lists a GPG key like this: gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puias This configuration is telling YUM that the GPG key for the repository exists on disk. The error you get from YUM is YUM letting you know that it couldn't find the GPG key at the path ...


0

This worked for me: Go to /etc/pki/rpm-gpg directory and download the RPM-GPG-KEY-puias from http://springdale.math.ias.edu/data/puias/6/x86_64/os/RPM-GPG-KEY-puias : su - root cd /etc/pki/rpm-gpg wget http://springdale.math.ias.edu/data/puias/6/x86_64/os/RPM-GPG-KEY-puias By the way, I appreciate if someone explains the issue more.



Top 50 recent answers are included