Wolfgang Rosenauer writes:

misleading subject but I'm currently facing something unexpected.

I'm building a project against openSUSE:Evergreen:11.4 but it gets the "wrong" openssl version. I need to build against the openssl currently there: # osc ls openSUSE:Evergreen:11.4 openssl ... openssl-1.0.1k.tar.gz ...

but the project installs an older one (seems like something also only in openSUSE:Evergreen:11.4 but still older.

There are several openssl packages in this project, and the one use for building comes from the openssl.289 package, being the lexicographically latest. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Wolfgang Rosenauer writes:

wolfi@Hygiea:~> osc ls openSUSE:Evergreen:11.4 openssl

That package has no binaries, so it isn't even considered. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Am 17.05.2015 um 14:58 schrieb Marcus Meissner:

On Sun, May 17, 2015 at 10:45:24AM +0200, Wolfgang Rosenauer wrote:

...

Hi,

misleading subject but I'm currently facing something unexpected.

I'm building a project against openSUSE:Evergreen:11.4 but it gets the "wrong" openssl version. I need to build against the openssl currently there: # osc ls openSUSE:Evergreen:11.4 openssl ... openssl-1.0.1k.tar.gz ...

but the project installs an older one (seems like something also only in openSUSE:Evergreen:11.4 but still older. Is there a cache issue or has it to do with the latest patch being "optional"?

It should pick up the new one.

Which project?

home:wrosenauer:messaging/resiprocate Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Am 17.05.2015 um 19:05 schrieb Andreas Schwab:

Wolfgang Rosenauer writes:

...

As this is an update project fed by a maintenance project

That doesn't change the way the _repository is populated.

ok, in that case can you please be a bit more verbose where the issue is actually? Can I do something about it or should I file a bug on OBS or do I need to ask someone to do something whatever? I cannot follow. Sorry, Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Am 17.05.2015 um 19:25 schrieb Andreas Schwab:

Wolfgang Rosenauer writes:

...

ok, in that case can you please be a bit more verbose where the issue is actually?

There is no issue, it's just the way it works.

aehm, no. When I build against a certain (update)project I want to get the latest (read highest version number) packages in my build environment. I don't think this is a wrong expectation. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Sonntag, 17. Mai 2015, 19:33:57 wrote Wolfgang Rosenauer:

Am 17.05.2015 um 19:25 schrieb Andreas Schwab:

...

Wolfgang Rosenauer writes:

...

ok, in that case can you please be a bit more verbose where the issue is actually?

There is no issue, it's just the way it works.

aehm, no. When I build against a certain (update)project I want to get the latest (read highest version number) packages in my build environment. I don't think this is a wrong expectation.

imagine you have two repos providing the same package, but with different config settings. Depending on the build numbers you would get sometimes the package with feature X and sometimes not. It is a nightmare to debug sideeffects of that... However, in the maintenance release projects always the package from the highest incident number should be taken. This is the case from what I see in your example, version openssl-1.0.0m-18.53.1.x86_64.rpm from openSUSE:Evergreen:11.4 openssl.289 is taken when using openSUSE:Evergreen:11.4 standard x86_64 repo is used. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, 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