[opensuse-buildservice] osc copypac excludes repos?

newer
[opensuse-buildservice] missing...

vetter＠physik.uni-wuerzburg.de

16 Jan 2015 16 Jan '15

10:58

Hi, I did a # osc copypac security:Stunnel stunnel security:Stunnel stunnel-5.03 After that all repos of stunnel-5.03 are "excluded". But why? I checked .spec and Meta of the package and Meta of the project, but don't see the reason. I also disabled SLE_10 jsut to have something in the Can somesone enlighten me, please? -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Show replies by date

Adrian Schröter

16 Jan 16 Jan

11:05

On Freitag, 16. Januar 2015, 10:58:26 wrote vetter@physik.uni-wuerzburg.de:

...

Hi, I did a # osc copypac security:Stunnel stunnel security:Stunnel stunnel-5.03 After that all repos of stunnel-5.03 are "excluded". But why?

you have multiple spec files inside, but none of them is named "stunnel-5.03.spec". So OBS has no clue which one to pick, so it does "exclude" the package. You may want to create a "stunnel5.spec" and put it in some package container named "stunnel5" ?

...

I checked .spec and Meta of the package and Meta of the project, but don't see the reason. I also disabled SLE_10 jsut to have something in the Can somesone enlighten me, please?

-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

vetter＠physik.uni-wuerzburg.de

11:28

Adrian Schröter wrote on 16/01/2015 11:05:22:

...

On Freitag, 16. Januar 2015, 10:58:26 wrote vetter@physik.uni-wuerzburg.de:

...
Hi, I did a # osc copypac security:Stunnel stunnel security:Stunnel stunnel-5.03 After that all repos of stunnel-5.03 are "excluded". But why?

you have multiple spec files inside, but none of them is named "stunnel-5.03.spec".

So OBS has no clue which one to pick, so it does "exclude" the package.

You may want to create a "stunnel5.spec" and put it in some package container named "stunnel5" ?

...
I checked .spec and Meta of the package and Meta of the project, but don't see the reason. I also disabled SLE_10 jsut to have something in the Can somesone enlighten me, please?

Thanks. I renamed both specs to match the package name. And now the builds start. The repo-specific spec-file for SLE11-Security-Module is new for the package, so it didn't happen before. Is there another way to have a repo-specific BuildRequire apart from a repo-specific spec-file? -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Adrian Schröter

11:39

On Freitag, 16. Januar 2015, 11:28:29 wrote vetter@physik.uni-wuerzburg.de:

...

Adrian Schröter wrote on 16/01/2015 11:05:22:

...
On Freitag, 16. Januar 2015, 10:58:26 wrote vetter@physik.uni-wuerzburg.de:

...
Hi, I did a # osc copypac security:Stunnel stunnel security:Stunnel stunnel-5.03 After that all repos of stunnel-5.03 are "excluded". But why?

you have multiple spec files inside, but none of them is named "stunnel-5.03.spec".

So OBS has no clue which one to pick, so it does "exclude" the package.

You may want to create a "stunnel5.spec" and put it in some package container named "stunnel5" ?

...
I checked .spec and Meta of the package and Meta of the project, but don't see the reason. I also disabled SLE_10 jsut to have something in the Can somesone enlighten me, please?

Thanks. I renamed both specs to match the package name. And now the builds start. The repo-specific spec-file for SLE11-Security-Module is new for the package, so it didn't happen before.

Is there another way to have a repo-specific BuildRequire apart from a repo-specific spec-file?

You could add a %if "%_repository" == "..." line around the BuildRequries, but I like to recommend to use something like %suse_version and friends instead. The repo name is free text and may be called different in another project. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

vetter＠physik.uni-wuerzburg.de

19 Jan 19 Jan

09:45

...

From: Adrian Schröter To: vetter@physik.uni-wuerzburg.de Cc: opensuse-buildservice@opensuse.org Date: 16/01/2015 11:40 Subject: Re: [opensuse-buildservice] osc copypac excludes repos?

On Freitag, 16. Januar 2015, 11:28:29 wrote vetter@physik.uni-wuerzburg.de:

...
Adrian Schröter wrote on 16/01/2015 11:05:22:

