WinCVS breaks after 1.1.17

[vipuls]

WinCVS does not work properly with Wine post 1.1.17. (Ubuntu Jaunty)

For some reason, a fresh checkout of a repository shows files as "modified" even though they have just been checked out.

I reverted back to 1.1.17 and things are back to normal. I am not sure how to file this so I am posting here.

[David Gerard]

2009/4/16 vipuls <[email protected]>:

WinCVS does not work properly with Wine post 1.1.17. (Ubuntu Jaunty)
For some reason, a fresh checkout of a repository shows files as "modified" even though they have just been checked out.
I reverted back to 1.1.17 and things are back to normal.  I am not sure how to file this so I am posting here.

If you're able to use CVS, you should be able to use git A
regression test is the way to pinpoint just what broke it for a bug
report:

http://wiki.winehq.org/RegressionTesting

This will allow you to zero in on the precise commit that broke WinCVS on Wine.


- d.

[austin987]

On Thu, Apr 16, 2009 at 2:31 PM, David Gerard <[email protected]> wrote:

2009/4/16 vipuls <[email protected]>:

WinCVS does not work properly with Wine post 1.1.17. (Ubuntu Jaunty)
For some reason, a fresh checkout of a repository shows files as "modified" even though they have just been checked out.
I reverted back to 1.1.17 and things are back to normal.  I am not sure how to file this so I am posting here.

If you're able to use CVS, you should be able to use git A
regression test is the way to pinpoint just what broke it for a bug
report:

http://wiki.winehq.org/RegressionTesting

This will allow you to zero in on the precise commit that broke WinCVS on Wine.


- d.

As a guess, I'd say it's the UnixFS patch again. In git, try:
$ git show 8044c11ecfca09e2b643feccb95a4d8f645ba656 | patch -p1 -R
$ make

and see if it works

--
-Austin

[vipuls]

As a guess, I'd say it's the UnixFS patch again. In git, try:
$ git show 8044c11ecfca09e2b643feccb95a4d8f645ba656 | patch -p1 -R
$ make

and see if it works

--
-Austin

So i checked out the Source and compiled -- and verified that the problem exists on HEAD.

Then I patched like you said and compiled -- and the problem goes away.

Is there already a bug posted for this? Is there a workaround?

Thanks.

[austin987]

On Thu, Apr 16, 2009 at 7:02 PM, vipuls <[email protected]> wrote:

As a guess, I'd say it's the UnixFS patch again. In git, try:
$ git show 8044c11ecfca09e2b643feccb95a4d8f645ba656 | patch -p1 -R
$ make

and see if it works

--
-Austin

So i checked out the Source and compiled -- and verified that the problem exists on HEAD.

Then I patched like you said and compiled -- and the problem goes away.

Is there already a bug posted for this? Is there a workaround?

http://bugs.winehq.org/show_bug.cgi?id=17980

There's a patch in the bug.

--
-Austin