mjhjmtu

Lets say I want to make an RPM which delivers an Apache Webserver with its own OpenSSL:

/mydir/apache_postfix1
/mydir/openssl_postfix1

Since Apache mod_ssl requires a real OpenSSL installation I have to configure --prefix=/mydir/openssl, make, make install OpenSSL to /mydir/openssl so Apache with mod_ssl can actually compile with configure --with-ssl=/mydir/openssl.

Unthinkable on a build server (Jenkins) with no permissions on anything outside its jobs directory. But I need to build Apache with OpenSSL and package it into an RPM (to deliver postfixed multiple Apaches each with their own OpenSSL).

So I thought that mock is the solution (which is more likely to be installed on the build server than we get any user/install permissions).

But I haven't found a full documentation on how I can use mock to use rpmbuilds full capabilities.

I tried mock -r epel-7-x68_64 example.src.rpm but it is looking for /builddir/build/SPECS/example.spec and so failing ... why? from where did it got this file?

This was just an example, the real problem consists of 7 independent software packages which should get configured/compiled against each other so they act as a single service ... and packaged into a single RPM for Red Hat Satellite to be delivered onto >200 servers ... without actually installing them on the build server ...

Any help or a link to usable documentation/examples are highly appreciable!

The best sources of documentation would be the mock source code, the official rpm documentation, the rpm packaging guide, and any further documentation any of those recommend. As for your posted example, it appears your example.src.rpm package does not have a proper spec file in the correct place for mock to work with.

mock will take an input of a src.rpm file to rebuild, or you can use a spec file and sources directory to build a source rpm (SRPM). With some extra config, you can even use mock directly with source code checkouts. Once you have mock installed and a user configured to use it (mock will complain if you attempt to use as root, an unprivileged user needs to be in the mock group), it is fairly simple to use:

yumdownloader --source openssl
mkdir rpm-results
mock -r epel-7-x68_64 --resultdir=rpm-results openssl-*.src.rpm

That will rebuild the distribution provided OpenSSL and place the resulting packages in the rpm-results dir. To make changes to the distribution provided package, you would want to install the src.rpm, make your changes, then build the resulting rpm files:

yumdownloader --source openssl
rpm -ivh openssl-*.src.rpm
# usually this installs to ~/rpmbuild
# make your changes to ~/rpmbuild/SOURCES/* and ~/rpmbuild/SPEC/openssl.spec as necesary
mkdir rpm-results
mock -r epel-7-x68_64 --resultdir=rpm-results --buildsrpm ~/rpmbuild/SPEC/openssl.spec
mock -r epel-7-x68_64 --resultdir=rpm-results rpm-results/openssl-*.src.rpm

I am not sure if newer versions do not require the two step build (SRPM => RPM), but this is how we have been using mock at my shop. You would likely want/need to do that for each package you are attempting to rebuild. I would not advise packaging everything into a single package like you ask, but nothing technically stops you from doing that. You would just need to make you own spec file that combines everything together or use a different tool such as FPM.

I am a maintainer of Mock, so I should provide you an answer. But I really cannot, because you did not specify what is actually a problem.

I can only elaborate on how Mock works and resolve some of your confusions.

When you call mock -r fedora-27-x86_64, then Mock will do (skipping some boring details):

1. dnf install --installroot /var/lib/mock/fedora-27-x86_64/root @buildsys-build This will install minimal system in separate directory. Further in this answer I will refer to /var/lib/mock/fedora-27-x86_64/root as $CHROOT.




2. Mock will extract your example.src.rpm. Especially it will put spec file into $CHROOT/builddir/build/SPECS and tar ball into $CHROOT/builddir/build/SOURCES.




3. Mock will parse your spec file and install all packages listed in BuildRequires into $CHROOT. (This is done as root).




4. Mock will then chroot() into $CHROOT and run there rpmbuild -ba /builddir/build/SPECS/example.spec. This is done as unprivileged user (with the UID equal to your UID). This is done because running rpmbuild have always been discouraged and can lead to serious problems.

So if you want to install some additional packages in chroot., you should not do that from within spec file by calling yum/dnf install (especially because rpm is not reentrant). But you should specify those packages in BuildRequires and provide a repository with those packages.

You can provide a repository either using mockchain -a REPOS (mockchain is a thin layer on top of mock) or by:

cp /etc/mock/fedora-27-x86_64.cfg ~/my-custom-fedora-27-x86_64.cfg
#add your repository to ~/my-custom-fedora-27-x86_64.cfg
mock -r ~/my-custom-fedora-27-x86_64.cfg example.src.rpm

If you have 7 src.rpm packages depended on each other, then probably the best way is to call mockchain 1.src.rpm 2.src.rpm .... 7.src.rpm and mockchain will create a temporary repository for results and try to build those packages in a naive way in while at-least-one-package-build do another loop.

If you specify what is actually your problem, then I can provide a more specific answer.