...
On Freitag, 16. Januar 2015, 10:58:26 wrote vetter@physik.uni-wuerzburg.de:

...
Hi, I did a # osc copypac security:Stunnel stunnel security:Stunnel stunnel-5.03 After that all repos of stunnel-5.03 are "excluded". But why?

you have multiple spec files inside, but none of them is named "stunnel-5.03.spec".

So OBS has no clue which one to pick, so it does "exclude" the

Informations- und Kommunikationstechnik Tel: +49 (0)931 31-85890 Fakultaet fuer Physik und Astronomie Fax: +49 (0)931 31-85508 Universitaet Wuerzburg iuk@physik.uni-wuerzburg.de Adrian Schröter wrote on 16/01/2015 11:39:21: package.

...

...
...
You may want to create a "stunnel5.spec" and put it in some package container named "stunnel5" ?

...
I checked .spec and Meta of the package and Meta of the project,

but don't

...
...
see the reason. I also disabled SLE_10 jsut to have something in the Can somesone enlighten me, please?

Thanks. I renamed both specs to match the package name. And now the builds start. The repo-specific spec-file for SLE11-Security-Module is new for the package, so it didn't happen before.

Is there another way to have a repo-specific BuildRequire apart from a

...

...
repo-specific spec-file?

You could add a

%if "%_repository" == "..."

line around the BuildRequries, but I like to recommend to use something like %suse_version and friends instead. The repo name is free text and may be called different in another project.

Right. The repo is defined as a path: <repository name="SLE11-Security-Module"> <path project="SUSE:SLE-11:SP3:Update" repository="security"/> <arch>i586</arch> <arch>x86_64</arch> </repository> Is there some variable(s) containing the path? Would have to contain the project and repository part of the path. -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Adrian Schröter

20 Jan 20 Jan

08:36

On Montag, 19. Januar 2015, 09:45:18 wrote vetter@physik.uni-wuerzburg.de: ...

...

...
On Freitag, 16. Januar 2015, 11:28:29 wrote vetter@physik.uni-wuerzburg.de:

...
Adrian Schröter wrote on 16/01/2015 11:05:22:

...
On Freitag, 16. Januar 2015, 10:58:26 wrote vetter@physik.uni-wuerzburg.de:

...
Hi, I did a # osc copypac security:Stunnel stunnel security:Stunnel stunnel-5.03 After that all repos of stunnel-5.03 are "excluded". But why?

you have multiple spec files inside, but none of them is named "stunnel-5.03.spec".

So OBS has no clue which one to pick, so it does "exclude" the

Adrian Schröter wrote on 16/01/2015 11:39:21: ... package.

...
...
...
You may want to create a "stunnel5.spec" and put it in some package container named "stunnel5" ?

...
I checked .spec and Meta of the package and Meta of the project,

but don't

...
...
see the reason. I also disabled SLE_10 jsut to have something in the Can somesone enlighten me, please?

Thanks. I renamed both specs to match the package name. And now the builds start. The repo-specific spec-file for SLE11-Security-Module is new for the package, so it didn't happen before.

Is there another way to have a repo-specific BuildRequire apart from a

...
...
repo-specific spec-file?

You could add a

%if "%_repository" == "..."

line around the BuildRequries, but I like to recommend to use something like %suse_version and friends instead. The repo name is free text and may be called different in another project.

Right. The repo is defined as a path: <repository name="SLE11-Security-Module"> <path project="SUSE:SLE-11:SP3:Update" repository="security"/> <arch>i586</arch> <arch>x86_64</arch> </repository>

Is there some variable(s) containing the path? Would have to contain the project and repository part of the path.

we need to set it inside of SUSE:SLE-11:SP3:Update security repo then. But I have to admit that I am not really keen on that. Can't you just require "openssl-devel" in any case? depending on the repo config, you either get openssl v0 or v1... -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

vetter＠physik.uni-wuerzburg.de

09:47

...

On Montag, 19. Januar 2015, 09:45:18 wrote vetter@physik.uni-wuerzburg.de: ...

...
...
On Freitag, 16. Januar 2015, 11:28:29 wrote vetter@physik.uni-wuerzburg.de:

