[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] Re: more CVS->arch woes: botched patchset and commit lo
From: |
Stig Brautaset |
Subject: |
[Gnu-arch-users] Re: more CVS->arch woes: botched patchset and commit locking problem |
Date: |
Sat, 27 Sep 2003 16:09:06 +0100 |
User-agent: |
Mutt/1.3.28i |
On Sep 27 2003, Denys wrote:
> This is a question for both Tom and Charles Duffy. I manually deleted
> the botched entry for patch-9748 from the archive, cached a revision
> (i.e. up to patch-9747), checked it out, and tried to restart from
> there. Now I have two problems:
>
> 1. commit is unable to acquire the revision lock. What does that mean
> and how can I find out and fix the problem?
Oops. When doing archive surgery like that, you should have done
something like this:
% cd {archive}/mozart/mozart--main/mozart--main--0/
% mv patch-9748/++revision-lock patch-9747
% mv patch-9748 /var/tmp/ # or use rm if you're brave...
However, to fix it I would think it should be sufficient to just do:
% tla lock-revision mozart--main--0
You can possibly also fix it with
% cd {archive}/mozart/mozart--main/mozart--main--0/patch-9747/
% mkdir -p ++revision-lock/+contents
Sorry I can't help with your other problems...
--
brautaset.org