9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 hg with private repositories
Date: Tue, 11 Aug 2009 11:03:19 -0700	[thread overview]
Message-ID: <7d3530220908111103j5376159wac421d81ac9357e4@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0908111052i1a73a2cdmbf4dea075189a0c4@mail.gmail.com>

On Tue, Aug 11, 2009 at 10:52 AM, Russ Cox<rsc@swtch.com> wrote:
> On Tue, Aug 11, 2009 at 9:37 AM, John Floren<slawmaster@gmail.com> wrote:
>> Hi
>>
>> So I'm trying to clone a private repository I just created on
>> bitbucket. This is what I see:
>>
>> jerq% hg clone https://<username>@bitbucket.org/<username>/<repo>/
>> destination directory: <repo>
>> http authorization required
>> realm: Bitbucket.org HTTP
>> user: <username>
>> abort: could not import module msvcrt!
>
> Surely there is a version of https support
> that doesn't involve msvcrt?  That's a
> Windows DLL.
>

I have hacked up python's getpass.py to do password-prompting for Plan
9, so I can now do https authentication. I'll send the modified
getpass.py to 9fans after I've made sure it works ok. My Python-fu is
not great, so right now it just always assumes you're using Plan 9
(bad).


>> If I try with ssh instead:
>> jerq% hg -v clone ssh://hg@bitbucket.org/<username>/<repo>/
>> running ssh hg@bitbucket.org "hg -R <username>/<repo>/ serve --stdio"
>> abort: no suitable response from remote hg!
>
> Presumably this is because ssh is sshv1
> but bitbucket requires sshv2.
>

I did 'bind /bin/openssh/ssh /bin/ssh' before running this hg command,
but to no avail. I do have my public keys uploaded, so there shouldn't
be a problem there... however now that https works I don't necessarily
need the ssh support.


John
-- 
"Object-oriented design is the roman numerals of computing" -- Rob Pike



  reply	other threads:[~2009-08-11 18:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 16:37 John Floren
2009-08-11 17:52 ` Russ Cox
2009-08-11 18:03   ` John Floren [this message]
2009-08-11 18:21   ` Jeff Sickel
2009-08-11 21:13     ` John Floren
2009-08-13  9:13   ` Bela Valek
2009-08-13  9:47     ` Ethan Grammatikidis
2009-08-13 14:53       ` David Leimbach
2009-08-13 15:13         ` Devon H. O'Dell
2009-08-13 15:31           ` Russ Cox
2009-08-13 17:45           ` Daniel Lyons
2009-08-13 18:00             ` erik quanstrom
2009-08-13 10:11     ` Adrian Tritschler
2009-08-15 12:38       ` Steve Simon
2009-08-11 18:19 ` John Floren
2010-05-21  5:08 ` ron minnich
2010-05-21  5:15   ` erik quanstrom
2010-05-21  6:10   ` Federico G. Benavento
2010-05-21 14:31     ` ron minnich
2010-05-21 12:33   ` John Floren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7d3530220908111103j5376159wac421d81ac9357e4@mail.gmail.com \
    --to=slawmaster@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).