On Wed, 2013-08-28 at 16:12 +0200, Marcela Mašláňová wrote:

From quick glance I guess you need to run build section with enabled collection. But the problem will be elsewhere. Let's ask Python guys.

Would enabling the SCL be enough to set up the python paths correctly? I did try this as per one of the specs in the python SCL[1], but that didn't seem to work. I need to have the python stuff both in /opt and the system available for this build from the looks of it, since the BuildRequires are still installed in the normal, non-SCL buildroot (I think?)

Hey Ankur, tl;dr: Not an SCL problem methinks, you are missing git in BuildRequires (and more). :) Base your .spec on apps.fedoraproject.org/packages/catkin/sources/spec/ and you should be fine.

From: """ Exception occurred: File "/usr/lib64/python2.7/subprocess.py", line 1308, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory The full traceback has been saved in /tmp/sphinx-err-m4tyUh.log, if you want to report the issue to the developers. """

Looking at the /tmp/sphinx-err-m4tyUh.log you can see that the exception occurred in catkin/doc/conf.py:52, there you'll find:

""" gitcmd = 'git log -n1 --pretty=format:%cD'.split() lastmod = subprocess.Popen(gitcmd, stdout=subprocess.PIPE).communicate()[0] """

In other words, it's trying to execute a git command when building the docs. Just adding git to BuildRequires, however, was not enough, so I just copy-pasted all the BuildRequires from the above mentioned .spec, modified the %install section, et voilà...

Matt

----- Original Message ----- From: "Marcela Mašláňová" mmaslano@redhat.com To: softwarecollections@lists.fedorahosted.org Cc: "Robert Kuska" rkuska@redhat.com, "Matej Stuchlik" mstuchli@redhat.com Sent: Wednesday, August 28, 2013 4:12:19 PM Subject: Re: Help building catkin for the ros-groovy SCL

On 08/28/2013 01:29 PM, Ankur Sinha wrote:

Hi,

I'm trying to build a SCL for the "Groovy" version of ROS[1]. I've built the meta package already (correctly I hope)[2]. I'm now building the first package "catkin". Here's the spec[3]. It doesn't build in mock though[build log:4]. It fails to locate some python libraries. Could someone please check if I'm doing something wrong here? The mock config that I use is here[5].

(This is my first experience with SCLs.)

[1] http://www.ros.org/wiki/groovy [2] http://ankursinha.fedorapeople.org/fedora-ros-groovy/SPECS/ros-groovy.spec [3] http://ankursinha.fedorapeople.org/fedora-ros-groovy/SPECS/ros-groovy-catkin... [4] http://paste.fedoraproject.org/35392/37768890/ [5] http://ankursinha.fedorapeople.org/fedora-ros-groovy/OTHER/fedora-19-ros-gro...

---

softwarecollections mailing list softwarecollections@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/softwarecollections

From quick glance I guess you need to run build section with enabled collection. But the problem will be elsewhere. Let's ask Python guys.

Marcela

On Thu, 2013-08-29 at 06:13 -0400, Matej Stuchlik wrote:

Hey Ankur,

Hi Matt,

tl;dr: Not an SCL problem methinks, you are missing git in BuildRequires (and more). :) Base your .spec on apps.fedoraproject.org/packages/catkin/sources/spec/ and you should be fine.

From: """ Exception occurred: File "/usr/lib64/python2.7/subprocess.py", line 1308, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory The full traceback has been saved in /tmp/sphinx-err-m4tyUh.log, if you want to report the issue to the developers. """

Looking at the /tmp/sphinx-err-m4tyUh.log you can see that the exception occurred in catkin/doc/conf.py:52, there you'll find:

""" gitcmd = 'git log -n1 --pretty=format:%cD'.split() lastmod = subprocess.Popen(gitcmd, stdout=subprocess.PIPE).communicate()[0] """

In other words, it's trying to execute a git command when building the docs. Just adding git to BuildRequires, however, was not enough, so I just copy-pasted all the BuildRequires from the above mentioned .spec, modified the % install section, et voilà...

Ah! Yikes! I didn't check that log file. My bad. Thanks for clearing it up! I'll go build it and post if I run into any other SCL related errors.