cvs problem

Oleg Bartunov <oleg@sai.msu.su> 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 dir lock in repository /projects/cvsroot/pgsql/contrib/pgstattuple'
cvs [server aborted]: read lock failed - giving up

Hmm. That's a new directory that Tatsuo just created. I bet the
umask or group ID that the cvs server is running under is wrong.

regards, tom lane

should be fixed now ...

On Mon, 1 Oct 2001, Oleg Bartunov 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 server: failed to obtain dir lock in repository /projects/cvsroot/pgsql/contrib/pgcrypto/expected'
cvs [server aborted]: read lock failed - giving up

Seems, again wrong permissions

Regards,

Oleg
On Mon, 1 Oct 2001, Marc G. Fournier wrote:

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 denied
cvs server: failed to obtain dir lock in repository /projects/cvsroot/pgsql/contrib/pgstattuple'
cvs [server aborted]: read lock failed - giving up

Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

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/pgsql/contrib/pgcrypto/expected'
cvs [server aborted]: read lock failed - giving up

Seems, again wrong permissions

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.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

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 permissions problem for group and other.

Please dive into the cvs repository and check the files (and directory,
which seems to be lacking group write permission) Bruce.

- Thomas

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 permissions problem for group and other.

Please dive into the cvs repository and check the files (and directory,
which seems to be lacking group write permission) Bruce.

OK, I see:

drwxrwxr-x 2 momjian pgsql 512 Oct 1 15:53 sql

and in the SQL directory I see:

-r--r--r-- 1 momjian pgsql 1843 Oct 1 12:12 blowfish.sql,v
-r--r--r-- 1 momjian pgsql 600 Oct 1 12:12 crypt-blowfish.sql,v
-r--r--r-- 1 momjian pgsql 547 Oct 1 12:12 crypt-des.sql,v
-r--r--r-- 1 momjian pgsql 559 Oct 1 12:12 crypt-md5.sql,v
-r--r--r-- 1 momjian pgsql 571 Oct 1 12:12 crypt-xdes.sql,v
-r--r--r-- 1 momjian pgsql 1529 Oct 1 12:12 hmac-md5.sql,v
-r--r--r-- 1 momjian pgsql 1536 Oct 1 12:12 hmac-sha1.sql,v
-r--r--r-- 1 momjian pgsql 350 Oct 1 12:12 init.sql,v
-r--r--r-- 1 momjian pgsql 694 Oct 1 12:12 md5.sql,v
-r--r--r-- 1 momjian pgsql 1371 Oct 1 12:12 rijndael.sql,v
-r--r--r-- 1 momjian pgsql 702 Oct 1 12:12 sha1.sql,v

I don't know what else to look for. Ideas?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

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 permissions problem for group and other.

Please dive into the cvs repository and check the files (and directory,
which seems to be lacking group write permission) Bruce.

The one thing I can't check is the anoncvs directory. Not sure if that
is the same as the CVS directory.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Bruce Momjian <pgman@candle.pha.pa.us> 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
there's a umask or group-membership issue on the anoncvs machine only.

regards, tom lane

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 server: failed to obtain dir lock in repository /projects/cvsroot/pgsql/contrib/pgcrypto/expected'
cvs [server aborted]: read lock failed - giving up

Seems, again wrong permissions

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.

Did you change versions of cvs (the software)? I had a little fiddle with it some time ago, and there was a change whereby the newer version didn't do what I wanted.

On Mon, 1 Oct 2001, Tom Lane wrote:

Bruce Momjian <pgman@candle.pha.pa.us> 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
there's a umask or group-membership issue on the anoncvs machine only.

It seems you don't have to be new here to be a bit peeved about things;-(

I'm peeved because I found instructions on how to checkout with anonymous CVS and did so a few times.

I had a find old time finding and reporting problems (with the software).

Then CVS stopped working because someone thought it a fine idea to reorganise the directory structure, to change the CVSROOT. No matter the user who had the old one stored on their computers.

I've report it twice, pointing out that what I did before worked, and that I was doing coincided with what the web pages said.

There was discussion that the web pages were wrong and who's job it was to fix. As an invited guest, I reckon it's the CVS repository that is wrong. It's wrong because it's different from what worked before.

Time to get your act together fellas.

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-membership issue on the anoncvs machine only.

Ack! Before everyone under the sun claims to have found a problem: the
user that the anon cvs pserver is running under can't create lock files
in the src dirs inline w/ the code). A few things can happen:

1) Add the cvs pserver user to the pgsql group and add write privs to
the dirs for the user (chmod -R g+w *)

2) Add a LockDir in the cvs config.

