Hi, On 06/19/2017 05:16 AM, Michael Schroeder wrote:

On Fri, Jun 16, 2017 at 04:08:41PM +0200, Olaf Hering wrote:

...

Am Fri, 16 Jun 2017 10:06:53 -0400 schrieb Robert Schweikert :

...

How do I skip something during the install test of a package build in the build service?

test -e /.build.log && exit 0

Bad advice. Do not test for /.build.log, the standard way is to test for existence of the /.buildenv file.

OK, thanks that does the trick :) Next question is how do I combine noarch with arch specific builds? The primary package is noarch, i.e. BuildArch: noarch but the subpackage has architecture specific code. The sub-package definition inherits the "noarch" setting. Do I have to redefine BuildArch or is there some "reset to default"? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Architect LINUX Team Lead Public Cloud rjschwei@suse.com IRC: robjo -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Jun 19 2017, Robert Schweikert wrote:

The primary package is noarch, i.e.

BuildArch: noarch

but the subpackage has architecture specific code. The sub-package definition inherits the "noarch" setting. Do I have to redefine BuildArch or is there some "reset to default"?

You can't do that. Either make an arch specific package the primary package, or add a dummy primary package. Then you can add noarch subpackages. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On 06/19/2017 03:20 AM, Andreas Schwab wrote:

On Jun 16 2017, Robert Schweikert wrote:

...

The package needs contain a %post in this section during regular install a script gets executed that modifies files in the root file system when installed on a running system. During package build these files are not there and thus %post fails during the install test.

Why are the files not present? That looks like a missing dependency.

Yes and no. Yes because I could add the "missing" packages as BuildRequires, no because that is not sufficient the %post script that runs also reaches out to the cloud framework metadata server which we will not have in the BuildService, so the "missing" build requires is somewhat of a moot point as the script will not ever work inside the Build Service, I just really need to disable it during the install test in the Build Service. How do I get that done? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Architect LINUX Team Lead Public Cloud rjschwei@suse.com IRC: robjo -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org