Mailinglist Archive: opensuse-buildservice (89 mails)

< Previous Next >
[opensuse-buildservice] Re: questions re: creating & building minimal project/spec file
not appropriate? Or is the .tar.gz not properly handled?

On Fri, Apr 24, 2015, at 10:43 AM, Dmitriy Perlow wrote:
The final command of `%setup -q` is `cd %name-%version`, please add a top
level directory or modify %setup:

On Fri, Apr 24, 2015, at 10:38 AM, Andreas Schwab wrote:
%setup (without -n) assumes that the tarfile extracts to a directory
that is %{name}-%{version}. Since you have used %{basepkgname}-local
for the Name tag, this won't match what openssl-1.0.2a.tar.gz uses as
its toplevel directory.

Exactly what's needed; my source & build locations are sorted. Thanks.

I need to add specific repo dependencies for use in my build.

For this test case, I'm building for target openSUSE_13.2/x86_64, but want to
use specific pkgs for dependencies, from specific repos, not the 13.2 base.

Questions re: two instances,

(1) I need to build a cryptodev package as a prereq. It'll source both some
include files for this openssl, and a kernel module.

I'll publish both my cryptodev and openssl pkgs in the same OBS subproject.

In the openssl.spec is it sufficient to 'require cryptdev', so that the
LOCAL-to-the-subproject pkg is always used/referenced?

(2) For the kernel-module, I want it built against sources from the
KernelStable repos.

I added

BuildRequires: kernel-desktop-devel

to the spec, and added

Kernel_stable_standard to my porject's "Repositories of

but at build, it sources from 13.2 repos, not from KernelStable

(openSUSE:13.2) kernel-default-devel- 100% |==================| 2.5 MB
(openSUSE:13.2) kernel-devel-3.16.6-2 100% |==================| 10 MB
(openSUSE:13.2) kernel-macros-3.16.6- 100% |==================| 515 kB

What's the syntax in an osc build project to force preference of a pkg dep from
a different/specific repo?

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups