CVS Proxy do not handle correctly absolute path into Repository file.

( CVSSCC , VS 6.0, Latest, WIN 2000/XP, CVS NT 1.x )

Type: Public Status:Closed Created: 08 Feb 05 02:00 Updated: 16 Mar 05 03:00

--> Igor Pushkov (admin) at 16 Mar 05 03:00 writes

This is fixed in RC2 version.

--> Igor Pushkov (admin) at 11 Feb 05 02:00 writes

We spent some time trying to repeat the problem. We even tried to
manually put the absolute path into Repository file. However in last
case nor CVS not our plug-in not work.
So, if possible can you please prepare small test repository with
small working copy and send zipped copies to us. We not see any chance
to repeat this on our side.

--> Igor Pushkov (admin) at 10 Feb 05 02:00 writes

CVS proxy 1.3 Release Candidate 1 will be release tomorrow.

--> Jean Gauthier (user) at 10 Feb 05 02:00 writes

WinCVS 1.3.20.3
Concurrent Versions System (CVSNT) 2.0.41a (client/server)

CVS Proxy 1.3 will be release in a near future?

--> Igor Pushkov (admin) at 09 Feb 05 02:00 writes

We longer not access /cvs subfolder directly to make something in it.
This is done in version 2.0 of plug-in and will be also added into
version 1.3. Do you check this with version 2.0. as I am ask. It is
also not work?
If yes, could you please let me know your exact CVS environment:
a) Version of WinCVS
b) Version of CVS server
This way we will be able to repeat this.

--> Jean Gauthier (user) at 08 Feb 05 02:00 writes

CVS Proxy do not handle correctly absolute path into Repository file.

WinCVS, for instance, creates a CVS Repository file with absolute reference
to the CVS module. Ie, it concates also the root to the module path.

According to CVS documentation, both relative module path and absolute path
are allowed.

This prevent to use Builtin or external diff and history tool.

Screen shot

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

CVS Proxy do not handle correctly absolute path into Repository file.