[opensuse-buildservice] supporting different versions of a package in one project
Hi, I'm running into a nasty issue in one of my OBS projects. OBS supports to have the same package in different versions within one project basically. I'm using that since years but now I'm running into a special case which is not supported. So I would consider it a bug but wanted to bring it up here (maybe someone knows about a workaround). I have one package in two versions within one project but now I have two versions of another package where one requires the older version to build and the other requires the newer version to build. So I've specified versioned dependencies in BuildRequires but that is not sufficient. They are actually taken into account but now I get "unresolvable" for the older package as it doesn't find the previous version apparently. So could we support this case in future? And does anybody know a workaround to that? Otherwise I won't be able to release Firefox 5 in the mozilla repository w/o removing all older versions what I don't want to do. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am 21.06.2011 10:57, schrieb Wolfgang Rosenauer:
I have one package in two versions within one project but now I have two versions of another package where one requires the older version to build and the other requires the newer version to build.
So I've specified versioned dependencies in BuildRequires but that is not sufficient. They are actually taken into account but now I get "unresolvable" for the older package as it doesn't find the previous version apparently.
I tried to workaround it by disabling "used for build" for the newer package and retrigger the build of the older dependent package. But it's still unresolved. Now that is a bug for sure I guess? Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Jun 21, 2011 at 01:44:01PM +0200, Wolfgang Rosenauer wrote:
Am 21.06.2011 10:57, schrieb Wolfgang Rosenauer:
I have one package in two versions within one project but now I have two versions of another package where one requires the older version to build and the other requires the newer version to build.
So I've specified versioned dependencies in BuildRequires but that is not sufficient. They are actually taken into account but now I get "unresolvable" for the older package as it doesn't find the previous version apparently.
I tried to workaround it by disabling "used for build" for the newer package and retrigger the build of the older dependent package. But it's still unresolved. Now that is a bug for sure I guess?
What about add a special provides into dependent packages and then reffer them in BuildRequires? Does it help you? Note that you should not combine a provides and a package name as BuildService preffers the package names. Regards Michal Vyskocil
Am Tuesday, 21. June 2011, 10:57:20 schrieb Wolfgang Rosenauer:
Hi,
I'm running into a nasty issue in one of my OBS projects.
OBS supports to have the same package in different versions within one project basically. I'm using that since years but now I'm running into a special case which is not supported. So I would consider it a bug but wanted to bring it up here (maybe someone knows about a workaround).
I have one package in two versions within one project but now I have two versions of another package where one requires the older version to build and the other requires the newer version to build.
That can't work in the same repository right now. You can provide multiple versions of one rpm in the repository, but you can only build against one version in a defined way. You need to create two repos and enable/disable the versions you need there.
So I've specified versioned dependencies in BuildRequires but that is not sufficient. They are actually taken into account but now I get "unresolvable" for the older package as it doesn't find the previous version apparently.
So could we support this case in future? And does anybody know a workaround to that? Otherwise I won't be able to release Firefox 5 in the mozilla repository w/o removing all older versions what I don't want to do.
Wolfgang
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Adrian Schröter -
Michal Vyskocil -
Wolfgang Rosenauer