Check-ins fail - problem with the username

  3 posts   Feedicon  
Replies: 2 - Last Post: October 12, 2009 17:00
by: Frederic Jean
showing 1 - 3 of 3
 
Posted: September 15, 2009 16:33 by 3P.
I am unable to make any chek-ins in my git repository using this account on Kenai. Any attempt to push a commit fails with the following error:

# git push -v origin master
Pushing to ssh://3P.@git.kenai.com/agentai~source
Counting objects: 633, done.
Compressing objects: 100% (590/590), done.
Writing objects: 100% (633/633), 139.66 KiB, done.
Total 633 (delta 478), reused 0 (delta 0)
user 3P. is not authorized to write to repository agentai~source
error: hooks/pre-receive exited with error code 1
To ssh://3P.@git.kenai.com/agentai~source
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'ssh://3P.@git.kenai.com/agentai~source'

According to the repository permissions I should have full read-write access.
I tried using a different user account (ppaw) with all information, including the ssh keypair, identical and it worked flawlessly, so the problem is probably related to my username (3P.).
Kenai revision 20090828.cb744ea
 
Posted: September 15, 2009 18:15 by Edwin Goei
That would be my guess as well. It appears to be a bug where kenai.com allows usernames with dot characters but not all parts of the system handle dots such as git and maybe hg source repositories. A workaround would be to create another account without a dot and add that to the same project with the appropriate role which you have already done. Thanks for the report and we will fix this in a future version.
 
Posted: October 12, 2009 17:00 by Frederic Jean
We pushed a change to address this particular issue. You should now be able to pull and push from your repository using the 3P. username.

Let us know if you have any further problems.
Replies: 2 - Last Post: October 12, 2009 17:00
by: Frederic Jean
  • Mysql
  • Glassfish
  • Jruby
  • Rails
  • Nblogo
Terms of Use; Privacy Policy;
© 2010, Oracle Corporation and/or its affiliates
(revision 20120518.3c65429)
 
 
Close
loading
Please Confirm
Close