Обсуждение: cvs changes and broken links
I couldn't keep up with the list traffic this week, but I thought I saw enough to convince me that after it was all said and done, I would still be able to do `cvs co pgsql`. I'm finding today that after using cvsup to sync up, I can no longer checkout pgsql, but pgsql-server instead. Is this intended, or are there more changes left to be made? Also, as side note, the link for cvsup is broken: http://developer.postgresql.org/TODO/docs/cvsup.html and CVS tree Oragnization: http://developer.postgresql.org/TODO/docs/cvs-tree.html Thanks, Joe
On Sat, 3 Aug 2002, Joe Conway wrote: > I couldn't keep up with the list traffic this week, but I thought I saw > enough to convince me that after it was all said and done, I would still > be able to do `cvs co pgsql`. I'm finding today that after using cvsup > to sync up, I can no longer checkout pgsql, but pgsql-server instead. Is > this intended, or are there more changes left to be made? Okay, I've tested both using the regular CVS and the anoncvs servers, and both co pgsql just fine ... can you email me (off list) the errors you are seeing, as well as your CVSROOT?
Got it, I think ... If you download 'repository' instead of 'pgsql', it should grab everything required, so that you can use CVS locally ... I looks like its working as expected over here, so that I can 'setenv CVSROOT' to this new location, and it will use the modules file properly ... please confirm for me that this is the case on your end ... On Sun, 4 Aug 2002, Marc G. Fournier wrote: > > Ah, okay, this is something I'm going to fix today ... CVSup is known to > be broken, due to the changes ... what I'm going to do is add a > 'repository' target to the available CVSup targets, that will pull down > both CVSROOT *and* everything else, so that 'cvs co pgsql' does work again > ... sh ould be in place later this aft ... > > > On Sun, 4 Aug 2002, Joe Conway wrote: > > > Marc G. Fournier wrote: > > > On Sat, 3 Aug 2002, Joe Conway wrote: > > > Okay, I've tested both using the regular CVS and the anoncvs servers, and > > > both co pgsql just fine ... can you email me (off list) the errors you are > > > seeing, as well as your CVSROOT? > > > > I use cvsup to sync my local CVS server with the main PostgreSQL CVS. A > > few people mentioned to delete the old source tree, so I did. What I'm > > getting now is a CVSROOT/pgsql-server created. When I want to locally > > check out pgsql, if I type `cvs co pgsql` I get: > > cvs checkout: cannot find module `pgsql' - ignored > > which I think is more-or-less expected since there is now no "pgsql" > > project under CVSROOT, but "pgsql-server" instead. > > > > I *can* do `cvs co pgsql-server` and get a pgsql-server tree, which > > *looks* just like pgsql used too, as far as I can tell. > > > > I've attached my cvsup script which I got from the linked cvsup > > instructions before the link went bad ;-) > > > > I can live OK with things like this, but I didn't think this was the > > intended state of affairs. I have done an anonymous cvs checkout from > > postgresql.org and it works just as advertised. > > > > Thanks for your help, > > > > Joe > > > >
Marc G. Fournier wrote: > Got it, I think ... If you download 'repository' instead of 'pgsql', it > should grab everything required, so that you can use CVS locally ... > > I looks like its working as expected over here, so that I can 'setenv > CVSROOT' to this new location, and it will use the modules file properly > ... please confirm for me that this is the case on your end ... > Yup, appears that did it. Thanks! Joe
On Sun, 4 Aug 2002, Joe Conway wrote: > Marc G. Fournier wrote: > > Got it, I think ... If you download 'repository' instead of 'pgsql', it > > should grab everything required, so that you can use CVS locally ... > > > > I looks like its working as expected over here, so that I can 'setenv > > CVSROOT' to this new location, and it will use the modules file properly > > ... please confirm for me that this is the case on your end ... > > > > Yup, appears that did it. > > Thanks! Great, thanks for the update ...