With the --postinstall option, mock tries to install the built RPMs. This is not aligned with a way how RPMs are built in Koji - the --postinstall is not used there. It therefore means that for some components containing packages which cannot be installed (for whatever reason), the mock-build fails while Koji scratch-build works. This is confusing to users.
In this commit, the --postinstall option is removed. The mock-build should focus on building the RPMs, testing whether they can be installed should be done as separate test.
With the
--postinstalloption, mock tries to install the built RPMs. This is not aligned with a way how RPMs are built in Koji - the--postinstallis not used there. It therefore means that for some components containing packages which cannot be installed (for whatever reason), the mock-build fails while Koji scratch-build works. This is confusing to users.In this commit, the
--postinstalloption is removed. The mock-build should focus on building the RPMs, testing whether they can be installed should be done as separate test.