[Gnu-arch-users] Problem with signed archive (unable to acquire revision lock)

[Magnus Therning]

Hmm, there seems to still be some issues with the signing of archives.
This might very well be a known issue, but I couldn't find anything on
the Wiki.

I have a signed archive, and when commiting a new revision I didn't have
my keys available. This resulted in a situation where there is a lock:

 $ tla commit
 A  rebllib/guest/.arch-ids/RidlHeaderIntfAccDecl.py.id
 A  rebllib/guest/RidlHeaderIntfAccDecl.py
 M  rebl
 M  rebllib/guest/__init__.py
 M  rebllib/guest/RidlHeaderIVtbl.py
 arch_commit: unable to acquire revision lock (internal error in 
archive-pfs.c(pfs_lock_revision))
     tree: /home/magnus/prog/rebl
     revision: address@hidden/rebl--main--1--patch-3

But I don't own the lock:
 
 $ tla lock-revision -u address@hidden/rebl--main--1--patch-3
 lock-revision: error unlocking revision address@hidden/rebl--main--1--patch-3 
-- lock not held

How do I get out of this situation?

 $ tla --version
 tla tla-1.2-4 from regexps.com
 
 Copyright 2003 Tom Lord
 
 This is free software; see the source for copying conditions.
 There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
 PARTICULAR PURPOSE.
 
 Report bugs to address@hidden
 
 # automatically generated release id (by arch-buildpackage)
 
 tla-1.2-4

(BTW quick testing shows that any failed run of the signing command
causes this behaviour, i.e. also when one enters the wrong password.
Wouldn't it be nice to have a few re-tries? It would sure be nice if the
archive was left untouched if signing failed.)

/M

-- 
Magnus Therning                    (OpenPGP: 0xAB4DFBA4)
address@hidden
http://magnus.therning.org/

People who don't make mistakes make the greatest mistake of all;
they do nothing.
     -- Unknown

signature.asc
Description: Digital signature