After my last post I decided to do sanity check to verify what I saw before 
when running the command you requested and I guess it was good I did.  I'm 
not sure why but I got a different result.

barry@R0150313:~/cvs/repo$ cvs -f -d 
:pserver:m022927@R0199562:/QREADS5_1_repo checkout -r HEAD -p 
Checking out CVSROOT/modules
RCS:  /QREADS5_1_repo/CVSROOT/modules,v
VERS: 1.1
# Three different line formats are valid:
# key -a    aliases...
# key [options] directory
# key [options] directory files...
# Where "options" are composed of:
# -i prog Run "prog" on "cvs commit" from top-level of module.
# -o prog Run "prog" on "cvs checkout" of module.
# -e prog Run "prog" on "cvs export" of module.
# -t prog Run "prog" on "cvs rtag" of module.
# -u prog Run "prog" on "cvs update" of module.
# -d dir Place module in directory "dir" instead of module name.
# -l Top-level directory only -- do not recurse.
# NOTE:  If you change any of the "Run" options above, you'll have to
# release and re-checkout any working directories of these modules.
# And "directory" is a path to a directory relative to $CVSROOT.
# The "-a" option specifies an alias.  An alias is interpreted as if
# everything on the right of the "-a" had been typed on the command line.
# You can encode a module within a module by using the special '&'
# character to interpose another module into the current module.  This
# can be useful for creating a module that consists of many directories
# spread out over the entire source repository.

On Tuesday, November 19, 2013 3:36:28 PM UTC-6, Barry Novinger wrote:
> Hi Christian,
> Any new ideas on this?
> Thanks,
> On Thursday, November 14, 2013 4:25:57 PM UTC-6, Barry Novinger wrote:
>> barry@R0150313:~/cvs/repo/QReadsApp$ cvs -d 
>> :pserver:m022927@R0199562:/QREADS5_1_repo checkout QReadsApp
>> cvs server: Updating QReadsApp
>> U QReadsApp/.classpath
>> U QReadsApp/.cvsignore
>> U QReadsApp/.project
>> U QReadsApp/.runtime
>> U QReadsApp/
>> .
>> .
>> .
>> U QReadsApp/edu/mayo/qreads/device/
>> cvs server: Updating QReadsApp/eehTmp
>> cvs server: Updating QReadsApp/icons
>> cvs server: Updating QReadsApp/images
>> U QReadsApp/images/wmp.bmp
>> cvs server: Updating QReadsApp/routeLists
>> barry@R0150313:~/cvs/repo/QReadsApp$ ls
>> QReadsApp
>> barry@R0150313:~/cvs/repo/QReadsApp$ cd QReadsApp
>> barry@R0150313:~/cvs/repo/QReadsApp/QReadsApp$ ls
>> build.xml      log4j.dtd            picn6220.dll
>> CVS            log4j.xml            picn6320.dll
>> edu            mcaRouteList.config  picn6520.dll
>> eehTmp         mcfRouteList.config  qreadsBuild.xml
>> icons          mcrRouteList.config  QReadsJniKit.dll
>> images         META-INF             routeLists
>> jmh263enc.dll
>> jmjpeg.dll     PegJniKit.dll
>> jmutil.dll     picn20.dll
>> barry@R0150313:~/cvs/repo/QReadsApp/QReadsApp$ cat CVS/Root
>> :pserver:m022927@R0199562:/QREADS5_1_repo
>> On Friday, November 8, 2013 11:23:48 AM UTC-6, Barry Novinger wrote:
>>> After exploring the existing topics and trying a number of things I 
>>> decided to post for specific help.
>>> Just recently downloaded reviewboard 1.7.16
>>> using mysql, apache mod_wsgi following the best instructions I can find.
>>> I can add a local CVS repository to reviewboard but not the teams remote 
>>> CVSNT repository.
>>> I can also access the teams CVSNT repository from the ubuntu shell. 
>>>  using cvs -d :pserver:user@host:/repo login
>>> Let me know if you need anything for diagnostics or have anything you 
>>> recommend me checking or trying 
>>> Thanks,

Get the Review Board Power Pack at
Sign up for Review Board hosting at RBCommons:
Happy user? Let us know at
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to