Does svn repo for 'release' tree have new auth requirement?

asked 2013-08-22 10:54:16 -0600

paepcke
71 ●4 ●7 ●10

I'm trying to release a new version of a previously released stack. I need to change an entry in release/distros/fuerte.rosdistro and distros/groovy.rosdistro to correct a git branch specification.

I UPed the latest 'release' tree from trunk, made the changes, and tried to commit. I think this used to just work, but I haven't done it in while: svn won't let me commit:

svn commit -m "Modified groovy.rosdistro and fuerte.rosdistro to pull different branches from robhum_utils repo." Password for 'default' GNOME keyring: svn: Commit failed (details follow): svn: MKACTIVITY of '/svn/release/!svn/act/bc7f360e-85e6-4d8a-b8da-2df6487a8432': authorization failed: Could not authenticate to server: rejected Basic challenge (https://code.ros.org)

Was there always a pwd/rsa auth, or is this new?

thanks,

Andreas

edit retag flag offensive close merge delete

Comments

Thanks, Tully, I'll try to get past the authentication barrier again, in the old place.

paepcke ( 2013-08-26 04:19:41 -0600 )edit

add a comment

0

answered 2013-08-26 06:55:34 -0600

Dirk Thomas
16276 ●62 ●190 ●215

updated 2013-08-26 06:56:52 -0600

There has been an announcement on the ros-release mailing list. I can't point to the archive since that is not yet available after the migeation to the OSUOSL.

We are continuing our migration of ROS services.  Today the release repository for dry packages has been moved from <a href="http://code.ros.org">code.ros.org</a> to Google code (<a href="https://code.google.com/p/ros-dry-releases/">https://code.google.com/p/ros-dry-releases/</a>).

The new repository location requires every maintainer who wants to release dry packages in the future to re-do the setup instructions (<a href="http://www.ros.org/wiki/release/Setup/Machine">http://www.ros.org/wiki/release/Setup/Machine</a>):

* update the installed Debian package "python-rosrelease" to version >= 0.2.11

* get a fresh checkout of the release tools from their new location

* request to join the ros-dry-releases project by sending an email to <a href="mailto:ros-release@code.ros.org">ros-release@code.ros.org</a> with your Googlecode login

If you are releasing ROS packages you might want to sign up for that mailing list since important release information like this is posted there.