monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] database architecture dependent?


From: Leif Jakob
Subject: [Monotone-devel] database architecture dependent?
Date: Tue, 27 Sep 2005 13:43:06 +0200
User-agent: Mutt/1.5.9i

Hi,

I just run in a mysterious problem:

address@hidden:$ monotone --db=empty.db heads -b SomeClosedSourceBranch
monotone: branch 'SomeClosedSourceBranch' is currently merged:
e837f7ee40be350cdb73d30c890968c9aba3f5f9 address@hidden 2005-09-20T13:57:48

address@hidden:$ md5sum empty.db
e7889c5c0fcccfe8fb9d8c707927fcd2  empty.db

address@hidden:$ uname -a
Linux uranus 2.6.11.11 #1 SMP Wed Jun 1 19:05:24 CEST 2005 ia64 GNU/Linux



ok, this look good... now we copy the database to a host with a different 
architecture:

address@hidden:/$ md5sum /tmp/empty.db
e7889c5c0fcccfe8fb9d8c707927fcd2  /tmp/empty.db

=> same file

address@hidden:$ uname -a
Linux praxidike 2.6.11.7 #1 SMP Tue Apr 12 14:02:08 CEST 2005 i686 GNU/Linux

address@hidden:$ monotone --db=/tmp/empty.db heads -b SomeClosedSourceBranch
monotone: branch 'SomeClosedSourceBranch' is empty

... strange... Only this branch is empty, all other that were created when that
branch was created exist.

but

monotone --db=empty.db ls certs e837f7ee40be350cdb73d30c890968c9aba3f5f9 | 
md5sum

returns the same certs on both machines.

Leif







reply via email to

[Prev in Thread] Current Thread [Next in Thread]