[ros-users] Error installing ROS in Debian

[Tully Foote]

Hi Gorka,

The ROS os detection uses "lsb_release -si" and "lsb_release -sc" when
trying to detect Debian.  Can you send what the results are of those
commands?  It's expecting "Debian"  for the issue.

Please note that Debian is only partially tested.  You will likely need to
add a few rosdep rules to rosdep.yaml files.  There is documentation at
http://www.ros.org/wiki/rosdep  and the tutorial
http://www.ros.org/wiki/rosdep/Tutorials/Add%20new%20OS%20to%20rosdep.yaml
tells
you how to extend any rosdep for a particular distro. If you do end up
needing to extend rosdep.yaml files in stacks.  Please submit back patches
to the stacks you have to patch so others don't have to do the same thing (
there are tracs for each of the projects at https://code.ros.org)

Tully

On Fri, May 28, 2010 at 12:49 AM, Gorka Azcune <gazcune at fatronik.com> wrote:

>  Hi all,
>
>
>
> We are trying to install ROS in a Debian distro from svn following the
> Ubuntu/Linux instructions provided in the web-site. We have a squeeze/sid
> version of Debian, which can be seen in /etc/debian_version. However, we get
> a weird error:
>
>
>
> [ rosmake ] rosdep install failed: Could not detect OS, tried
> ['uninitialized from ROS_OS_OVERRIDE=name:version', 'rosdep_test_os',
> 'debian', 'ubuntu', 'ubuntu', 'fedora', 'rhel', 'arch', 'macports',
> 'gentoo', 'cygwin']
>
> Traceback (most recent call last):
>
>   File "./rosinstall", line 326, in <module>
>
>     sys.exit(rosinstall_main(sys.argv) or 0)
>
>   File "./rosinstall", line 319, in rosinstall_main
>
>     subprocess.check_call("source %s && rosmake rostest --rosdep-install" %
> (os.path.join(options.path, 'setup.sh')), shell=True,
> executable='/bin/bash')
>
>   File "/usr/lib/python2.5/subprocess.py", line 462, in check_call
>
>     raise CalledProcessError(retcode, cmd)
>
> subprocess.CalledProcessError: Command 'source
> /home/treaccio/tmp/ros/setup.sh && rosmake rostest --rosdep-install'
> returned non-zero exit status 255
>
>
>
> Looking at the error we also tried to assign
> ROS_OS_OVERRIDE=debian:squeeze/sid manually, using the export command,
> before running rosinstall. But this also output an error:
>
>
>
> Using environment variable ROS_OS_OVERRIDE=name:version
>
> [ rosmake ] Detected rosout not built, adding it to the build
>
> [ rosmake ] Packages requested are: ['rostest', 'rosout']
>
> [ rosmake ] Logging to directory
>
> [ rosmake ] /home/treaccio/.ros/rosmake/rosmake_output-20100528-094544
>
> [ rosmake ] Expanded args ['rostest', 'rosout'] to:
>
> ['rostest', 'rosout']
>
> [ rosmake ] Generating Install Script using rosdep then executing. This may
> take a minute, you will be prompted for permissions. . .
>
> Using environment variable ROS_OS_OVERRIDE=name:version
>
> Traceback (most recent call last):
>
>   File "/home/treaccio/tmp/ros/ros/bin/rosmake", line 59, in <module>
>
>     if not rma.main():
>
>   File "/home/treaccio/tmp/ros/ros/tools/rosmake/src/rosmake/rosmake.py",
> line 649, in main
>
>     self.rosdep_install_result = self.install_rosdeps(buildable_packages,
> options.rosdep_yes)
>
>   File "/home/treaccio/tmp/ros/ros/tools/rosmake/src/rosmake/rosmake.py",
> line 125, in install_rosdeps
>
>     r.install(include_duplicates=False, default_yes=default_yes);
>
>   File "/home/treaccio/tmp/ros/ros/tools/rosdep/src/rosdep/core.py", line
> 366, in install
>
>     script = self.generate_script(include_duplicates, default_yes)
>
>   File "/home/treaccio/tmp/ros/ros/tools/rosdep/src/rosdep/core.py", line
> 331, in generate_script
>
>     self.osi.get_os().strip_detected_packages(native_packages)
>
> AttributeError: Override instance has no attribute
> 'strip_detected_packages'
>
> Traceback (most recent call last):
>
>   File "./rosinstall", line 326, in <module>
>
>     sys.exit(rosinstall_main(sys.argv) or 0)
>
>   File "./rosinstall", line 319, in rosinstall_main
>
>     subprocess.check_call("source %s && rosmake rostest --rosdep-install" %
> (os.path.join(options.path, 'setup.sh')), shell=True,
> executable='/bin/bash')
>
>   File "/usr/lib/python2.5/subprocess.py", line 462, in check_call
>
>     raise CalledProcessError(retcode, cmd)
>
> subprocess.CalledProcessError: Command 'source
> /home/treaccio/tmp/ros/setup.sh && rosmake rostest --rosdep-install'
> returned non-zero exit status 1
>
>
>
> We realized that ROS uses its own tools for Python to detect the underlying
> OS. For some reasons, that tool doesn’t work for us. Are we missing
> anything? Is there any special issue we need to take into account for Debian
> installation?
>
>
>
> Thanks in advance!
>
>
>
> *______________________________*
>
> *Gorka Azkune Galparsoro*
>
> Kontrol eta IKT Saila
>
> Departamento de Control y TIC
>
> *Control and ICT Department *
>
>
>
> *FATRONIK** *
> Mikeletegi Pasealekua, 7 - . Teknologi Parkea
> E-20.009 Donostia (Gipuzkoa)-Spain
>
> *Telf*: (+34) 943 005500
> *Fax*: (+34) 943 005511
> *e-mail* : gazcune at fatronik.com
> *web *: www.fatronik.com
>
>
>
>
>
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>


-- 
Tully Foote
Systems Engineer
Willow Garage, Inc.
tfoote at willowgarage.com
(650) 475-2827
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20100528/1bf4ae13/attachment-0003.html>