ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
1

Using rosmake offline

asked 2012-04-16 10:42:04 -0500

Willy Lambert gravatar image

updated 2012-04-17 04:04:11 -0500

Hi

I am on electric in a Debian squeeze linux. everything is working perfectly for now when I am online (I mean with an internet connection).

But as soos as I loose the web connection, rosmake don't want to work anymore with this :

ard@ard-host(9.2):~$ rosmake arp_master
[ rosmake ] Packages requested are: ['arp_master']                              
[ rosmake ] Logging to directory/opt/ros/rosmake/rosmake_output-20120416-223036 
[ rosmake ] Expanded args ['arp_master'] to:
['arp_master']                     
[ rosmake ] Checking rosdeps compliance for packages arp_master.  This may take a few seconds.
Traceback (most recent call last):
  File "/opt/ros/ros/bin/rosmake", line 65, in <module>
    if rma.main():
  File "/opt/ros/ros/tools/rosmake/src/rosmake/engine.py", line 865, in main
    self.rosdep_check_result = self.check_rosdep(buildable_packages)
  File "/opt/ros/ros/tools/rosmake/src/rosmake/engine.py", line 296, in check_rosdep
    failed_rosdeps = r.check()
  File "/opt/ros/ros/tools/rosdep/src/rosdep/core.py", line 449, in check
    if not self.install_rosdep(r, rdlp, default_yes=False, execute=False, display=display):
  File "/opt/ros/ros/tools/rosdep/src/rosdep/core.py", line 527, in install_rosdep
    my_installer = installer(rosdep_dict[mode])
  File "/opt/ros/ros/tools/rosdep/src/rosdep/installers.py", line 130, in __init__
    raise rosdep.core.RosdepException("Failed to load a rdmanifest from %s, and no alternate URI given"%(self.url))
RosdepException: Failed to load a rdmanifest from https://kforge.ros.org/rosrelease/viewvc/sourcedeps/eigen/eigen-3.0.1-1.rdmanifest, and no alternate URI given
Traceback (most recent call last):
  File "/opt/ros/ros/bin/rosmake", line 65, in <module>
    if rma.main():
  File "/opt/ros/ros/tools/rosmake/src/rosmake/engine.py", line 865, in main
    self.rosdep_check_result = self.check_rosdep(buildable_packages)
  File "/opt/ros/ros/tools/rosmake/src/rosmake/engine.py", line 296, in check_rosdep
    failed_rosdeps = r.check()
  File "/opt/ros/ros/tools/rosdep/src/rosdep/core.py", line 449, in check
    if not self.install_rosdep(r, rdlp, default_yes=False, execute=False, display=display):
  File "/opt/ros/ros/tools/rosdep/src/rosdep/core.py", line 527, in install_rosdep
    my_installer = installer(rosdep_dict[mode])
  File "/opt/ros/ros/tools/rosdep/src/rosdep/installers.py", line 130, in __init__
    raise rosdep.core.RosdepException("Failed to load a rdmanifest from %s, and no alternate URI given"%(self.url))
rosdep.core.RosdepException: Failed to load a rdmanifest from https://kforge.ros.org/rosrelease/viewvc/sourcedeps/eigen/eigen-3.0.1-1.rdmanifest, and no alternate URI given

I think this may be due to packages that are trying to getting dependencies online.

Does anyone has the same behavior ? Does anyone now how to go over this ?

UPDATE :

After correcting Cmake logic and manifests, the problem is still here.

What allows me to overcome this problem is not to define the <rosdep name="eigen"> line in my manifest. This is because eigen3 is already installed, but rosdep is always trying to connect to the net to get the last version. Is this a bug of rosdep ?

I can isolate the problem just doing "rosdep install" (so the problem seems to be in rosdep instead of rosmake ... (more)

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2012-04-16 12:47:57 -0500

joq gravatar image

updated 2012-04-17 12:01:56 -0500

It looks like you may be trying to use the old Diamondback eigen package, which downloads and builds the library from source.

Starting with Electric, you should replace <depend eigen> with <rosdep eigen> in your manifest.xml, and make some updates to your CMakeLists.txt. That will use the system version of the eigen library (after the rosdep is installed).

UPDATE: The Debian entry for the eigen rosdep may be broken. Rosdep should detect that eigen is already installed and not try to download it again. What does this say?

rosdep check eigen

UPDATE2: Clearly, the Debian rosdep for eigen is broken. I am opening a Trac ticket to get it fixed. On Fuerte rosdep works differently, but the same problem appears to be present there, too.

edit flag offensive delete link more

Comments

question edited

Willy Lambert gravatar image Willy Lambert  ( 2012-04-17 04:00:28 -0500 )edit

Thanks for the update, it helped us find the problem. Commenting out the &lt;rosdep name="eigen"&gt; seems reasonable for a temporary workaround.

joq gravatar image joq  ( 2012-04-17 12:05:32 -0500 )edit

my pleasure, thanks for your time. I'll do this

Willy Lambert gravatar image Willy Lambert  ( 2012-04-17 12:08:22 -0500 )edit

Question Tools

Stats

Asked: 2012-04-16 10:42:04 -0500

Seen: 668 times

Last updated: Apr 17 '12