New answers tagged

0

if you still can't find your version with previous answer, you can try this : cat /etc/*-release


0

The last lines explain the issue. You shut down a VM that was in the middle of appending/changing the rpmdb. You will have to rebuid the rpmdb to fix the issue. If for some reason you do NOT have a backup of /var/lib/rpm, you will have to do it manually. Plenty of manuals, explanations and posts describing how.


0

1. Look at the yum log in /var/log/yum.log 2. yum downgrade package1 [package2] [...] For details look at the yum manpage


1

Notice the line: package custom-linux-9026-10.0.0-BUILD116.noarch is already installed So despite the filename of package-10.0.0B116-02202013-x64.rpm the package (in rpm header) is likely named custom-linux-9026-10.0.0-BUILD116. So you must call rpm -e custom-linux-9026-10.0.0-BUILD116


1

If you still have the original rpm file, extract the package name from it with -qp and the filename, eg $ rpm -qp ~/myrpm-1.0-05077.i586.rpm myrpm-1.0-05077.i586 and try using that in the rpm erase, as the filename might not match the package name.


0

rpm -aq | grep -i package.rpm if still not getting the output, then run updatedb command and try again i will if ignore case sensitive If you want to remove the rpm please give the full package name. rpm -e package-10.0.0B116-02202013-x64.rpm


0

Running the "yum update" operation will update any packages that are on the system. Specifically that means: Downloading new version Checking new version's download. Installing/Updating new version Checking new version's installation The old package is not installed any longer, just the new one. Depending on what extensions you have, you likely will only ...


1

I'd suggest two approaches to determine which packages can be removed: do a minimal installation with the RedHat release in question (which you didn't mention, by the way) and only add the packages on top which are mandatorily required for what this machine is intended to do. Then get the listing of all packages by name (so you could easily compare to ...


0

RPM packages does not contains incremental updates (as contrary to e.g. Solaris). So every package contains everything needed for both upgrade and clean install. When you call yum install firefox And firefox is already installed then yum should refuse to proceed even when there is newer version available. You should call: yum upgrade firefox This will ...


1

When you install new updates with yum, the original installed packages and binaries are updated. It doesn't keep multiple copies of them around. It does cache various things however. You can use various yum clean options to tidy up some of yum's own cache files. For example, yum clean packages will remove cached packages that have been downloaded, some ...


1

By default, rpmbuild strips binaries and libraries (using /usr/lib/rpm/brp-compress) after they have been placed in the rpm file. You should be able to disable this by adding to the start of your spec file %global __os_install_post %{nil}


2

You can do this using yum, by making a ".repo" repository file for your collection and running yum temporarily enabling this repository while disabling the other repositories. You might find this simplest by making a shell script to call yum while disabling the regular repositories. Use yum repolist to get the names to disable. Something like #!/bin/sh ...


0

I have also come across this problem today in SLES 11SP4 (RPM verion 4.4.2.3): there is neither a --noclean nor the rewrite the %clean tag suggested solution prevents the deletion of the /var/tmp/rpm-tmp.* script. I could solve the problem though by adding a succinct exit -1 at the end of the phase I was debugging: rpmbuilder exits with a error: Bad exit ...


0

I think the error says it: "missing or too old". Probably some symbols are missing in your library nss. You can check this using: nm <path-to-libnss3> | grep VFY_VerifyDigestDirect Now there are two possibilities: VFY_VerifyDigestDirect is found; that means the linker doesn't find your nss3 library after all VFY_VerifyDigestDirect is not found; ...


2

You are mixing CentOS 6 packages (.el6) with CentOS 7 packages (.el7), which is invalid. They differ a lot. You installed mysql56-community-release-el7.* instead of mysql56-community-release-el6*, where from you get that. Remove this wrong package source: yum remove "mysql56-community-release-el7.*" Install the correct one (as you installed the above ...



Top 50 recent answers are included