New answers tagged

0

Here's a specific example using "httpd" as the package to download and install. This process was tested on both CentOS6 and CentOS7. Install the stuff you need and make a place to put the downloaded RPMs: # yum install yum-plugin-downloadonly yum-utils createrepo # mkdir /var/tmp/httpd # mkdir /var/tmp/httpd-installroot Download the RPMs. This uses the ...


1

Thanks for the detailed explanation maxschlepzig, but your proposed fix isn't correct. It would result in comdir being set to /usr/share/bash-completion when bash-completion is installed. Files from there aren't loaded, they have to be in /usr/share/bash-completion/completions. That would break being able to consistently use %{compdir} as an install ...


1

Seems you're asking for yumdownloader which is contained in the package yum-utils. There are already a few questions and answers about this, see e.g. Download all dependencies with yumdownloader, even if already installed? or How do I find package URLs with Yum? yumdownloader will download the packages, although it will not generate a file Install.sh as the ...


0

The Docker image is extremely stripped down. I believe they remove the man pages after the RPMs are installed. You can verify this with rpm -V shadow-utils. I know I've had problems trying to use delta RPMs to upgrade packages because the man pages are missing. Sadly, I think the only way to get a man page for something would be to force reinstall the RPM ...


0

Why aren't you switching to non-interactive session? # TMOUT=0 -bash: TMOUT: readonly variable # unset TMOUT -bash: unset: TMOUT: cannot unset: readonly variable # su # export TMOUT=10 # unset TMOUT #


0

A source RPM (src.rpm) is source packaged up using the RPM format. You can use that to build a binary package for your machine, or use it as a starting point for custom versions. Source RPMs are quite a bit more portable than binary ones, but unless you are knowledgeable I'd advise against going down this path. Check the CentOS pages, see if there are ...


1

The reason why you're seeing that error is because the person who maintains the package incorrectly included /usr/share/man and /usr/share/man/man1 in the RPM package's definition of what the package "owns". Because the package claims to own that directory (and will try to delete it if you uninstall it), yum detects that another, already installed package, ...


1

Try installing the previous version: rpm -ivh http://binaries.html-tidy.org/binaries/tidy-5.1.14/tidy-5.1.14-64bit.rpm


0

I will assume a lot, your descriptions lack much needed information, and mislead otherwise. I would assume that install.sh is the script you expect to run in bash, presented by you as: a="/var/mqm/trace/WMQUNX8000.00/LINUX/MQV8000GA/6/x86_64/install.sh" If that is true, call it as: /path/to/bash "$a" Of course, install.sh should have this code Again, ...


7

Software from the distribution is mechanically linked consistently, and expects to find libavcodec.so.54, so the unversioned name isn't required for any of the pre-built packages. If you're building software yourself, however, it's common to use -lavcodec or similar, which will find libavcodec.so unversioned. Similarly, build scripts may expect these names ...


1

Use the --excludepath= option, for instance if you have this kind of error: $ sudo rpm -i chromium-27.0.1453.110-202711.x86_64.rpm error: unpacking of archive failed on file /usr/share/applications/chromium-devel.desktop;569df493: cpio: open failed - Permission denied you can use the option like this: $ sudo rpm -i ...


1

Mockchain (from mock package) can do what you want. It accept list of SRPM as parameter, It has very naive algorithm which tries to rebuild them, those which fails are tried in second iteration. Those iteration continues as long as at least package is built successfully in the loop. So it can consume lots of CPU cycles, but it does not require too much ...


0

Requires are not inherited to subpackages. Just remove the line Requires: %{nil} and it will work.


2

rpm-4.8.0 has added a global file lock in /var/lib/rpm/.rpm.lock that prevents an rpm install from recursing by invoking rpm in %post. See why can't I install packages with rpm? I get "transaction lock" Meanwhile there is very little need to have/use a global interprocess lock: rpm (and processes that depend on rpmlib like yum) hardly ...


1

Built files that get created with make install during the %makeinstall phase need to be explicitly included or excluded. I was able to work around this by running manual rm commands after %makeinstall, but there appears to be another workaround in the %files section using %exclude clauses: %files %defattr (-,root,root) %{_libdir}/libmp3lame.so.* ...


1

Removing the configuration for the repository does not delete the packages you got from it, and those are the ones with broken dependencies. CentOS warns forcefully that some third party repositories break the system by overwriting core packages. There are a few vetted repositories, checked (somewhat) not do cause terrible grief. Delete the broken packages ...


0

I had to set the baseurl gpg to point to local locations such as this. [media] name=Red Hat Enterprise Server DVD Media baseurl=file:///run/media/user/RHEL-7.2\ Server.x86_64/ enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-Key-redhat-release



Top 50 recent answers are included