On Fri, 22 Oct 2004, Heikki Linnakangas wrote:
> The repository path was changed from /cvsroot/pgsql-server to
> /cvsroot/pgsql some time ago. You'll have to re-checkout or fix the
> CVS/Repository file in each subdirectory in your checked-out copy.
Oh. Thanks! I should have tried, but in the p
On Fri, 22 Oct 2004, Dennis Bjorklund wrote:
I'm having problems with cvs:
cvs diff: failed to create lock directory for `/cvsroot/pgsql-server'
(/cvsroot/pgsql-server/#cvs.lock): No such file or directory
cvs diff: failed to obtain dir lock in repository `/cvsroot/pgsql-server'
cvs [diff aborted]
I'm having problems with cvs:
cvs diff: failed to create lock directory for `/cvsroot/pgsql-server'
(/cvsroot/pgsql-server/#cvs.lock): No such file or directory
cvs diff: failed to obtain dir lock in repository `/cvsroot/pgsql-server'
cvs [diff aborted]: read lock failed - giving up
--
/Dennis
On Wed, Jul 23, 2003 at 12:53:34PM -0400, Tom Lane wrote:
> Patrick Welche <[EMAIL PROTECTED]> writes:
> > On a different note, I also wonder about:
> >
> > M src/backend/parser/gram.c
> >
> > It seems that you checkout the source with no gram.c. Build it, thus creating
> > gram.c. Next time you
Patrick Welche <[EMAIL PROTECTED]> writes:
> On a different note, I also wonder about:
>
> M src/backend/parser/gram.c
>
> It seems that you checkout the source with no gram.c. Build it, thus creating
> gram.c. Next time you cvs update, you get Attic/gram.c merged in :/ - or is
> my use of cvs in
On Wed, Jul 23, 2003 at 11:34:04AM -0300, The Hermit Hacker wrote:
>
> try it now ... I think its a pathing problem with a cron entry ... just
> fixed that, so should be okay now ...
...
> > cvs [server aborted]: read lock failed - giving up
Yup - that's all fine thanks!
> > On a different note
try it now ... I think its a pathing problem with a cron entry ... just
fixed that, so should be okay now ...
On Wed, 23 Jul 2003, Patrick Welche wrote:
> cvs server: Updating src/bin/scripts/po
> cvs server: failed to create lock directory for
> `/projects/cvsroot/pgsql-server/src/bin/scripts/
cvs server: Updating src/bin/scripts/po
cvs server: failed to create lock directory for
`/projects/cvsroot/pgsql-server/src/bin/scripts/po'
(/projects/cvsroot/pgsql-server/src/bin/scripts/po/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository
`/projects/cvsroot/pgsq
On Monday 08 October 2001 09:37 pm, John Summerfield wrote:
> I don't see for whom the long name would be a problem; certainly if
> it has been that way for five years, it couldn't have been a serious
> problem.
Ask Marc why he changed it.
> > > > Correction: Marc Fournier controls the entire di
On Mon, 8 Oct 2001, Lamar Owen wrote:
> On Friday 05 October 2001 07:48 pm, John Summerfield wrote:
> > On Fri, 5 Oct 2001, Lamar Owen wrote:
> > I made it clear I was getting frustrated. Read in that context, I think it
> > was pretty mild;-)
>
> But it was done in an uninformed way. Had you
On Friday 05 October 2001 07:48 pm, John Summerfield wrote:
> On Fri, 5 Oct 2001, Lamar Owen wrote:
> I made it clear I was getting frustrated. Read in that context, I think it
> was pretty mild;-)
But it was done in an uninformed way. Had you read the previous two-three
weeks of the archives,
On Fri, 5 Oct 2001, Marc G. Fournier wrote:
> On Fri, 5 Oct 2001, John Summerfield wrote:
>
> > I don't think I was being rude. It's true I'm no diplomat. I've
> > criticised actions (and, I think, with considerable justice), but I've
> > not actually criticised people.
>
> How can your criticis
On Fri, 5 Oct 2001, Lamar Owen wrote:
> On Thursday 04 October 2001 09:40 pm, John Summerfield wrote:
> > Well, remember I only arrived here in the past two weeks. What I've seen
> > has not been reassuring.
>
> May I be so bold as to suggest your taking a few hours of your time and
> reading th
On Thursday 04 October 2001 09:40 pm, John Summerfield wrote:
> Well, remember I only arrived here in the past two weeks. What I've seen
> has not been reassuring.
May I be so bold as to suggest your taking a few hours of your time and
reading the last six months to a year of the list's archives
On Fri, 5 Oct 2001, John Summerfield wrote:
> On Thu, 4 Oct 2001, Stephan Szabo wrote:
>
>
> > of the message this was in response to which appears to be what Lamar was
> > responding to. Besides, there's a far cry from a message of constructive
> > criticism and the message this was in response
On Fri, 5 Oct 2001, John Summerfield wrote:
> I don't think I was being rude. It's true I'm no diplomat. I've
> criticised actions (and, I think, with considerable justice), but I've
> not actually criticised people.
How can your criticisms be 'with considerable justice' (justification?)
when yo
On Thu, 4 Oct 2001, Lamar Owen wrote:
> On Wednesday 03 October 2001 07:53 pm, John Summerfield wrote:
> > On Tue, 2 Oct 2001, Lamar Owen wrote:
> > > On Monday 01 October 2001 07:33 pm, John Summerfield wrote:
> > > > Time to get your act together fellas.
>
> > > This is open source John, not r
On Thu, 4 Oct 2001, Stephan Szabo wrote:
> of the message this was in response to which appears to be what Lamar was
> responding to. Besides, there's a far cry from a message of constructive
> criticism and the message this was in response to. The point that the
> documentation and reality ne
On Wednesday 03 October 2001 07:53 pm, John Summerfield wrote:
> On Tue, 2 Oct 2001, Lamar Owen wrote:
> > On Monday 01 October 2001 07:33 pm, John Summerfield wrote:
> > > Time to get your act together fellas.
> > This is open source John, not rocket science. (pun intended)
> Hmm. Kids I was at
...
> I hope you're in better shape by beta time.
Hi John. I would highly recommend taking a deep breath and coming back
in a couple of weeks. Things should have settled down by then and we
will have returned to your high standards of service and support. In the
meantime, folks are busy getting u
> Changing the CVS repository so it doesn't work the same way any
> more isn't smart. Having wrong documentation isn't smart. Taking
> two weeks and NOT fixing a simple problem isn't smart. Giving
> wrong advice isn't smart. Test your advice - where possible I
> do.
I will consider this point val
On Thu, 4 Oct 2001, John Summerfield wrote:
> On Tue, 2 Oct 2001, Lamar Owen wrote:
>
>
> > On Monday 01 October 2001 07:33 pm, John Summerfield wrote:
> > > It seems you don't have to be new here to be a bit peeved about things;-(
> > [snip]
> > > Time to get your act together fellas.
> >
> >
On Thu, 4 Oct 2001, John Summerfield wrote:
> I know I'm not well-known here, but I've made my contributions in other arenas where
>I'm stronger.
>
> PG isn't perfect - we all know that. Nor is the project administration. When there's
>a problem identified, someone has to take responsibility fo
On Tue, 2 Oct 2001, Lamar Owen wrote:
> On Monday 01 October 2001 07:33 pm, John Summerfield wrote:
> > It seems you don't have to be new here to be a bit peeved about things;-(
> [snip]
> > Time to get your act together fellas.
>
> This is open source John, not rocket science. (pun intended)
H
On Tue, 2 Oct 2001, Vince Vielhaber wrote:
> On Tue, 2 Oct 2001, John Summerfield wrote:
>
> > On Mon, 1 Oct 2001, Tom Lane wrote:
> >
> >
> > > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > > The one thing I can't check is the anoncvs directory. Not sure if that
> > > > is the same as the CV
On Monday 01 October 2001 07:33 pm, John Summerfield wrote:
> It seems you don't have to be new here to be a bit peeved about things;-(
[snip]
> Time to get your act together fellas.
This is open source John, not rocket science. (pun intended)
Lighten up. The release will happen, regardless of
On Tue, 2 Oct 2001, John Summerfield wrote:
> On Mon, 1 Oct 2001, Tom Lane wrote:
>
>
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > The one thing I can't check is the anoncvs directory. Not sure if that
> > > is the same as the CVS directory.
> >
> > It is the anoncvs server that's broken.
On Mon, 1 Oct 2001, Bruce Momjian wrote:
> > Marc,
> >
> > it worked, but now I'm again getting:
> >
> > cvs server: failed to create lock directory for
>/projects/cvsroot/pgsql/contrib/pgcrypto/expected'
>(/projects/cvsroot/pgsql/contrib/pgcrypto/expected/#cvs.lock): Permission denied
> > cvs
On Mon, 1 Oct 2001, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > The one thing I can't check is the anoncvs directory. Not sure if that
> > is the same as the CVS directory.
>
> It is the anoncvs server that's broken. The committers don't seem to be
> having any problem with
> > The one thing I can't check is the anoncvs directory. Not sure if that
> > is the same as the CVS directory.
>
> It is the anoncvs server that's broken. The committers don't seem to be
> having any problem with accesses to the primary server. I suspect that
> there's a umask or group-membe
Bruce Momjian <[EMAIL PROTECTED]> writes:
> The one thing I can't check is the anoncvs directory. Not sure if that
> is the same as the CVS directory.
It is the anoncvs server that's broken. The committers don't seem to be
having any problem with accesses to the primary server. I suspect that
>
> > Those are directories I just created. They have the same permission as
> > all the other files here. Maybe there is a problem with CVS server
> > creating stuff with the wrong permission.
>
> >From my experience, it is likely that you have a umask problem. Or there
> is some other read/w
>
> > Those are directories I just created. They have the same permission as
> > all the other files here. Maybe there is a problem with CVS server
> > creating stuff with the wrong permission.
>
> >From my experience, it is likely that you have a umask problem. Or there
> is some other read/w
> Those are directories I just created. They have the same permission as
> all the other files here. Maybe there is a problem with CVS server
> creating stuff with the wrong permission.
>From my experience, it is likely that you have a umask problem. Or there
is some other read/write permissio
On Mon, 1 Oct 2001, Bruce Momjian wrote:
> > Marc,
> >
> > it worked, but now I'm again getting:
> >
> > cvs server: failed to create lock directory for
>/projects/cvsroot/pgsql/contrib/pgcrypto/expected'
>(/projects/cvsroot/pgsql/contrib/pgcrypto/expected/#cvs.lock): Permission denied
> > cvs
> Marc,
>
> it worked, but now I'm again getting:
>
> cvs server: failed to create lock directory for
>/projects/cvsroot/pgsql/contrib/pgcrypto/expected'
>(/projects/cvsroot/pgsql/contrib/pgcrypto/expected/#cvs.lock): Permission denied
> cvs server: failed to obtain dir lock in repository
>/p
I can't do `cvs update -d -P'. I get the following error:
cvs server: failed to create lock directory for
`/projects/cvsroot/pgsql/contrib/pgcrypto/expected'
(/projects/cvsroot/pgsql/contrib/pgcrypto/expected/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository
`/
Marc,
it worked, but now I'm again getting:
cvs server: failed to create lock directory for
/projects/cvsroot/pgsql/contrib/pgcrypto/expected'
(/projects/cvsroot/pgsql/contrib/pgcrypto/expected/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository
/projects/cvsroot
should be fixed now ...
On Mon, 1 Oct 2001, Oleg Bartunov wrote:
> Marc,
>
> what's happens with cvs ? I still can't update:
>
> cvs server: failed to create lock directory for
>/projects/cvsroot/pgsql/contrib/pgstattuple'
>(/projects/cvsroot/pgsql/contrib/pgstattuple/#cvs.lock): Permission
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> what's happens with cvs ? I still can't update:
> cvs server: failed to create lock directory for
>/projects/cvsroot/pgsql/contrib/pgstattuple'
>(/projects/cvsroot/pgsql/contrib/pgstattuple/#cvs.lock): Permission denied
> cvs server: failed to obtain
Marc,
what's happens with cvs ? I still can't update:
cvs server: failed to create lock directory for
/projects/cvsroot/pgsql/contrib/pgstattuple'
(/projects/cvsroot/pgsql/contrib/pgstattuple/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository
/projects/cvsroot/p
On Mon, Nov 06, 2000 at 08:59:38AM -0400, The Hermit Hacker wrote:
> what version of CVS are you running? when was the last time you did
> anything with it?
It works again. I have no idea what failed.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linu
what version of CVS are you running? when was the last time you did
anything with it?
cvs on hub hasn't been upgraded since Sept 13th, so it isn't an upgrade
issue ... and just tested from work, and I can checkout no probs ...
On Mon, 6 Nov 2000, Michael Meskes wrote:
> Here's what I get
Here's what I get doing a commit:
Protocol error: 'Directory' missingE Protocol error: 'Directory' missingE
...
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
44 matches
Mail list logo
