[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Re: [Bug 1311] monotone is broken on Ubuntu
From: |
Nathaniel Smith |
Subject: |
Re: [Monotone-devel] Re: [Bug 1311] monotone is broken on Ubuntu |
Date: |
Tue, 15 Aug 2006 14:48:09 -0700 |
User-agent: |
Mutt/1.5.12-2006-07-14 |
On Mon, Aug 14, 2006 at 06:03:56AM -0700, Brian C. Lane wrote:
> address@hidden wrote:
>
> > http://bugs.openembedded.org/show_bug.cgi?id=1311
> >
> > ------- Comment #2 from address@hidden 2006-08-14 02:14 -------
> > Could you put your OE.mtn file up somewhere where we can see it?
> >
> > When you do, could you email address@hidden, since we
> > don't normally check the OE bug tracker?
> >
> > -- Nathaniel, a monotone people
>
> You can get the file from http://www.brianlane.com/OE.mtn.gz
This file appears to contain some cached data generated by Eric
Anderson's net.venge.monotone.experiment.performance branch. As is
usual for such experiments, there hasn't been any work done to make
sure it interoperates well with mainline monotone, or that there's any
kind of reasonable migration path between them (or even between
versions on that branch). You're of course free to use such branches,
but it's at your own risk, and you need to make sure you know what
you're doing...
If you created the file yourself, then you probably know what I'm
talking about :-). If you got it from somewhere else, then you might
want to have a word with them about distributing broken databases,
and how this could happen...
If it's necessary to migrate this particular database to be
all-mainline or all-performance-experiment, then I do have some
migration code on a different branch that could be extracted and used.
However, unless this database has critical information, you're
probably better off just throwing it away and getting a new one.
The version at http://www.openembedded.org/snapshots/OE.mtn.bz2 is
apparently fine for mtn mainline, but if you want to be sure, you can
run 'mtn db check' after getting your new database, and see if you get
any errors like the one you originally reported.
(Cross-posted to OE bugzilla, to make sure Koen sees it.)
-- Nathaniel
--
.i dei jitfa fanmo xatra