Current, official Hg repository?

[Rick Rankin]

> ----- Original Message ----
> From: Stephen J. Turnbull <xxx at yyy>
> To: Rick Rankin <xxx at yyy>
> Cc: XEmacs Beta <xxx at yyy>
> Sent: Friday, February 1, 2008 6:09:58 PM
> Subject: Re: Current, official Hg repository?
> 
> Rick Rankin writes:
> 
> > I'm seeing the same thing. 'hg pull' gives me
> >
> > $ hg pull
> > abort: repository default not found!
> 
> No, that's not the same thing.  Vladimir at least was able to connect
> to the repository.

Well, by 'same thing', I meant that 'hg tip' gives me the same information that Vladimir was reporting:

changeset:   4310:a6d7e031a10b
tag:         tip
user:        Mike Sperber <sperber at deinprogramm.de>
date:        Thu Dec 06 20:10:16 2007 +0100
summary:     Fix two Tailor glitches.

> 
> What does `grep default .hg/hgrc' tell you?

Actually, there's no hgrc file in the .hg directory. The contents are

$ ls -al .hg
drwxr-xr-x+  3 rick Users     0 Feb  1 16:10 .
drwxr-xr-x+ 16 rick Users     0 Feb  1 16:10 ..
-rw-r--r--   1 rick Users    57 Dec  7 17:05 00changelog.i
-rw-r--r--   1 rick Users     8 Feb  1 16:10 branch
-rw-r--r--   1 rick Users    95 Dec  7 17:08 branch.cache
-rw-r--r--   1 rick Users 68085 Feb  1 16:10 dirstate
-rw-r--r--   1 rick Users    15 Dec  7 17:05 requires
drwxr-xr-x+  3 rick Users     0 Feb  1 14:52 store
-rw-r--r--   1 rick Users     0 Dec  7 17:05 undo.dirstate

This is on Cygwin; however, my Linux box has exactly the same contents and gives exactly the same message to 'hg pull'. Perhaps I did the wrong thing when I first got the source. I'm pretty sure I ran

hg clone http://hg.debian.org/hg/xemacs/xemacs-beta

when I first got the source. Maybe I need to start over?

> If it's
> ssh://hg.debian.org//hg/xemacs/xemacs-beta, then you probably are
> having problems with your ssh-agent (need to ssh-add, maybe?)
> Otherwise, if something other than
> http://hg.debian.org/hg/xemacs/xemacs-beta is returned, you can try
> setting it to that.  This may not work (eg, if your original repo was
> cloned from one of our experimental repos or if it's a CVS workspace
> ;-), in which case you'll have to do a new
> 
> hg clone http://hg.debian.org/hg/xemacs/xemacs-beta
> 
> Note that Mercurial's default behavior is somewhat inconvenient for
> non-core-developers.  You can get "cvs update" behavior with "hg pull -u"
> which automatically follows up an "hg pull" with an "hg update".  I
> don't know if there's a cvsrc-like way to make "-u" the default option
> for pull.
> 
> You can also enable the fetch extension by adding
> 
> [extensions]
> hgext.fetch =
> 
> to ~/.hgrc.  This performs an hg pull then an hg update, followed by
> calling your favorite 3-way merge program for any files that have
> conflicts.
> 

Scratch that. I was looking through some of the Mercurial-related messages that I've saved, and I found one from Michael Sperber on 12/7 (see http://calypso.tux.org/pipermail/xemacs-beta/2007-December/012893.html) that gives the following commands for initially getting the source:

hg init xemacs
cd xemacs
hg pull http://hg.debian.org/hg/xemacs/xemacs-beta

*That's* how I initially got the source. It looks like I should have used 'hg clone' instead?

--Rick