Your message dated Mon, 29 Oct 2007 20:37:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#120043: Debian CVS bug triage - bug #120043
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: cvs
Version: 1.11.1p1-1

When using the cvs client against an NT-based cvs pserver the client
mangles the cvsroot to many times.

I can check out the files fine, but doing anything after that fails:

[evelina] peter:~/dir> cvs up
cvs server: Updating .
cvs server: cannot open directory d:/cvsroot/d:/cvsroot/dir: Invalid argument
cvs server: skipping directory 

[evelina] peter:~/dir> cat cvs/Root
:pserver:[EMAIL PROTECTED]:/d//cvsroot

The place it's going wrong is in repos.c, around line 110:
    if (! isabsolute(repos))

repos at this place is d:/cvsroot, and isabsolute (filesubr.c) only
checks the first character for a '/' and not "?:/.*" which is an
absolute path in the windows world (ok, it should really be a '\', but a
'/' is used and works), so the result is that /d//cvsroot is prepended to
repos, resulting in /d//cvsroot/d:/cvsroot/.

Which is wrong and make things fail...

/Peter Toneby
-- 
Alpha Test Version:  Too buggy to be released to the paying public. 
Beta Test Version:  Still too buggy to be released. 
Release Version:  Alternate pronunciation of "Beta Test Version". 


--- End Message ---
--- Begin Message ---
Peter Toneby wrote:
> Feel free to close this bug. It's not relevant for me and is most likely
> fixed in upstream anyway (don't know, haven't checked, will not check).

Closing as now one else besides you reported this problem.

-- 
Lior Kaplan
[EMAIL PROTECTED]

GPG fingerprint:
C644 D0B3 92F4 8FE4 4662  B541 1558 9445 99E8 1DA0


--- End Message ---

Reply via email to