...
Adrian Schröter wrote on 16/01/2015 11:05:22:

...
On Freitag, 16. Januar 2015, 10:58:26 wrote vetter@physik.uni-wuerzburg.de:

...
Hi, I did a # osc copypac security:Stunnel stunnel security:Stunnel stunnel-5.03 After that all repos of stunnel-5.03 are "excluded". But why?

you have multiple spec files inside, but none of them is named "stunnel-5.03.spec".

So OBS has no clue which one to pick, so it does "exclude" the

Adrian Schröter wrote on 16/01/2015 11:39:21: ... package.

...
...
...
You may want to create a "stunnel5.spec" and put it in some

...

...
...
...
...
container named "stunnel5" ?

...
I checked .spec and Meta of the package and Meta of the

...

...
but

...
...
don't

...
...
see the reason. I also disabled SLE_10 jsut to have something in the Can somesone enlighten me, please?

Thanks. I renamed both specs to match the package name. And now

...

...
builds

...
...
start. The repo-specific spec-file for SLE11-Security-Module is new for

...

...
...
...
package, so it didn't happen before.

Is there another way to have a repo-specific BuildRequire apart from a

...
...
repo-specific spec-file?

You could add a

%if "%_repository" == "..."

line around the BuildRequries, but I like to recommend to use something like %suse_version and friends instead. The repo name is free text and may be called different in another project.

Right. The repo is defined as a path: <repository name="SLE11-Security-Module"> <path project="SUSE:SLE-11:SP3:Update" repository="security"/> <arch>i586</arch> <arch>x86_64</arch> </repository>

Is there some variable(s) containing the path? Would have to contain

Adrian Schröter wrote on 20/01/2015 08:36:44: package project, the the the

...

...
project and repository part of the path.

we need to set it inside of SUSE:SLE-11:SP3:Update security repo then.

But I have to admit that I am not really keen on that. Can't you just require "openssl-devel" in any case?

depending on the repo config, you either get openssl v0 or v1...

The SLE11-Security-Module is a addon for SLE11 that brings openssl v1 in addition to openssl v0 from SLE11. So both are available and the openssl-devel is v0. At least it was, when I tried after SLE11-Security-Module was available in OBS. Maybe it's not worth thinking about it, since SLE12 is available with openssl v1 only. My "knowledge" about how to use it in OBS stems from here (the FAQ part): https://www.suse.com/communities/conversations/introducing-the-suse-linux-en... -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Adrian Schröter

09:50

On Dienstag, 20. Januar 2015, 09:47:37 wrote vetter@physik.uni-wuerzburg.de:

...

Adrian Schröter wrote on 20/01/2015 08:36:44:

...
...
...
On Freitag, 16. Januar 2015, 11:28:29 wrote vetter@physik.uni-wuerzburg.de:

...
Adrian Schröter wrote on 16/01/2015 11:05:22:

...
On Freitag, 16. Januar 2015, 10:58:26 wrote vetter@physik.uni-wuerzburg.de: > Hi, > I did a > # osc copypac security:Stunnel stunnel security:Stunnel stunnel-5.03 > After that all repos of stunnel-5.03 are "excluded". But why?

you have multiple spec files inside, but none of them is named "stunnel-5.03.spec".

So OBS has no clue which one to pick, so it does "exclude" the

Adrian Schröter wrote on 16/01/2015 11:39:21: ... package.

...
...
...
You may want to create a "stunnel5.spec" and put it in some

...
...
...
...
container named "stunnel5" ?

> I checked .spec and Meta of the package and Meta of the

...
but

...
...
don't

...
> see the reason. > I also disabled SLE_10 jsut to have something in the > Can somesone enlighten me, please?

Thanks. I renamed both specs to match the package name. And now

...
builds

...
...
start. The repo-specific spec-file for SLE11-Security-Module is new for

...
...
...
package, so it didn't happen before.

Is there another way to have a repo-specific BuildRequire apart from a

...
...
repo-specific spec-file?

You could add a

%if "%_repository" == "..."

line around the BuildRequries, but I like to recommend to use something like %suse_version and friends instead. The repo name is free text and may be called different in another project.

