Bug 16852 - libsolv not built with "-DENABLE_COMPLEX_DEPS=1" to enable support for RPM 4.13 rich deps
Summary: libsolv not built with "-DENABLE_COMPLEX_DEPS=1" to enable support for RPM 4....
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-29 15:55 CEST by Neal Gompa
Modified: 2015-09-29 20:27 CEST (History)
1 user (show)

See Also:
Source RPM: libsolv-0.6.13-0.20150925.2.mga6.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Neal Gompa 2015-09-29 15:55:35 CEST 
Description of problem:
Cauldron has RPM 4.13.0 (well, a release candidate of it), which has support for the new rich dependency logic. I do not know if we are using rich dependencies yet in Cauldron, but it would be great if libsolv in Cauldron was built to support it so that it will work with libhif, DNF, or other things that use libsolv.

Version-Release number of selected component (if applicable):
libsolv-0.6.13-0.20150925.2.mga6.src.rpm

Suggested solution:
Simply add "-DENABLE_COMPLEX_DEPS=1" to the build flags passed in at %cmake in the %build step.

Reproducible: 

Steps to Reproduce:
Neal Gompa 2015-09-29 15:55:54 CEST

CC: (none) => thierry.vignaud

Comment 1 Thierry Vignaud 2015-09-29 15:57:31 CEST 
URPM has no support for them for now
Thierry Vignaud 2015-09-29 16:13:39 CEST

Assignee: bugsquad => thierry.vignaud

Comment 2 Neal Gompa 2015-09-29 17:06:29 CEST 
So then, I suppose we don't want to enable it in libsolv, since we can't use it with the default depsolver (URPM)?

Technically, as long as we're not actually *using* the feature in our system packages at this time, there's no reason it couldn't be enabled. That would give us an opportunity to try out the feature outside of system repositories.
Comment 3 Thierry Vignaud 2015-09-29 20:27:12 CEST 
Fixed

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.