Received: from spf3.us4.outblaze.com (spf3.us4.outblaze.com [205.158.62.25]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id j0P9SMdG018750 for ; Tue, 25 Jan 2005 09:28:23 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf3.us4.outblaze.com (Postfix) with ESMTP id BA1C153911 for ; Tue, 25 Jan 2005 09:28:54 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CtNCX-00078p-Pg for migo@homemail.com; Tue, 25 Jan 2005 04:41:33 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CtN9P-0005vc-Rs for gnu-arch-users@gnu.org; Tue, 25 Jan 2005 04:38:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CtN9O-0005v1-Cr for gnu-arch-users@gnu.org; Tue, 25 Jan 2005 04:38:18 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CtN1I-00048x-Ai for gnu-arch-users@gnu.org; Tue, 25 Jan 2005 04:29:56 -0500 Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.34) id 1CtMdW-0003HB-GQ for gnu-arch-users@gnu.org; Tue, 25 Jan 2005 04:05:22 -0500 Received: (qmail 11481 invoked by uid 0); 25 Jan 2005 09:05:21 -0000 Received: from 139.30.201.19 by www52.gmx.net with HTTP; Tue, 25 Jan 2005 10:05:21 +0100 (MET) Date: Tue, 25 Jan 2005 10:05:21 +0100 (MET) From: "Ulf Ochsenfahrt" To: John A Meinel MIME-Version: 1.0 References: <41F55AF2.30507@arbash-meinel.com> Subject: Re: [Gnu-arch-users] Serious problem here X-Priority: 3 (Normal) X-Authenticated: #2857145 Message-ID: <4796.1106643921@www52.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: gnu-arch-users@gnu.org X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 5654 Lines: 157 > Ulf Ochsenfahrt wrote: > > Hi! > > > > ... > > > # tla get ulfjack@gmx.de--2005/cqs--mainline--0.2 cqs3 > > Password: > > * ensuring library has > ulfjack@gmx.de--2005/cqs--mainline--0.2--patch-140 > > * searching ancestor revision in library in archive ulfjack@gmx.de--2005 > > * found ancestor revision in library > (ulfjack@gmx.de--2005/cqs--mainline--0.2--patch-138) > > * patching for this revision > (ulfjack@gmx.de--2005/cqs--mainline--0.2--patch-140) > > * patching for revision > ulfjack@gmx.de--2005/cqs--mainline--0.2--patch-139 > > > /home/asuffield/arch/dists/tla/tla-1.3/src/tla/libarch/library-txn.c:492:botched invariant > > !replay_status > > PANIC: exiting on botched invariant > > > > This invariant looks like as it was trying to create a local copy in the > revision library, there was an error, so it exited. > > It sounds like something happened such that your patch-139 is corrupt. > When you went to get patch-140, you had 138, so it had to go *through* > 139 to get there. Since 139 is broken, it can't make it to 140. The really weired thing is, after I deleted my gfs revlib (only the cqs thing), I could check out the latest revision again. Mind you, since I use a revlib, I'm not doing cacherevs anymore, so it had to go through 139. > > I deleted the last couple of revisions from both revlibs, but I still > > can't check out that revision on my gf's pc anymore. > > Even deleting the last few, still means when doing a checkout you have > to apply patch-139. > > Try this: > > tla get ulfjack@gmx.de--2005/cqs--mainline--0.2--patch-138 cqs-test > tla get-changset ulfjack@gmx.de--2005/cqs--mainline--0.2--patch-139 p-139 > cd cqs-test > tla apply-changeset ../p-139 > > If that fails, then probably patch-139 is truly corrupt. It doesn't seem like patch-139 is corrupt. Also, on the other machine, I could still check out patch-140. No cacherev. > ... > > I can check out on > > my own. Now it gets even worse. I tried to do a star-merge into my > > _public_ repository. And it did. It applied lots of patches _again_, > > although most of them have already been merged in. Lots of conflicts - > > of course (line-breaks inserted by me): > > > > * star-merge by > delta(ulfjack@conquer-space.net--2004-public/cqs--mainline-- > > 0.2--patch-47,ulfjack@gmx.de--2005/cqs--mainline--0.2--patch-140)[/home/ > > ulfjack/arch/REMOTE-PUBLIC/cqs] > > > > tla logs -f ulfjack@gmx.de--2005/cqs--mainline--0.2 says that it has > > patch-logs up to and including 133. > But you should have up to 140, correct? I wanted to get 134-140 - the last time I star-merged I got up to and including 133, but when I now did star-merge, it got me 47 up to something. > > > > Any idea what went wrong? Could be several mistakes. Could have been my > > fault (at least partially). Any idea how I could fix my repository? > > > > Update: I deleted my gfs revlib and did a full checkout. Now star-merge > > works again. Error in the revlib handling code? I still can't star-merge > > into my public repository. > > If you had a cachrev, then when she does a full checkout, she will never > try to get the broken patch-139. > I don't know what would have gone wrong with the revision library. > > Are you doing something like keeping your revlib in /tmp? I've seen > machines where /tmp is cleaned, such that files that aren't accessed for > a month are deleted. This could cause revision library corruption, which > should be detected, but I suppose may not be. Nope. Its in /home/ulfjack/repository/library/ and the repository is in /home/ulfjack/repository/2005/ (the old one is in .../2004/). > > > > Update 2: I was able to manually merge my private changes into my > > public repository. I could then do a sync-tree and now everything seems > > to work again. > > > > -- Ulf > > I can't tell you much more without having seen the problem. And as it > happened in a private repository, probably it isn't out there to look > at. (I don't really have the time right now, either.) > But hopefully I've given a couple of pointers of things to look for. I cannot give you read access to my private repo, as that is on my home pc (dialup and a firewall). The project I'm talking about is open source, so I could give you a copy of that project (if that would help). It seems like there are two problems here: My gfs inability to checkout 140 (which works now) and my inability to star-merge into my public repo. I got the first one to work again and I think I've deleted too much evidence to provide any more clues as to what went wrong. Now the second... If anyones serious about finding out more, I _could_ get you an ssh connection into my machine. Slow, but it should work. I still have the old tree available where star-merge failed. > John > =:-> Cheers, -- Ulf > Yow. > > Do you get this same botched invariant if you try with the version of > tla you were using before? Which version were you using when this was > committed? 1.3-1, Debian unstable. Unfortunately, I don't have the old version anymore - and I am not sure I could get it - Debian unstable packages get deleted pretty quickly - it was a 1.2 tla though. See http://packages.debian.org/unstable/devel/tla (Only current until Andrew Suffield uploads a new package.) Cheers, -- Ulf -- GMX im TV ... Die Gedanken sind frei ... Schon gesehen? Jetzt Spot online ansehen: http://www.gmx.net/de/go/tv-spot _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/