Re: [Monotone-devel] default branch for "monotone sync"

[William Uther]

On 26/02/2007, at 7:22 AM, Evan Martin wrote:

> On 2/24/07, Nathaniel Smith <address@hidden> wrote:
> > Best practice is probably to split your two projects out into two
> > databases.  (You can do this by creating two new, empty databases,  
> > and
> > then use a file:// URL with mtn sync to push some subset of branches
> > into each of the new databases; then just modify _MTN/options in your
> > checkouts to point to the new databases.)
>
> % ls -l puz.db
> -rw-r--r-- 1 martine martine 8552448 2007-02-24 14:02 puz.db
>
> % mtn -d hsmtn.db sync file://puz.db org.neugierig.hsmtn
> mtn: connecting to file://puz.db
> mtn: network error: name resolution failure for puz.db: Unknown host
[snip]
> Is this a bug or am I misunderstanding something?  (At least in web
> browsers, file URIs start with file:// and then have a path, so it's
> common to have three slashes at the beginning.)

Monotone seems to use file: instead of file://.  e.g. tests/ 
netsync_over_pipes/__driver__.lua contains the line:

check(mtn("sync", "file:test2.db", "testbranch"), 0, false, false)

On top of that, I was having problems with file: when writing the  
patches I posted over the weekend.  I didn't get around to reporting  
the problems yet.  I ended up testing like this:

mtn -d puz.db serve

Then start a new shell and:

mtn -d hsmtn.db sync localhost org.neugierig.hsmtn

Be well,

Will         :-}