To developers: Is there a CVS server incompatibility with CVSNT since last security update?

[marko]

Hi CVS developers,

a few days ago, when SuSE put the latest security update on the web, we,
of course, did that crucial update immediately. But, strangely, with our
WinCVS and TortoiseCVS clients problems started. It turned out that
suddenly everything checked out was "in the way" during next update!

I joined the discussion concerning strange behaviour of the "SF cvs
servers" (but I guess they are cvs servers on *n*x systems, so perhaps
this should be addressed to you?!) on 2004-05-19 which can be found at:

 
http://sourceforge.net/tracker/?func=detail&aid=949583&group_id=10072&atid=110072

where it is eventually claimed that there is a server problem, not a
client problem.

What do you say to this?

Now I use with WinCVS the latest CVSNT 2.0.41a, which is said to have a
workaround hotfix to overcome the server troubles. With that it works
fine. TortoiseCVS obviously also released a new version.

I don't know what is going on here, perhaps you have more specific
information (probably from SF) or discuss this already on the developer
mailing list...

... I just wanted to let you know about it.

Regards,
Marko