Hi,
I am not a monotone developer, but my monotone installation told me to
send the below output of a monotone session to this e-mail address as
monotone crashed during the command db regenerate_caches.
-
mtn --db=OE.mtn co -b org.openembedded.dev
mtn:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
monotone-0.25.2-0.pm.0.i586.rpm
monotone 0.25
OE-this-is-for-mtn-0.30.mtn.bz2
Database meant for montone 0.30
Note for the monotone developers: can you *please* teach monotone the
difference between
too new and too old when issueing db
Otto Bommer schrieb:
I run OpenSuse 10.2 with the following monotone RPM installed on top
from Packman:
wget
http://packman.links2linux.de/download/monotone/19203/monotone-0.25.2-0.pm.0.i586.rpm
I just created some rpms for oS 10.2 today which haven't yet been
uploaded to venge.net. They can
Note for the monotone developers: can you *please* teach monotone the
difference between
too new and too old when issueing db migrate messages? I've now had to
explain to
multiple users that they shouldn't follow the advice monotone gives, but the
exact reverse
(update mtn, not the db).
I
package monotone
retitle 404616 monotone: Segmentation fault on powerpc
thanks
On 12/27/06, Brian May [EMAIL PROTECTED] wrote:
Me thinks it is still RC, as it makes monotone completely
unusable. Even if it is PowerPC specific, Debian is still supported on
all architectures, not just Intel.
I
In message [EMAIL PROTECTED] on Thu, 04 Jan 2007 20:30:55 +0100, Koen Kooi
[EMAIL PROTECTED] said:
koen monotone-0.25.2-0.pm.0.i586.rpm
koen
koen monotone 0.25
koen
koen OE-this-is-for-mtn-0.30.mtn.bz2
koen
koen Database meant for montone 0.30
koen
koen
koen Note for the monotone
On Thursday 04 January 2007 17:52, Otto Bommer wrote:
[...]
mtn: failed to write debugging log to /home/ootoo/.monotone/dump
This is strange, too. Full disk?
- Thomas M.
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
Thanks for the symbol-ful backtrace. I regret to say I don't know
what is going on there, but I have this bad feeling it's a Boost bug.
zw
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
On 1/4/07, Shaun Jackman [EMAIL PROTECTED] wrote:
On 1/4/07, Zack Weinberg [EMAIL PROTECTED] wrote:
Thanks for the symbol-ful backtrace. I regret to say I don't know
what is going on there, but I have this bad feeling it's a Boost bug.
I get the same impression. Or, perhaps a difference
package monotone
block 404616 405599
thanks
Thanks for tracking down the root cause, Aaron! I suspected a Boost bug.
Cheers,
Shaun
On 1/4/07, Aaron M. Ucko [EMAIL PROTECTED] wrote:
I think bug #405599 may be responsible for #404616 (which I tried to
x-debbugs-cc):
Package: libboost-dev
On 1/4/07, Otto Bommer [EMAIL PROTECTED] wrote:
mtn --db=OE.mtn db regenerate_caches
mtn: regenerating cached rosters and heights
mtn: regenerated
mtn: 9,460/11,737
mtn: fatal: Botan::Exception: Botan: Gzip_Decompression: Data integrity
error - CRC32 error
mtn: this is almost certainly a bug
I have recently desired to take my many branches and consolidate them into a
larger more co-hesive project such that it may be easier for people to work
with.
I have used, with much confusion and difficulty, a structure such as
work/_MTN (branch1)
work/project1/_MTN(branch1.project1)
Oops, forgot to change the subject.
On 1/4/07, J Decker [EMAIL PROTECTED] wrote:
I have recently desired to take my many branches and consolidate them into
a larger more co-hesive project such that it may be easier for people to
work with.
I have used, with much confusion and difficulty,
Shaun == Shaun Jackman [EMAIL PROTECTED] writes:
I think bug #405599 may be responsible for #404616
Great!
(which I
tried to x-debbugs-cc):
For future reference, just a CC will do, x-debbugs-cc only has any
benefit when opening a bug report (and you don't know what the bug id
14 matches
Mail list logo
