gnu-arch-users
[Top][All Lists]
Advanced

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

[Gnu-arch-users] tla get PANIC


From: John F Meinel Jr
Subject: [Gnu-arch-users] tla get PANIC
Date: Tue, 17 Feb 2004 15:28:45 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

I am having a very quirky bug. Specifically, I am trying to get a project from my archive, but I can only check it out in an empty tree. So if I type:
$ mkdir tmp && cd tmp
$ tla get vida--dev--0.1 vida

It works fine.

However, if I try and do it in my normal working directory, (which has sub-dirs with other checked out repositories), I get:

$ tla get vida--dev--0.1
* from pristine cache: address@hidden/vida--dev--0.1--base-0
* patching for revision: address@hidden/vida--dev--0.1--patch-1
PANIC: conflict applying patch in arch_build_revision

Is there any reason that 'tla get' would depend on what directory I am in? Does it search sub-directories for other arch repositories, and that is causing the conflict?

To give an idea of my layout, I have a central repository (address@hidden), and then my own personal repository (address@hidden). One of the subdirectories in my working directory contains the central repository, and I am trying to 'get' from my personal repository.

I can issue the command:
$ tla get vida--dev--0.1--base-0
In the working directory and it works. However, when I try to do:
$ tla update
I get:
D  configs/.arch-ids/all-dev.id
D  configs/all-dev
A  configs/all-dev
A {arch}/vida/vida--dev/vida--dev--0.1/address@hidden/patch-log/patch-1 A {arch}/vida/vida--dev/vida--dev--0.1/address@hidden/patch-log/patch-2 A {arch}/vida/vida--dev/vida--dev--0.1/address@hidden/patch-log/patch-2
M  {arch}/=tagging-method
* changeset: ./,,apply-delta-changeset.1077053164.1940.7
* applying changeset
CA  configs/all-dev
A {arch}/vida/vida--dev/vida--dev--0.1/address@hidden/patch-log/patch-1 A {arch}/vida/vida--dev/vida--dev--0.1/address@hidden/patch-log/patch-2 A {arch}/vida/vida--dev/vida--dev--0.1/address@hidden/patch-log/patch-2
M   {arch}/=tagging-method
* reapplying local changes
* linting the source tree
These explicit ids have no corresponding file:

configs/.arch-ids/all-dev.id


I recently switched from explicit id's to tagline id's. Which seemed to work just fine (that's why you get the D configs/all-dev, and A configs/all-dev.) But for some reason, in this particular directory, it complains when I do the update.

Thanks for whatever help you can give me. Right now I'm just using the workaround of checking out into a different directory, and then moving it into my working directory.
John
=:->





reply via email to

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