Right. The repo is defined as a path: <repository name="SLE11-Security-Module"> <path project="SUSE:SLE-11:SP3:Update" repository="security"/> <arch>i586</arch> <arch>x86_64</arch> </repository>

Is there some variable(s) containing the path? Would have to contain

On Montag, 19. Januar 2015, 09:45:18 wrote vetter@physik.uni-wuerzburg.de: ... package project, the the the

...
project and repository part of the path.

we need to set it inside of SUSE:SLE-11:SP3:Update security repo then.

But I have to admit that I am not really keen on that. Can't you just require "openssl-devel" in any case?

depending on the repo config, you either get openssl v0 or v1...

The SLE11-Security-Module is a addon for SLE11 that brings openssl v1 in addition to openssl v0 from SLE11. So both are available and the openssl-devel is v0. At least it was, when I tried after SLE11-Security-Module was available in OBS. Maybe it's not worth thinking

The openssl1-devel package is also providing openssl-devel. So when you use the security repo, you should get v1 and not v0 with the same requirement (that was also the reason for a second repo, to give packagers an easy choice which one to use)

...

about it, since SLE12 is available with openssl v1 only.

My "knowledge" about how to use it in OBS stems from here (the FAQ part): https://www.suse.com/communities/conversations/introducing-the-suse-linux-en...

vetter＠physik.uni-wuerzburg.de

10:21

...

On Dienstag, 20. Januar 2015, 09:47:37 wrote vetter@physik.uni-wuerzburg.de:

...
...
On Montag, 19. Januar 2015, 09:45:18 wrote vetter@physik.uni-wuerzburg.de: ...

...
Adrian Schröter wrote on 16/01/2015 11:39:21: ...

...
On Freitag, 16. Januar 2015, 11:28:29 wrote vetter@physik.uni-wuerzburg.de:

...
Adrian Schröter wrote on 16/01/2015 11:05:22: > On Freitag, 16. Januar 2015, 10:58:26 wrote vetter@physik.uni-wuerzburg.de: [deleted intro] Is there some variable(s) containing the path? Would have to contain

Adrian Schröter wrote on 20/01/2015 08:36:44: the

...
...
project and repository part of the path.

we need to set it inside of SUSE:SLE-11:SP3:Update security repo

...

...
...
But I have to admit that I am not really keen on that. Can't you

just

...
require "openssl-devel" in any case?

depending on the repo config, you either get openssl v0 or v1...

The SLE11-Security-Module is a addon for SLE11 that brings openssl v1 in addition to openssl v0 from SLE11. So both are available and the openssl-devel is v0. At least it was, when I tried after SLE11-Security-Module was available in OBS. Maybe it's not worth

Adrian Schröter wrote on 20/01/2015 09:50:58: then. thinking

...

The openssl1-devel package is also providing openssl-devel.

So when you use the security repo, you should get v1 and not v0 with the same requirement (that was also the reason for a second repo, to give packagers an easy choice which one to use)

...
about it, since SLE12 is available with openssl v1 only.

My "knowledge" about how to use it in OBS stems from here (the FAQ

part):

...

...
https://www.suse.com/communities/conversations/introducing-the- suse-linux-enterprise-11-security-module/

Hm, I branched it, removed the extra-spec, used BuildRequires openssl-devel and now it is in this state: unresolvable: have choice for openssl-devel: libopenssl1-devel libopenssl-devel https://build.opensuse.org/package/show/home:asvetter:branches:security:Stun... -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Adrian Schröter

10:48

On Dienstag, 20. Januar 2015, 10:21:40 wrote vetter@physik.uni-wuerzburg.de:

...

...
On Dienstag, 20. Januar 2015, 09:47:37 wrote vetter@physik.uni-wuerzburg.de:

...
...
On Montag, 19. Januar 2015, 09:45:18 wrote vetter@physik.uni-wuerzburg.de: ...

...
Adrian Schröter wrote on 16/01/2015 11:39:21: ...

...
On Freitag, 16. Januar 2015, 11:28:29 wrote vetter@physik.uni-wuerzburg.de: > Adrian Schröter wrote on 16/01/2015 11:05:22: > > On Freitag, 16. Januar 2015, 10:58:26 wrote > vetter@physik.uni-wuerzburg.de: [deleted intro] Is there some variable(s) containing the path? Would have to contain

