[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Wildcard bug? Or user error?

From: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Thu, 6 Sep 2018 10:22:34 -0400

On Mon, Sep 3, 2018 at 6:31 PM Branko Čibej <brane_at_apache.org> wrote:

> These cases are, believe it or not, completely different. On your Mac,
> the shell expands the wildcards. On Windows, Subversion is linked with a
> library that's shipped with Visual Studio (setargv.obj) that expands the
> wildcards in the arguments. It looks like something strange is happening
> during that wildcard expansion.
>
> It would be best to report this to whoever built the Subversion
> binaries; it might be that their setargv.obj is corrupt somehow.
>
> In any case, there's no code in Subversion proper for expanding
> wildcards in the command-line arguments.
>
>
Just to keep this list in the loop, in case someone else stumbles
upon this, Stefan of Tortoise fame has confirmed your suspicion:
There is a bug in the (at this time) latest Windows SDK, version
10.0.17134.0, that causes the first matching filename to be
truncated to one character.

An upcoming Windows Update is supposed to fix it.

Here is the link Stefan provided:

https://developercommunity.visualstudio.com/content/problem/289637/setargvobj-is-broken-in-the-latest-windows-sdk.html
Received on 2018-09-06 16:22:56 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.