Unable to commit to owned HG fork

Dec 12, 2010 at 3:53 AM

Hi there,

I've just created a fork at:

http://nupackpackages.codeplex.com/SourceControl/network/Forks/nblumhardt/NuGetSprachePackages

After making some changes, I've run 'hg push' (via TortoiseHg) only to get:

pushing to https://hg01.codeplex.com/forks/nblumhardt/nugetsprachepackages

searching for changes

1 changesets found

http authorization required

realm: hg01.codeplex.com

abort: authorization failed

[command interrupted]

I've double- and triple-checked my password.

Any suggestions where I've gone wrong? Many thanks in advance!

Nick

Apr 10, 2011 at 11:08 PM
Edited Apr 10, 2011 at 11:59 PM

Did you get this resolved?  I'm trying to push to my own fork for the first time, and receiving the same results.  I just created the HG fork 3 days ago.  I'm 100% sure my username/password is correct.

Apr 11, 2011 at 6:51 AM
BenAmada wrote:

Did you get this resolved?  I'm trying to push to my own fork for the first time, and receiving the same results.  I just created the HG fork 3 days ago.  I'm 100% sure my username/password is correct.


There was a permission issue on our end that I corrected.  Can you retry your push?

Thanks,
-Colin

Apr 11, 2011 at 9:12 PM

Hi Colin ... I just tried and was successfully able to push.  Thanks very much for fixing that.

Aug 19, 2011 at 4:28 PM

Colin, can you give us more details on what types of issues can cause this? I'm facing a similar problem on a different fork and I don't know what to do. 

I get an authorization error with a log like:

[command returned code 255 Fri Aug 19 12:15:36 2011]
% hg --repository C:\devHg\Orchard.Source\src\Orchard.Web\Modules\Contrib.Chapters outgoing --quiet --template {node}^M https://hg01.codeplex.com/forks/michaelplevy/addimportexport
7b3eaf1ebd7598b7420e30c518239cb7beabf31a
[command completed successfully Fri Aug 19 12:16:03 2011]
% hg --repository C:\devHg\Orchard.Source\src\Orchard.Web\Modules\Contrib.Chapters push https://hg01.codeplex.com/forks/michaelplevy/addimportexport
pushing to https://hg01.codeplex.com/forks/michaelplevy/addimportexport
searching for changes
http authorization required
realm: hg01.codeplex.com
abort: authorization failed
[command returned code 255 Fri Aug 19 12:16:39 2011]
Contrib.Chapters% 

Aug 19, 2011 at 4:31 PM
michaelplevy wrote:

Colin, can you give us more details on what types of issues can cause this? I'm facing a similar problem on a different fork and I don't know what to do. 

I get an authorization error with a log like:

 

[command returned code 255 Fri Aug 19 12:15:36 2011]
% hg --repository C:\devHg\Orchard.Source\src\Orchard.Web\Modules\Contrib.Chapters outgoing --quiet --template {node}^M https://hg01.codeplex.com/forks/michaelplevy/addimportexport
7b3eaf1ebd7598b7420e30c518239cb7beabf31a
[command completed successfully Fri Aug 19 12:16:03 2011]
% hg --repository C:\devHg\Orchard.Source\src\Orchard.Web\Modules\Contrib.Chapters push https://hg01.codeplex.com/forks/michaelplevy/addimportexport
pushing to https://hg01.codeplex.com/forks/michaelplevy/addimportexport
searching for changes
http authorization required
realm: hg01.codeplex.com
abort: authorization failed
[command returned code 255 Fri Aug 19 12:16:39 2011]
Contrib.Chapters% 

 

I've resolved the permission issue on our end. Please try pushing again.

Matt

Aug 19, 2011 at 4:34 PM

Thank you.

Nov 26, 2011 at 9:32 PM

I am getting this same error for atha.codeplex.com.

Matt/Colin/Someone? Please fix!

Dec 2, 2011 at 5:36 AM

I just created a new project, and I'm seeing the same issue

 

% hg clone --verbose -- https://hg01.codeplex.com/latestchattywp7

destination directory: latestchattywp7

no changes found

updating to branch default

resolving manifests

0 files updated, 0 files merged, 0 files removed, 0 files unresolved

http authorization required

realm: hg01.codeplex.com

abort: authorization failed

[command returned code 255 Thu Dec 01 22:35:38 2011]

Dec 2, 2011 at 7:19 AM

When a new project or fork gets created we've occasionally seen an issue where the security configuration is not correct.  The best thing to do is use our Contact Us form to let us know and we'll get it fixed.