Missing provides in packages built on ABF

Why packages built on ABF miss some ‘provides’?

Just an example. I built httpcomponents-core v4.4.6 on ABF then I try so search it in my box (with my personal repo enable):

$ urpmq --provides httpcomponents-core
httpcomponents-core: mvn(org.apache.httpcomponents:httpcore:pom:)[== 4.3.2]
httpcomponents-core: mvn(org.apache.httpcomponents:httpcore-nio:pom:)[== 4.3.2]
httpcomponents-core: mvn(org.apache.httpcomponents:httpcore)[== 4.3.2]
httpcomponents-core: mvn(org.apache.httpcomponents:httpcomponents-core:pom:)[== 4.3.2]
httpcomponents-core: mvn(org.apache.httpcomponents:httpcore-nio)[== 4.3.2]
httpcomponents-core: osgi(org.apache.httpcomponents.httpcore-nio)[== 4.3.2]
httpcomponents-core: osgi(org.apache.httpcomponents.httpcore)[== 4.3.2]
httpcomponents-core: httpcomponents-core[== 4.3.2-3.3:2015.0]
httpcomponents-core: httpcomponents-core[== 4.4.6-1:3001]

As you can see only latest row refers to my package. This is a little boring especially when the package should be used as a dependence of another because it force me to change the ‘BuildRequires’ filed of other packages.

Also it may broke the system when I try to update. In fact if an installed package requires ‘mvn(org.apache.httpcomponents:httpcore)’ it should be removed before update.

Did you already ask to the om-cooker list?

I did not. I did here because I think it may be interesting for all the other ABF users by community. Maybe there is just an option to check in ABF. All I know is it is the same behaviour as rpmbuild on my local machine so other ‘provides’ are generated elsewhere (but not by genhdlist2 I use for my local repo).

Do you think om-cooker list is more suitable for such a question?

Yes. You can also try IRC on irc.freenode.org, channel openmandriva-cooker
However, if you get a valid answer, please, let us know :slight_smile:

After an IRC session the bug has been fixed. :slight_smile:

It was a bug in javapackages-tools and it was related to the omdv build system, not just to ABF.

1 Like

I forgot to mention all java packages must contain the line (usually it is paced at the head of file)

%{?_javapackages_macros:%_javapackages_macros}

in order to activate javapackages macros and auto generate dependencies.