Mailinglist Archive: opensuse-buildservice (170 mails)

< Previous Next >
Re: [opensuse-buildservice] Re: problem with package always in 'unresolvable'
On Wed, Jul 10, 2013 at 3:49 AM, Jan Engelhardt <jengelh@xxxxxxx> wrote:
On Wednesday 2013-07-10 10:44, Andreas Schwab wrote:

Jan Engelhardt <jengelh@xxxxxxx> writes:

Well, it is a candidate for the build-time solver, but not for
the runtime solver.

Is it? Apparently both packages still provide PACKAGE_FOO, and
Substitute has no influence on that.

In this case, the problem is very similar to the one described by the
documentation here:
http://en.opensuse.org/openSUSE:Build_Service_prjconf#Substitute

I have a package that provides the same functionality as another
(right down to the point that they would conflict on the filesystem).
I don't ever want software to use one of them, always the other. I
have a project hierarchy that looks like this:

upstream -> projectA- -> projectB -> projectC

Now. The 'substitute' part is part of the buildconf for projectA which
supplies just a few essential packages.
projectB supplies the replacement package with "Conflicts:
oldpackagename". I also experimented with adding "Provides:
oldpackagename". The replacement package builds fine and all of the
other packages that have a BuildRequires: oldpackagename or
BuildRequires: newpackagename in projectB also build fine using
"newpackage".
However, packages in projectC fail to even start building due to the
aforementioned "choice" between oldpackagename and newpackagename.

I guess I'm confused as to why everything in projectB is groovy, but
things in projectC are wonky.

I've commented out the Substitute line and have added a Prefers to the
buildconf of projectA. Let's see how it goes.
Maybe I should use both?

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

< Previous Next >