incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Van Steenburgh" <vansteenbu...@users.sf.net>
Subject [allura:tickets] #6355 SCM Auth not working properly with some special chars in repo name [ss4315]
Date Mon, 01 Jul 2013 14:43:52 GMT
- **status**: open --> in-progress
- **assigned_to**: Tim Van Steenburgh



---

** [tickets:#6355] SCM Auth not working properly with some special chars in repo name [ss4315]**

**Status:** in-progress
**Labels:** support p2 
**Created:** Tue Jun 11, 2013 12:25 PM UTC by Chris Tsai
**Last Updated:** Fri Jun 28, 2013 06:18 PM UTC
**Owner:** Tim Van Steenburgh

[forge:site-support:#4315]

>L.S.

>After the upgrade of our Hg projects in https://sourceforge.net/projects/openu/ to Allura,
some projects (for instance https://sourceforge.net/p/openu/nl-openu-products-portlet and
https://sourceforge.net/p/openu/nl.openu.stoer.course-theme) cannot be pushed to anymore.
The error message is:

>jal@orange:/opt/sdk/themes/nl.openu.stoer.course-theme$ hg push
pushing to ssh://joolza@hg.code.sf.net/p/openu/nl.openu.stoer.course-theme
running ssh joolza@hg.code.sf.net 'hg -R p/openu/nl.openu.stoer.course-theme serve --stdio'
searching for changes
2 changesets found
remote: abort: could not lock repository /hg/p/openu/nl.openu.stoer.course-theme: Permission
denied
abort: unexpected response: empty string

>Other repositories on which we have identical rights do work. Permission setting on the
UI seem to be in order and we tried doing this a a developer and as an admin with the same
result. Has something gone wrong with the conversion, and can we fix this ourselves? I can't
find a way do do shell access to the new Allura repos to fix this.

>Thanks in advance,

>Jules Alberts (sf account joolza)

Permissions on the project settings seem fine, but <https://sourceforge.net/auth/repo_permissions?username=joolza&repo_path=/p/openu/nl.openu.stoer.course-theme>
isn't returning the values as I would expect (they're all false instead of all true).

Also, I tried creating a few new repos on my test project that included punctuation, and they
don't seem to have the correct auth either:

<https://sourceforge.net/auth/repo_permissions?username=ctsai&repo_path=/p/strawhat/one.dot>
<https://sourceforge.net/auth/repo_permissions?username=ctsai&repo_path=/p/strawhat/plus+repo>

On the other hand, this repo I created a while ago (to test when the repo name restrictions
were relaxed) seems to return auth properly: <https://sourceforge.net/auth/repo_permissions?username=ctsai&repo_path=/p/strawhat/1.>


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message