Strangely, when I ran it just down, I actually got the prompt for a
password.

On a different note, rosdep install seems to be suppressing output from
macports, which is somewhat disconcerting to me. I like to be notified when
things are being installed on my computer, just so I can ctrl+c if I have
any objections =P

{{{
geometry rubinet$ rosdep install camera1394
executing this script:
 set -o errexit
#Packages
sudo port install libdc1394
# No rule for glut

Password:
geometry rubinet$
}}}

On Fri, Jan 14, 2011 at 12:06 PM, Tully Foote <tfoote@willowgarage.com>wrote:

>
>
> On Fri, Jan 14, 2011 at 9:20 AM, Nicholas Butko <nbutko@ucsd.edu> wrote:
>
>> Tully,
>>
>> I tried that, and rosdep seems to hang. I get the following output:
>>
>> {{{
>> dyn137-110-111-179:geometry rubinet$ rosdep install camera1394
>> executing this script:
>>  set -o errexit
>> #Packages
>> sudo port install libdc1394
>> # No rule for glut
>>
>> }}}
>>
>> I'd be interested in seeing where this hangs.  If you could show the
> relevant part of "ps auxf" or equivalent on mac.  It's quite possible that
> it is waiting for your password but the prompt was accidentally suppressed.
> I've seen that before and there are reports of that sort of problem on
> SUSE.  https://code.ros.org/trac/ros/ticket/3242
>
>
>
>>
>> And then nothing happens. I am not asked for my password for the sudo
>> command. Note that "sudo rosdep install" also fails, I think because rosbash
>> is not set up for su:
>>
>> {{{
>> dyn137-110-111-179:geometry rubinet$ sudo rosdep install camera1394
>> Traceback (most recent call last):
>>   File "/Users/rubinet/ros/cturtle/ros/bin/rosdep", line 34, in <module>
>>     from ros import rosdep
>> ImportError: No module named ros
>> dyn137-110-111-179:geometry rubinet$
>> }}}
>>
>> I would expect this.  And sudo is not necessary at that level as the
> script calls sudo inside it.
>
> Tully
>
>> --Nick
>>
>>
>>
>> On Fri, Jan 14, 2011 at 9:09 AM, Tully Foote <tfoote@willowgarage.com>wrote:
>>
>>> Nick,
>>>
>>> Can you make sure to put a line like this in the geometry rosdep.yaml:
>>>
>>> {{{
>>> glut:
>>>   ...
>>>   macports: |
>>>     # No rule for glut
>>> }}}
>>>
>>> Rosdep requires a multiline expression to interpret it as a script.
>>>
>>> bullet, a dependency of camera1394 and uses glut.
>>>
>>> Tully
>>>
>>>
>>> On Fri, Jan 14, 2011 at 8:41 AM, Nicholas Butko <nbutko@ucsd.edu> wrote:
>>>
>>>> Jack, that patch looks exactly right. However, I am getting strange
>>>> behavior.
>>>>
>>>> When I *haven't* applied the patch, this is my output:
>>>>
>>>> dyn137-110-111-179:camera1394 rubinet$ rosdep install camera1394
>>>> Failed to find rosdep glut for package camera1394 on OS:macports
>>>> version:macports
>>>> Failed to find rosdep libdc1394-dev for package camera1394 on
>>>> OS:macports version:macports
>>>> ERROR: ABORTING: Rosdeps [u'glut', u'libdc1394-dev'] could not be
>>>> resolved
>>>>
>>>> When I *have* applied the patch, this is my output:
>>>>
>>>> dyn137-110-111-179:camera1394 rubinet$ rosdep install camera1394
>>>> Failed to find rosdep glut for package camera1394 on OS:macports
>>>> version:macports
>>>> ERROR: ABORTING: Rosdeps [u'glut'] could not be resolved
>>>>
>>>> I tried to fix this by adding an empty macports entry (macports: |) to
>>>> everywhere that rosdep.yaml has "glut". From my investigation, this only
>>>> seems to happen in the geometry package. Yet the problem persists.
>>>>
>>>> Another strange thing is that I get the same behavior *regardless of
>>>> whether libdc1394 is installed* (It is easy to uninstall and reinstall).
>>>>
>>>> --Nick
>>>>
>>>>
>>>> On Fri, Jan 14, 2011 at 8:00 AM, Jack O'Quin <jack.oquin@gmail.com>wrote:
>>>>
>>>>> On Thu, Jan 13, 2011 at 3:21 PM, Nicholas Butko <nbutko@ucsd.edu>
>>>>> wrote:
>>>>> > I may be able to try something out for you. I'll take a look later
>>>>> today.
>>>>>
>>>>> Nick,
>>>>>
>>>>> Would you try adding this to the rosdep.yaml in the camera_drivers
>>>>> stack? Then, see if "rosdep install camera1394" does something
>>>>> sensible? The patch should work with both cturtle and unstable.
>>>>>
>>>>> Can someone who has a Mac *without* libdc1394 installed run the same
>>>>> test and report whether the library installs correctly? (You don't
>>>>> need a camera to run that test.)
>>>>>
>>>>> Index: rosdep.yaml
>>>>> ===================================================================
>>>>> --- rosdep.yaml (revision 35214)
>>>>> +++ rosdep.yaml (working copy)
>>>>> @@ -12,6 +12,7 @@
>>>>>   ubuntu: libdc1394-22-dev
>>>>>   arch: libdc1394
>>>>>   fedora: libdc1394-devel
>>>>> +  macports: libdc1394
>>>>>
>>>>>  gforth:
>>>>>   ubuntu: gforth
>>>>> --
>>>>>  joq
>>>>> _______________________________________________
>>>>> ros-users mailing list
>>>>> ros-users@code.ros.org
>>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> ros-users mailing list
>>>> ros-users@code.ros.org
>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>>
>>>>
>>>
>>>
>>> --
>>> Tully Foote
>>> Systems Engineer
>>> Willow Garage, Inc.
>>> tfoote@willowgarage.com
>>> (650) 475-2827
>>>
>>> _______________________________________________
>>> ros-users mailing list
>>> ros-users@code.ros.org
>>> https://code.ros.org/mailman/listinfo/ros-users
>>>
>>>
>>
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>>
>
>
> --
> Tully Foote
> Systems Engineer
> Willow Garage, Inc.
> tfoote@willowgarage.com
> (650) 475-2827
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>