On 22/02/15 12:09, gil wrote:

Il 22/02/2015 11:58, Alec Leamas ha scritto:

...

Greetings, gurus!

So, I have have successfully built two dependencies (thanks for all help!), and now going for the third which requires the the first two. The build is OK, but rpmbuild crashes with a simple message:

Exception: Following dependencies were not resolved and requires cannot be generated. Either remove the dependency from pom.xml or add proper packages to BuildRequires: com.hifiremote:DecodeIrCaller:1314 required by org.harctoolbox:IrpMaster

But, things are not simple (?):

$ rpm -q --whatprovides 'mvn(com.hifiremote:DecodeIrCaller)' DecodeIrCaller-0.1.1-1.fc21.noarch

I. e., rpmbuild does not find the installed maven-generated package DecodeIrCaller even though it provides the proper things(?) The package looks OK to my silly eyes:

$ rpm -ql DecodeIrCaller /usr/share/java/DecodeIrCaller.jar /usr/share/maven-metadata/DecodeIrCaller.xml /usr/share/maven-poms/DecodeIrCaller /usr/share/maven-poms/DecodeIrCaller/DecodeIrCaller.pom

Spec of built package: http://paste.fedoraproject.org/188869/60250414 Spec of DecodeIrCaller: http://ur1.ca/js0d7

Any hint?

remove this in DecodeIrCaller.spec mv %{buildroot}/usr/lib/java/%{name} %{buildroot}%{_javadir} jni should live and stay in _jnidir aka /usr/lib/java

Thanks, that was actually a good catch. Still, the result after fixing is the same.

Cheers!

--alec

On 22/02/15 13:00, gil wrote:

Il 22/02/2015 12:46, Alec Leamas ha scritto:

...

On 22/02/15 12:09, gil wrote:

...

...

...

remove this in DecodeIrCaller.spec mv %{buildroot}/usr/lib/java/%{name} %{buildroot}%{_javadir} jni should live and stay in _jnidir aka /usr/lib/java

Thanks, that was actually a good catch. Still, the result after fixing is the same.

Cheers!

maybe there is something of wrong in your pom file

I wouldn't bet against that. for sure...

DecodeIrCaller pom: http://ur1.ca/js0qe IrpMaster (crashing build) pom: http://ur1.ca/js0qj

--alec

On 2015-02-23 13:17, Alec Leamas wrote:

On 22/02/15 11:58, Alec Leamas wrote:

...

Greetings, gurus!

So, I have have successfully built two dependencies (thanks for all help!), and now going for the third which requires the the first two. The build is OK, but rpmbuild crashes.

So, after a debugging session deep down in the python libraries the bug is simple: when I install the DecodeIrCaller package, it sets the metadata file to 600, so rpmbuild can't read it. It would have been easy if it wasn't that the python packages have mis-configured logging so there is no reasonable error message.

The python logging is a plain bug I will file. But the mystery is why my DecodeIrCaller package installs the metadata for this very package as a 600 file.

The relevant pieces:

The spec: http://ur1.ca/js840 The pom: http://ur1.ca/js842

The problem: $ ls -l /usr/share/maven-metadata/DecodeIrCaller.xml -rw-------. 1 root root 938 Feb 23 13:02 /usr/share/maven-metadata/DecodeIrCaller.xml

Has anyone a clue?

You shouldn't specify metadata files (and poms and jars) manually, but use %files -f .mfiles

Then the permissions are specified by the tooling and the problem should go away. If not, please fill a bug.

Michael Simacek

Cheers!

--alec

java-devel mailing list java-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/java-devel