Received: from spf1.us4.outblaze.com (spf1.us4.outblaze.com [205.158.62.23]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id iAA7C531000804 for ; Wed, 10 Nov 2004 07:12:06 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf1.us4.outblaze.com (Postfix) with ESMTP id 2B2EE53AFE for ; Wed, 10 Nov 2004 07:12:00 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CRmmY-0003Ja-SX for migo@homemail.com; Wed, 10 Nov 2004 02:20:42 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CRml7-0002W6-2E for gnu-arch-users@gnu.org; Wed, 10 Nov 2004 02:19:13 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CRml6-0002VN-4G for gnu-arch-users@gnu.org; Wed, 10 Nov 2004 02:19:12 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CRml6-0002VJ-2C for gnu-arch-users@gnu.org; Wed, 10 Nov 2004 02:19:12 -0500 Received: from [66.187.233.31] (helo=mx1.redhat.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CRmcG-0004hn-SB for gnu-arch-users@gnu.org; Wed, 10 Nov 2004 02:10:05 -0500 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iAA7A3hp017677; Wed, 10 Nov 2004 02:10:04 -0500 Received: from pobox.tokyo.redhat.com (pobox.tokyo.redhat.com [172.16.33.225]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iAA7A2r02035; Wed, 10 Nov 2004 02:10:03 -0500 Received: from localhost (gls07.tokyo.redhat.com [172.16.32.104]) by pobox.tokyo.redhat.com (8.12.8/8.12.8) with ESMTP id iAA7A0OC018491; Wed, 10 Nov 2004 16:10:01 +0900 Date: Wed, 10 Nov 2004 15:38:49 +0900 (JST) Message-Id: <20041110.153849.53700245.jet@gyve.org> To: bulb@ucw.cz Subject: Re: [Gnu-arch-users] Re: conflict applying patch in arch_build_revision From: Masatake YAMATO In-Reply-To: <20041109232704.GS721@vagabond> References: <20041109.173235.212066485.jet@gyve.org> <20041109232704.GS721@vagabond> X-Mailer: Mew version 4.0.62 on Emacs 21.3.50 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 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: 4205 Lines: 107 Thank you for suggestions. > On Tue, Nov 09, 2004 at 11:11:24 +0100, Matthieu Moy wrote: > > Masatake YAMATO writes: > > > > >> [jet@localhost jet]$ tla get jet@gyve.org--inspector/gtracer--mainline--0.0 /tmp/examples > > >> * from pristine cache: jet@gyve.org--inspector/gtracer--mainline--0.0--base-0 > > >> * patching for revision: jet@gyve.org--inspector/gtracer--mainline--0.0--patch-1 > > >> PANIC: conflict applying patch in arch_build_revision > > > > Seems your archive is corrupted :-( > > It does not have to be the archive. It might be the "pristine cache", > that is pristine tree in your working copy. Try to remove each and every > {arch}/++pristine-trees directory you can find. In fact, those in > /tmp/* should suffice. Like this? [jet@localhost tmp]$ tla get jet@gyve.org--inspector/gtracer--mainline--0.0--base-0 /tmp/examples * from import revision: jet@gyve.org--inspector/gtracer--mainline--0.0--base-0 * making pristine copy * tree version set jet@gyve.org--inspector/gtracer--mainline--0.0 [jet@localhost tmp]$ cd examples/ [jet@localhost examples]$ find . | grep '\{arch\}/++pristine-trees$' ./{arch}/++pristine-trees [jet@localhost examples]$ rm -rf ./{arch}/++pristine-trees [jet@localhost examples]$ tla update * setting aside local changes temporarily * linting the source tree * build pristine tree for jet@gyve.org--inspector/gtracer--mainline--0.0--base-0 * from import revision: jet@gyve.org--inspector/gtracer--mainline--0.0--base-0 * reverting changes * updating for new patches in archive * finding or making gtracer--mainline--0.0--base-0 * build reference tree for jet@gyve.org--inspector/gtracer--mainline--0.0--base-0 * from import revision: jet@gyve.org--inspector/gtracer--mainline--0.0--base-0 * finding or making gtracer--mainline--0.0--patch-40 * build reference tree for jet@gyve.org--inspector/gtracer--mainline--0.0--patch-40 * from import revision: jet@gyve.org--inspector/gtracer--mainline--0.0--base-0 * patching for revision: jet@gyve.org--inspector/gtracer--mainline--0.0--patch-1 PANIC: conflict applying patch in arch_build_revision [jet@localhost examples]$ > By the way, is the machine running tmpreaper? That would explain > corruption of pristines under tmp. /tmp is used to explain my trouble. Even if I run `tla get' in my home directory, the situation is not changed. After updating which was failed as I write above, I tried to run tla replay. It seems that =tagging-method causes the trouble. [jet@localhost examples]$ tla replay * patching for revision jet@gyve.org--inspector/gtracer--mainline--0.0--patch-1 A/ misc A/ misc/.arch-ids A/ src A/ src/.arch-ids A/ src/module A/ src/module/.arch-ids A/ src/preload A/ src/preload/.arch-ids A Makefile.am A autogen.sh A configure.in A misc/.arch-ids/=id A misc/Makefile.am A run-test.sh.in A src/.arch-ids/=id A src/Makefile.am A src/gtracer.h A src/module/.arch-ids/=id A src/module/Makefile.am A src/module/extensions.c A src/module/log.c A src/module/main.c A src/module/module.h A src/module/nil_log.c A src/module/pmaps_log.c A src/module/queue.c A src/module/signal_log.c A src/module/viewer.c A src/preload/.arch-ids/=id A src/preload/Makefile.am A src/preload/gmodule_wrapper.c A src/preload/init.c A src/preload/preload.h A src/preload/signal_wrapper.c A src/test.c A {arch}/.arch-project-tree CA {arch}/=tagging-method A {arch}/gtracer/gtracer--mainline/gtracer--mainline--0.0/jet@gyve.org--inspector/patch-log/base-0 A {arch}/gtracer/gtracer--mainline/gtracer--mainline--0.0/jet@gyve.org--inspector/patch-log/patch-1 replay: conflicts occured during replay [jet@localhost examples]$ _______________________________________________ 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/