New answers tagged

0

Alternatively, pipe it into grep. rpm -qi packagename | grep -E '^(Name|Packager|Vendor) +:'


2

With --queryformat parameter: rpm -qi --queryformat "%{NAME} %{PACKAGER} %{VENDOR}\n"


1

You seem to have installed a newer version of mock provided by EPEL. For that package, the config files are changed from /etc/mock/centos-7-x86_64.cfg to /etc/mock/epel-7-x86_64.cfg and are provided by the RPM package mock-core-configs. The newer mock seems to be for the transition to dnf and python3, so they may have removed architectures that they no ...


0

Using __install as an example you can see where it's defined with rpm --showrc | grep __install Or you can see the definition with rpm --eval "%{__install}"


0

The package is executing a pre- or post-install script in /var/tmp/rpm-tmp.5WIuFR; on line 9 of that script, it is attempting to execute /etc/init.d/xxx-driver, but that latter file does not have execute permissions set.


3

Given the lack of mutual dependencies, which is guaranteed, the following algorithm will yield the minimal set: for each package in the list, list all of its requirements (rpm -qR foo) for each package in the requirements, remove it from the list if it’s present Listing foo’s requirements yields baz (presumably among others), and listing baz’s requirements ...


0

I'm afraid there is no easy way as the RPM file specifications (see e.g. here) do not include a tag to advertise the copyright holder, only the license type. It would seem that the only somewhat "scriptable" way relies on the contained files labelled as documentation, which you can list via rpm -qpd {rpmfilename}.rpm in the hope that the RPM packager ...


Top 50 recent answers are included