On Sun, Apr 09, 2006 at 08:38:41AM +0200, Richard Levitte - VMS Whacker wrote:
In message [EMAIL PROTECTED] on Sat, 8 Apr 2006 04:52:05 -0700, Nathaniel
Smith [EMAIL PROTECTED] said:
njs Does anyone know _any_ other problem that should hold up 0.26?
njs Speak up now!
Hmm, you know,
Nathaniel Smith writes:
rev 1: add dir blah
rev 2 (child of rev 1): delete dir blah
rev 3 (child of rev 1): add files blah/foo, blah/bar
and then you merged revs 2 and 3. Since blah was deleted in
2, and left alone in 3, in new merged rev, there is no blah
directory. However,
On Sun, Apr 09, 2006 at 12:04:45PM +0200, Peter Simons wrote:
Thank you for the explanation. The branch in question is very
messed up, unfortunately, I remember doing several wild directory
renames.
And at least one directory delete, apparently :-).
Possibly followed by a directory
Nathaniel Smith wrote:
On Sat, Apr 08, 2006 at 01:54:17PM -0400, [EMAIL PROTECTED] wrote:
And would anyone happen to have tested it on a Debian AMD64 platform?
I'd probably be looking for conpatible packages for Debian i386 sarge
and Debian AMD64 etch -- or starting to learn how to build
[My mail server crashed today, for obscure reasons, and it seems like
I lost a bunch of mails, both going in and out, and judging from the
monotone-devel archive, it looks like this didn't go out. Appologies
if you get a double]
In message [EMAIL PROTECTED] on Sat, 8 Apr 2006 13:54:17 -0400,
On Sun, Apr 09, 2006 at 01:24:15PM -0400, [EMAIL PROTECTED] wrote:
On Sun, Apr 09, 2006 at 12:14:47PM -0500, Matthew A. Nicholson wrote:
Nathaniel Smith wrote:
You can build a deb from the monotone source. It is fairly simple to do
so (dpkg-buildpackage -us -uc -rfakeroot).
Thanks.
On 4/8/06, Richard Levitte - VMS Whacker [EMAIL PROTECTED] wrote:
Could anyone who has experienced all these problems pull the latest
revision, rebuild and see if you still get the same problems?
I have made a build from the monotone-0.26.tar.gz source (downloaded
today) and the simple test
I've been playing around with automate inventory a bit lately to try and
make the implementation a bit more roster friendly and fix a couple of
small-ish issues.
For reference the current format is (roughly):
column 1: pre-state
unchanged, dropped, renamed from
column 2: post-state