On Thu, Jan 29, 2015 at 2:42 PM, Jan Engelhardt
On Thursday 2015-01-29 19:27, Greg Freemyer wrote:
The OBS process for home / devel projects is simply:
- build a RPM - run rpmlint - if no major errors, publish
Note the total absence of installing the rpm or invoking any of the executables.
That is incorrect; as part of rpmlint (or was it post-build-checks, who knows), the RPMs get installed to see if the install-uninstall cycle is idempotent. Search for that exact last word in your build log.
Then how do packages with non-satisfied "Requires" statements get published? As an example I just branched a package: https://build.opensuse.org/package/show/home:gregfreemyer:branches:security/... I added "Requires: non-existent-junk" to the specfile. Yet, the package built and is now published. If the RPM was installed prior to publishing, it must have used a force option to ignore required packages. In fact if you look at: https://build.opensuse.org/package/binary/home:gregfreemyer:branches:security/python-plaso?arch=x86_64&filename=python-plaso-1.2.0-10.1.noarch.rpm&repository=openSUSE_13.2 you can see there are 7 different "Requires:" statements that can't be satisfied. (The other 6 are in security:forensics, but not in factory. The home project I added the branch to is not using security:forensics to satisfy Requires: statements.) fyi: I would prefer this build to fail. Maybe it is nice in home projects to let packages build that don't have all the "required" external packages, but in devel projects in particular, I think the build should fail. They don't. Thanks Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org