cvs co CVSROOT
cd CVSROOT
echo "LockDir /tmp/cvsroot" >> config
cvs ci -m "Adding a central lock dir to the anoncvs server" config
mkdir /tmp/cvsroot
chmod 1777 /tmp/cvsroot
chown root.wheel /tmp/cvsroot

I think that should do it... -sc

--
Sean Chittenden

On Tue, 2 Oct 2001, John Summerfield wrote:

On Mon, 1 Oct 2001, Tom Lane wrote:

Bruce Momjian <pgman@candle.pha.pa.us> 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
there's a umask or group-membership issue on the anoncvs machine only.

It seems you don't have to be new here to be a bit peeved about things;-(

I'm peeved because I found instructions on how to checkout with anonymous CVS and did so a few times.

I had a find old time finding and reporting problems (with the software).

Then CVS stopped working because someone thought it a fine idea to reorganise the directory structure, to change the CVSROOT. No matter the user who had the old one stored on their computers.

Gee, I didn't realize we were doing it just cuze "someone thought it a
fine idea"

I've report it twice, pointing out that what I did before worked, and that I was doing coincided with what the web pages said.

There was discussion that the web pages were wrong and who's job it was to fix. As an invited guest, I reckon it's the CVS repository that is wrong. It's wrong because it's different from what worked before.

I just looked in cvs and it looks fine there.

Time to get your act together fellas.

Gee, I didn't realize we were screwing off.

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net
56K Nationwide Dialup from $16.00/mo at Pop4 Networking
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================

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 minor server issues (that
are being worked out right now, even as I write, by highly capable
professionals, who, BTW, are doing this on a volunteer basis).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

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 <pgman@candle.pha.pa.us> 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
there's a umask or group-membership issue on the anoncvs machine only.

It seems you don't have to be new here to be a bit peeved about things;-(

I'm peeved because I found instructions on how to checkout with anonymous CVS and did so a few times.

I had a find old time finding and reporting problems (with the software).

Then CVS stopped working because someone thought it a fine idea to reorganise the directory structure, to change the CVSROOT. No matter the user who had the old one stored on their computers.

Gee, I didn't realize we were doing it just cuze "someone thought it a
fine idea"

Then why didn't you put it back the way it had been when it worked? When someone does a cvs login, cvs records the value for CVSROOT.

You made everyone's cvs login fail.

I don't see the sense in that.

And then you diddle round endlessly instead of telling me what I had to do to fix YOUR mistake.

I hope you're in better shape by beta time.

And instead of componding the problem with rudeness, listen to it. You don't have to like the message or the language, but there are reasons for both.

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)

Hmm. Kids I was at school with were building rockets in their backyards.
OSS is similarly a backyard affair. Awhere's the difference;-)

Lighten up. The release will happen, regardless of minor server issues (that
are being worked out right now, even as I write, by highly capable
professionals, who, BTW, are doing this on a volunteer basis).

I appreciate the volunteer point. However, a project in disarray is a project in disarray
whether volunteer or not.

And the discussion that followed my original report of the CVS problem looked to me
more like finger-pointing than a real effort to locate and fix the problem, or to help me on my way.

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 for fixing it, and someone has to ensure the person reporting the problem has a way forward.

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.

"Lighten up" isn't the right response. Examine your project. See what points
I make have merit. Welcome criticism. You don't have to like the message you know;-)

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 valid. When we changed CVS download steps,
we should have updated the CVS web page right away. I did update the
SGML version, but for other reasons, the web version didn't update and
that caused great confusion.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

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.

This is open source John, not rocket science. (pun intended)

Lighten up. The release will happen, regardless of minor server issues (that
are being worked out right now, even as I write, by highly capable
professionals, who, BTW, are doing this on a volunteer basis).

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.

"Lighten up" isn't the right response. Examine your project. See what points
I make have merit. Welcome criticism. You don't have to like the message you know;-)

Actually, I think "Lighten up" was a reasonable response, given the tone
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 need to match up is a good one, but saying
that "It's wrong because it's different from what worked before" isn't
reasonable. Saying, "This change is unfortunate and did it really have
to happen and why? And the documentation and the server realities really
have to match up. Perhaps changing the page first with a note of both
configurations with an estimated time change for the server would have
been better/the right way to do this" is reasonable.

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 for fixing it, and someone has to ensure the person reporting the problem has a way forward.

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.

"Lighten up" isn't the right response. Examine your project. See what points
I make have merit. Welcome criticism. You don't have to like the message you know;-)

Do you know why you're not well known? With the pissy attitude you're
showing here more and more folks tend to just drop your email in the
bit bucket - like this...

*** PLONK ***

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net
56K Nationwide Dialup from $16.00/mo at Pop4 Networking
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================

...

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 us there...

Regards.

- Thomas