Adrian Schröter wrote on 20/01/2015 08:36:44: the

...
...
project and repository part of the path.

we need to set it inside of SUSE:SLE-11:SP3:Update security repo

...
...
...
But I have to admit that I am not really keen on that. Can't you

just

...
require "openssl-devel" in any case?

depending on the repo config, you either get openssl v0 or v1...

The SLE11-Security-Module is a addon for SLE11 that brings openssl v1 in addition to openssl v0 from SLE11. So both are available and the openssl-devel is v0. At least it was, when I tried after SLE11-Security-Module was available in OBS. Maybe it's not worth

Adrian Schröter wrote on 20/01/2015 09:50:58: then. thinking

...
The openssl1-devel package is also providing openssl-devel.

So when you use the security repo, you should get v1 and not v0 with the same requirement (that was also the reason for a second repo, to give packagers an easy choice which one to use)

...
about it, since SLE12 is available with openssl v1 only.

My "knowledge" about how to use it in OBS stems from here (the FAQ

part):

...
...
https://www.suse.com/communities/conversations/introducing-the- suse-linux-enterprise-11-security-module/

Hm, I branched it, removed the extra-spec, used BuildRequires openssl-devel and now it is in this state: unresolvable: have choice for openssl-devel: libopenssl1-devel libopenssl-devel

okay, I solved that via a generic prefer in the update project. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

vetter＠physik.uni-wuerzburg.de

11:02

Adrian Schröter wrote on 20/01/2015 10:48:04:

...

On Dienstag, 20. Januar 2015, 10:21:40 wrote vetter@physik.uni-wuerzburg.de:

...
Adrian Schröter wrote on 20/01/2015 09:50:58:

...
On Dienstag, 20. Januar 2015, 09:47:37 wrote vetter@physik.uni-wuerzburg.de:

...
...
On Montag, 19. Januar 2015, 09:45:18 wrote vetter@physik.uni-wuerzburg.de: ...

...
Adrian Schröter wrote on 16/01/2015 11:39:21: ... > On Freitag, 16. Januar 2015, 11:28:29 wrote vetter@physik.uni-wuerzburg.de: > > Adrian Schröter wrote on 16/01/2015 11:05:22: > > > On Freitag, 16. Januar 2015, 10:58:26 wrote > > vetter@physik.uni-wuerzburg.de: [deleted intro] Is there some variable(s) containing the path? Would have to contain

Adrian Schröter wrote on 20/01/2015 08:36:44: the

...
...
project and repository part of the path.

we need to set it inside of SUSE:SLE-11:SP3:Update security repo

...

...
then.

...
...
...
But I have to admit that I am not really keen on that. Can't you

...

...
...
...
...
require "openssl-devel" in any case?

depending on the repo config, you either get openssl v0 or v1...

The SLE11-Security-Module is a addon for SLE11 that brings openssl v1 in addition to openssl v0 from SLE11. So both are available and the openssl-devel is v0. At least it was, when I tried after SLE11-Security-Module was available in OBS. Maybe it's not worth

just thinking

...
The openssl1-devel package is also providing openssl-devel.

So when you use the security repo, you should get v1 and not v0 with

the

...
same requirement (that was also the reason for a second repo, to give packagers an easy choice which one to use)

...
about it, since SLE12 is available with openssl v1 only.

My "knowledge" about how to use it in OBS stems from here (the FAQ

...

...
part):

...
...
https://www.suse.com/communities/conversations/introducing-the- suse-linux-enterprise-11-security-module/

Hm, I branched it, removed the extra-spec, used BuildRequires openssl-devel and now it is in this state: unresolvable: have choice for openssl-devel: libopenssl1-devel libopenssl-devel

okay, I solved that via a generic prefer in the update project.

Great :) Thanks a lot! Andreas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

3383

Age (days ago)

3387

Last active (days ago)

List overview

Download

10 comments

2 participants

participants (2)

Adrian Schröter
vetter＠physik.uni-wuerzburg.de

[opensuse-buildservice] osc copypac excludes repos?

tags

participants (2)