Thread: anoncvs currently broken
anoncvs is still broken: cvs server: Updating src/interfaces/libpqxx/config cvs server: Updating src/interfaces/libpqxx/debian cvs server: failed to create lock directory for `/projects/cvsroot/interfaces/libpqxx/debian' (/projects/cvsroot/interfaces/libpqxx/debian/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/projects/cvsroot/interfaces/libpqxx/debian' cvs [server aborted]: read lock failed - giving up -- Oliver Elphick Oliver.Elphick@lfix.co.uk Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C ======================================== "Watch ye therefore, and pray always, that ye may be accounted worthy toescape all these things that shall come to pass, and to stand before the Son of man." Luke 21:36
should be fixed ... looks like just an ownership issue on a new directory ... On 13 Aug 2002, Oliver Elphick wrote: > anoncvs is still broken: > > cvs server: Updating src/interfaces/libpqxx/config > cvs server: Updating src/interfaces/libpqxx/debian > cvs server: failed to create lock directory for > `/projects/cvsroot/interfaces/libpqxx/debian' > (/projects/cvsroot/interfaces/libpqxx/debian/#cvs.lock): Permission > denied > cvs server: failed to obtain dir lock in repository > `/projects/cvsroot/interfaces/libpqxx/debian' > cvs [server aborted]: read lock failed - giving up > > -- > Oliver Elphick Oliver.Elphick@lfix.co.uk > Isle of Wight, UK > http://www.lfix.co.uk/oliver > GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C > ======================================== > "Watch ye therefore, and pray always, that ye may be > accounted worthy to escape all these things that shall > come to pass, and to stand before the Son of man." > Luke 21:36 > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org >
On Mon, Aug 12, 2002 at 09:38:00PM -0300, Marc G. Fournier wrote: > > should be fixed ... looks like just an ownership issue on a new directory More like I uploaded that directory just as you were rsync'ing to anonymous CVS and a lock file got copied along, but was never deleted on a subsequent rsync. Or so it's been suggested to me. Jeroen
On Tue, 2002-08-13 at 02:47, Jeroen T. Vermeulen wrote: > On Mon, Aug 12, 2002 at 09:38:00PM -0300, Marc G. Fournier wrote: > > > > should be fixed ... looks like just an ownership issue on a new directory > > > More like I uploaded that directory just as you were rsync'ing to > anonymous CVS and a lock file got copied along, but was never deleted > on a subsequent rsync. Or so it's been suggested to me. That was based on a number of assumptions. Of course Marc knows exactly what was wrong because he had to fix it :)
On Tue, 13 Aug 2002, Jeroen T. Vermeulen wrote: > On Mon, Aug 12, 2002 at 09:38:00PM -0300, Marc G. Fournier wrote: > > > > should be fixed ... looks like just an ownership issue on a new directory > > > More like I uploaded that directory just as you were rsync'ing to > anonymous CVS and a lock file got copied along, but was never deleted > on a subsequent rsync. Or so it's been suggested to me. Nope, there was no lock file over there when I checked manually, just had to re-set the perms and all appears to be okay ...