All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bulpin <james@xensource.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Mercurial Repositories on xenbits.xensource.com/Mercurial version 0.6c
Date: Tue, 23 Aug 2005 12:07:40 +0100	[thread overview]
Message-ID: <430B037C.2050606@xensource.com> (raw)

Summary:
   1. xenbits is now running the latest version of Mercurial with no
      apparent problems
   2. people wishing to upgrade their version of Mercurial to 0.6c
      using a local repository created with an older version will
      need to tweak their repository.

Detail:

Matt Mackall, the Mercurial developer, has found the cause of the 
problems we were experiencing with the upgrade to Mercurial 0.6c. The 
full detail was forwarded to this list by Ling Xiaofeng earlier under 
the title "FW: problem for mecurial 0.6c". The following is the xenbits 
specific stuff.

The root cause was a change to the on-disk file layout affecting 
directories that end in ".d" (tools/examples/init.d being our problem). 
What this means for us is that any repository cloned or init'ed with a 
version of Mercurial prior to 0.6c will need to be tweaked using the 
process suggested by Matt:

    find .hg -type d -name "*.[di]" -exec echo mv {} {}.hg ";"

    Run this at the top of your working dir. Take out the 'echo' once
    you've confirmed it's finding the right files.

(An alternative method is to create a fresh clone from xenbits using 
0.6c as this will create the correct file layout.)

I've done this to all repositories on xenbits and we are now running 
0.6c which appears to be working fine now. All repositories verify 
successfully.

Note that this only applies to repositories created with Mercurial 
versions older than 0.6c which are now accessed with 0.6c. The wire 
protocol is unchanged as it is only local on-disk layout that differs. 
This issue will *not* affect the following scenarios:
  - fresh clones made with any Mercurial version
  - any use of 0.6b or earlier as the client (the fact that our server 
runs 0.6c makes no difference)

Regards,
James

                 reply	other threads:[~2005-08-23 11:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=430B037C.2050606@xensource.com \
    --to=james@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.