[opensuse-buildservice] problem with package always in 'unresolvable'
I'm running an instance of OBS 2.3 I have a package that always says 'unresolvable', and when I use osc to ask for buildinfo, it lists a half-dozen packages like this: <error>unresolvable: have choice for PACKAGE_FOO needed by PACKAGE_BAR: PACKAGE_DEP1 PACKAGE_DEP2, have choice for .... Now, the problem is that PACKAGE_FOO says it built successfully, and I'm using in a parent project's buildconf: Substitute: PACKAGE_DEP2 PACKAGE_DEP1 because I *always* want to use PACKAGE_DEP2. I don't understand what's going on here. In summary: project 1, package A builds fine. project 2 (which uses project 1 as a build repo), package B refuses to build, the problem listed is a problem with package A. -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Jon Nelson <jnelson-suse@jamponi.net> writes:
<error>unresolvable: have choice for PACKAGE_FOO needed by PACKAGE_BAR: PACKAGE_DEP1 PACKAGE_DEP2, have choice for ....
Now, the problem is that PACKAGE_FOO says it built successfully, and I'm using in a parent project's buildconf:
Substitute: PACKAGE_DEP2 PACKAGE_DEP1
because I *always* want to use PACKAGE_DEP2.
Then you should use Prefer. Just because you change PACKAGE_DEP2 to PACKAGE_DEP1 doesn't change the fact that PACKAGE_DEP2 is still a candidate for the solver. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "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
On Wednesday 2013-07-10 09:00, Andreas Schwab wrote:
<error>unresolvable: have choice for PACKAGE_FOO needed by PACKAGE_BAR: PACKAGE_DEP1 PACKAGE_DEP2, have choice for ....
Now, the problem is that PACKAGE_FOO says it built successfully, and I'm using in a parent project's buildconf:
Substitute: PACKAGE_DEP2 PACKAGE_DEP1
because I *always* want to use PACKAGE_DEP2.
Then you should use Prefer. Just because you change PACKAGE_DEP2 to PACKAGE_DEP1 doesn't change the fact that PACKAGE_DEP2 is still a candidate for the solver.
Well, it is a candidate for the build-time solver, but not for the runtime solver. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Jan Engelhardt <jengelh@inai.de> 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. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "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
On Wednesday 2013-07-10 10:44, Andreas Schwab wrote:
Jan Engelhardt <jengelh@inai.de> 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.
What I mean is: given the RPMs are produced and available to an openSUSE zypper, it will, because pkg2 obsoletes pkg1, not normally offer pkg1 for installation. This is different in the build system, as you just described. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wed, Jul 10, 2013 at 3:49 AM, Jan Engelhardt <jengelh@inai.de> wrote:
On Wednesday 2013-07-10 10:44, Andreas Schwab wrote:
Jan Engelhardt <jengelh@inai.de> 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@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Andreas Schwab -
Jan Engelhardt -
Jon Nelson