Ask Your Question

Hudson Pre-Release: 401 HTTP error when attempting kforge pull

asked 2012-02-20 04:26:15 -0500

paepcke gravatar image

updated 2012-02-22 07:22:18 -0500

hsu gravatar image

I am trying to run a Hudson pre-install on the 'gestures' stack. Hudson's console output is at

The salient part seems to be this HTTP 401 error that prevents Hudson from pulling the stack out of kforge into a stack overlay:

------------------  Begin Excerpt --------------------------
Install the stacks to test from source.
Failed to execute 'rosinstall --rosdep-yes stack_overlay /opt/ros/unstable stack_overlay.rosinstall'
Initialized empty Git repository in /tmp/install_dir/stack_overlay/gestures/.git/
rosinstall operating on /tmp/install_dir/stack_overlay from specifications in rosinstall files  /opt/ros/unstable,         stack_overlay.rosinstall
Installing master to /tmp/install_dir/stack_overlay/gestures

error: The requested URL returned error: 401 while accessing

fatal: HTTP request failed
ERROR: Failed to install tree '/tmp/install_dir/stack_overlay/gestures'
 Checkout of version master into /tmp/install_dir/stack_overlay/gestures failed.
------------ End Excerpt -------------

401 is 'user authorization required'. Do I need to open the kforge project somehow?



edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2012-02-20 05:38:33 -0500

fergs gravatar image

The default behavior for Kforge is for a project to be private. You need to add the user "Visitor" as a "Friend"-level user for the project repositories to be publicly accessible.

edit flag offensive delete link more


Raised Visitor role from 'Visitor' to 'Friend.' Error has changed: Salient:Host key verification failed. fatal: The remote end hung up unexpectedlyClone of 'ssh://' into s

paepcke gravatar image paepcke  ( 2012-02-22 04:47:35 -0500 )edit

You need to set the checkout to pull from the https url not the ssh url.

tfoote gravatar image tfoote  ( 2012-02-22 15:48:06 -0500 )edit

Did set it to https for the stack (see original msg). The pkgs are git submodules. Guess stack is pulled w/ https, then submodules are attempted via ssh. As you say. that can't work. Will see how to control that.

paepcke gravatar image paepcke  ( 2012-02-22 17:53:16 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2012-02-20 04:26:15 -0500

Seen: 364 times

Last updated: Feb 22 '12