Thread: Permission problems on pgfoundry
Bruce granted me commit privileges on the pg_migrator project, but it
doesn't seem to have quite worked:
> Checking in src/Makefile;
> /cvsroot/pg-migrator/pg_migrator/src/Makefile,v <-- Makefile
> new revision: 1.4; previous revision: 1.3
> cvs [commit aborted]: could not open lock file `/cvsroot/pg-migrator/pg_migrator/src/,Makefile,': Permission denied
Could somebody look into what's wrong there?
regards, tom lane
[+gforge-admins] Everything looks fine, permissions are all 775, with group pg-migrator ... files themselves are all owned by bmomjian:pg-migrator, and 444 ... On Mon, 29 Jun 2009, Tom Lane wrote: > Bruce granted me commit privileges on the pg_migrator project, but it > doesn't seem to have quite worked: > >> Checking in src/Makefile; >> /cvsroot/pg-migrator/pg_migrator/src/Makefile,v <-- Makefile >> new revision: 1.4; previous revision: 1.3 >> cvs [commit aborted]: could not open lock file `/cvsroot/pg-migrator/pg_migrator/src/,Makefile,': Permission denied > > Could somebody look into what's wrong there? > > regards, tom lane > > -- > Sent via pgsql-www mailing list (pgsql-www@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-www > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
What is the root of this checked out repo? It needs to be /cvsroot/pg-migrator, not plain /cvsroot as set out here: <http://pgfoundry.org/scm/?group_id=1000235> If you do that the lock file will be placed in the correct directory. (The reason we have a dummy CVS root in /cvsroot is to support the web interface only. And yes, it's a hack.) cheers andrew On Mon, June 29, 2009 11:30 pm, Marc G. Fournier wrote: > > [+gforge-admins] > > Everything looks fine, permissions are all 775, with group pg-migrator ... > files themselves are all owned by bmomjian:pg-migrator, and 444 ... > > > > On Mon, 29 Jun 2009, Tom Lane wrote: > >> Bruce granted me commit privileges on the pg_migrator project, but it >> doesn't seem to have quite worked: >> >>> Checking in src/Makefile; >>> /cvsroot/pg-migrator/pg_migrator/src/Makefile,v <-- Makefile >>> new revision: 1.4; previous revision: 1.3 >>> cvs [commit aborted]: could not open lock file >>> `/cvsroot/pg-migrator/pg_migrator/src/,Makefile,': Permission denied >> >> Could somebody look into what's wrong there? >> >> regards, tom lane >> >> -- >> Sent via pgsql-www mailing list (pgsql-www@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-www >> > > ---- > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) > Email . scrappy@hub.org MSN . scrappy@hub.org > Yahoo . yscrappy Skype: hub.org ICQ . 7615664 > _______________________________________________ > Gforge-admins mailing list > Gforge-admins@pgfoundry.org > http://pgfoundry.org/mailman/listinfo/gforge-admins >
On Tue, Jun 30, 2009 at 5:07 AM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> Bruce granted me commit privileges on the pg_migrator project, but it
> doesn't seem to have quite worked:
There is a cronjob updating the /etc/{password,groups} files so,
depending on when it's planned, you have a delay before being granted
the access.
(It might not be the problem though).
If we succeed in having pam_pgsql working on FreeBSD, I hope to remove
the delay for the next pgFoundry install.
--
Guillaume
Guillaume Smet <guillaume.smet@gmail.com> writes:
> On Tue, Jun 30, 2009 at 5:07 AM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
>> Bruce granted me commit privileges on the pg_migrator project, but it
>> doesn't seem to have quite worked:
> There is a cronjob updating the /etc/{password,groups} files so,
> depending on when it's planned, you have a delay before being granted
> the access.
Hah, the same commit worked this morning, so that must have been it.
Thanks for the info.
regards, tom lane
"Andrew Dunstan" <andrew@dunslane.net> writes: > What is the root of this checked out repo? It needs to be > /cvsroot/pg-migrator, not plain /cvsroot as set out here: > <http://pgfoundry.org/scm/?group_id=1000235> Hmm ... Bruce has been complaining of problems committing files in the top level of the repo. Maybe this is the cause? regards, tom lane
Tom Lane wrote: > "Andrew Dunstan" <andrew@dunslane.net> writes: > > What is the root of this checked out repo? It needs to be > > /cvsroot/pg-migrator, not plain /cvsroot as set out here: > > <http://pgfoundry.org/scm/?group_id=1000235> > > Hmm ... Bruce has been complaining of problems committing files in the > top level of the repo. Maybe this is the cause? I use this command: cvs -q -d :ext:bmomjian@cvs.pgfoundry.org:/cvsroot/pg-migrator so I should be OK. My problem is that if a subdirectory and the top-level directory both have modified files, the commit message editor shows all files as modified, but only the subdirectory files get changed in CVS; I have to run cvs commit again to apply the top-level changes. I have tried re-checking out the CVS tree but it didn't help. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +