> So I see what happened: > > Here is what happens if I try it as anuser with commit privileges: > [EMAIL PROTECTED] spe-super]> hg push -R /builds/th199096/spe-super > -e "ssh -q -F /home/th199096/opensolaris/config" > ssh://[EMAIL PROTECTED]/hg/nfsv41/os-nfs41-gate > pushing to ssh://[EMAIL PROTECTED]/hg/nfsv41/os-nfs41-gate > searching for changes > Are you sure you wish to push? [y/N]: ^Cinterrupted! > > And here is what happens if I try it as anon: > [EMAIL PROTECTED] spe-super]> hg push -R /builds/th199096/spe-super > -e "ssh -q -F /home/th199096/opensolaris/config" > ssh://[EMAIL PROTECTED]/hg/nfsv41/os-nfs41-gate > pushing to ssh://[EMAIL PROTECTED]/hg/nfsv41/os-nfs41-gate > searching for changes > Are you sure you wish to push? [y/N]: > > If I avoid the use of -e, I don't have access rights as either user > because of: > [EMAIL PROTECTED] spe-super]> hg clone /builds/th199096/spe-super > ssh://[EMAIL PROTECTED]//hg/nfsv41/os-nfs41-gate > Restricted use system; no interactive login. > abort: could not create remote repo! > [EMAIL PROTECTED] spe-super]> hg clone /builds/th199096/spe-super > ssh://[EMAIL PROTECTED]//hg/nfsv41/os-nfs41-gate > Restricted use system; no interactive login. > abort: could not create remote repo! > > So what I believe is happening is that even though I am specifying > [EMAIL PROTECTED] in the hg clone/push commands, the > -e option is reading the user name and key out of the config file. And > that is a valid user....
So a couple things going on: Like you figured out, -e is supplying a user arg, so it's not really connecting anonymously. But the later failures are not related to access rights: you're using "hg clone," instead of "hg push." The clone operation will always expect to create the new repository. And you already created it using the SCM console web application. The failure here is "could not create remote repo," not "access denied." I believe the site is responding predictably and appropriately in all cases above, but that the output is somewhat cryptic. --Mark _______________________________________________ website-discuss mailing list [email protected]
