New answers tagged

0

That is a valid concern, however the client side is also an issue. The clients also cache the repo information. This means you can still have problems when a client tries to update when the repo has changed, but the client hasn't updated its local cache information yet. So you end up running yum clean all anyway to force them to update their local cache. ...


1

rpmbuild adds Python requiremenst automatically from the version of python used. As such, it was adding python(abi)=2.7 to the requires list of the RPM. However, when using the python27 that scl was using provides python27-python. The issue was resolved by adding the line AutoReqProv: no to the spec file in the RPM. The machine that was having the rpm ...


0

Have you tried defining it from the rpmbuild command-line? The --showrc switch shows you the "level" at which various macros are defined. There is a hierarchy in case something is defined in more than one place, where -8 (command-line) wins out over -14 (disk, i.e. ~/.rpmmacros file). $ rpmbuild --showrc | grep ' _sbindir' -14: _sbindir %{...


0

The Packager tag discouragement is poorly worded--I think the intent would be clearer something like this: "Don't hard-code your name in the Packager field in the RPM specfile. The rpmbuild tool will fill it in from the macro, if defined." Where macro can be defined like this: rpmbuild --define "packager $USER@$HOSTNAME" | grep -i packager -8: packager ...


3

I'd suggest installing it into another directory with rpm --prefix and pull out the stuff you need. Alternatively, you could extract it directly with rpm2pcio package.rpm | cpio -idmv. Using --prefix does at least have the benefit of executing any post-install scripts, etc... in the RPM. Hope the helps!



Top 50 recent answers are included