Re: CVS commits
Hilmar Preusse <email@example.com> wrote:
> On 16.04.05 Hilmar Preusse (firstname.lastname@example.org) wrote:
>> On 12.04.05 Frank Küster (email@example.com) wrote:
>> > But anyway, I have checked that the debian subdirectories of
>> > tetex-bin and -base are in order, also texmf.d and new-manpages,
>> > at least as far as unstable is concerned.. The only interesting
>> > comparison is between the orig.tar.gz and the corresponding
>> > subdirs from a fresh checkout.
>> OK, I can do an checkout (over DSL), but that won't probably happen
>> before next week.
> Tried to do a checkout an hour ago:
> cvs server: Updating tetex-base/context/config
> cvs server: Updating tetex-base/context/data
> cvs server: Updating tetex-base/debian
> cvs server: Updating tetex-base/debian/cweb-examples
> cvs server: Updating tetex-base/debian/license-info
> cvs server: failed to create lock directory for `/cvs/tetex/tetex-base/debian/license-info' (/cvs/tetex/tetex-base/debian/license-info/#cvs.lock): Permission denied
> cvs server: failed to obtain dir lock in repository `/cvs/tetex/tetex-base/debian/license-info'
> cvs [server aborted]: read lock failed - giving up
This only happens for anonymous checkouts. And I have no idea why cvs
would want to lock the directory at all if you are just doing a
checkout; as far as I understand the Cederqvist, this is only done when
a process needs write access. Well, cvs speaks about a "read lock".
Maybe you can talk to the CVS maintainer.
Inst. f. Biochemie der Univ. Zürich