(sodesk) ~% cd tmp
(sodesk) ~/tmp% cvs -d:pserver:anoncvs@anoncvs.openoffice.org:/cvs login
(Logging in to anoncvs@anoncvs.openoffice.org)
CVS password: 
(sodesk) ~/tmp% cvs -d:pserver:anoncvs@anoncvs.openoffice.org:/cvs co udk/www
cvs server: cannot find module `udk/www' - ignored
cvs [checkout aborted]: cannot expand modules
(sodesk) ~/tmp% cvs -d:pserver:anoncvs@anoncvs.openoffice.org:/cvs co udk 
cvs server: cannot find module `udk' - ignored
cvs [checkout aborted]: cannot expand modules
(sodesk) ~/tmp% cvs -d:pserver:anoncvs@anoncvs.openoffice.org:/cvs co oo/udk
cvs server: Updating oo/udk
cvs server: Updating oo/udk/bridges
U oo/udk/bridges/makefile.rc
U oo/udk/bridges/version.mk
cvs server: Updating oo/udk/bridges/inc
cvs server: Updating oo/udk/bridges/inc/bridges
<control-c>
(sodesk) ~/tmp/oo% cat CVS/Repository 
oo


The work around that was put in place for the modules file on the anoncvs
server isn't working in all situations.  See above for one such example.

Reassigned to jeremy 
for ownership 
(to coordinate support from chris toward resolution)

Please verify this has been resolved, 
then close issue. 

Accepting.

To transfer jeremy's issues 
and as this relates to the technical infrastructure, 
reassigning to kat 
for ownership 
(to coordinate technical support as required toward resolution). 

Accepting issue.

Accepting issue.

Kat, this should be tracked on p.c.n under a feature request for
the CVSup functionality.  Once this functionality is rolled into
a standard part of SC this issue is one of the problems which
will need to be sure to be addressed.

The issue is that the repository on the anoncvs machine is an exact
mirror of the master except for the way the modules file is handled.

Shane

Reported to SC v1.0 per Chris also. Being tracked and handled internally.

Looking for an update on the timeframe for providing CVSup functionality, and
reclassifying resolved remind.

Kat

Marking Remind

The target for this functionality is the SC 1.1.0 version. 

fixed?

reassigning to taska

Reassigning these to support.  Here's the current process, for those who weren't
at the CollabNet/OpenOffice meeting this week:

1) OpenOffice members should assign new issues to issues@www.openoffice.org (the
default owner).
2) Louis will to through new issues and assign them to support@openoffice.org or
himself.
3) I will look at new issues, "accept" them, and begin work on them.
4) Issues will remain assigned to support@openoffice.org as the CollabNet team
works on them- that way the whole support team is kept abreast of changes, and
support engineers other than myself can help out if necessary.

Thanks!
Taska

I'll look into this.

I tested this and it's actually still a problem.  Still researching
the history.

Okay, having discovered that the entire source tree is under 'oo', I
can verify that 'www' directories now exist in all of the modules.  I
declare this issue fixed.

As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.

As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.