[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: Branko Čibej <brane_at_apache.org>
Date: Tue, 4 Sep 2018 00:31:06 +0200

On 03.09.2018 22:30, Nathan Hartman wrote:
> On Mon, Sep 3, 2018 at 11:10 AM Johan Corveleyn <jcorvel_at_gmail.com> wrote:
>
>> On Sun, Sep 2, 2018 at 11:10 PM Nathan Hartman <hartman.nathan_at_gmail.com>
>> wrote:
>>> I've encountered weirdness with wildcards several times today, so I
>>> just tried in a clean freshly checked-out copy:
>>>
>>> E:\workspace\processor>svn rm *.hconfig
>>> svn: E200005: Use --force to override this restriction (local
>> modifications may be lost)
>>> svn: E200005: 'E:\workspace\processor\a' is not under version control
>
> (snip)
>
>
>> My first reaction is that this might be unrelated to svn, but merely
>> to Windows (or some Windows library). I wouldn't know what, but to
>> rule out that svn has anything to do with it, try something like 'dir
>> *.hconfig' in that directory.
>
> Thank you for your reply.
>
> This behavior appears consistent everywhere. For example (I am
> working in a different directory now):
> E:\workspace\BSP>dir *.h
> Volume in drive E is WORK
> Volume Serial Number is D28A-433E
>
> Directory of E:\workspace\BSP
>
> 09/03/2018 04:12 PM 828 BSP-Global.h
> 09/03/2018 04:12 PM 568 BSP-Main.h
> 09/03/2018 04:12 PM 632 DigitalInputs.h
> 09/03/2018 04:12 PM 8,528 DigitalInputsAutoGen.h
> 09/03/2018 04:12 PM 731 DigitalOutputs.h
> 09/03/2018 04:12 PM 10,073 DigitalOutputsAutoGen.h
> 09/03/2018 04:12 PM 502 DmaChannels.h
> 7 File(s) 21,862 bytes
> 0 Dir(s) 250,642,432 bytes free
>
> Okay... Now:
>
> E:\workspace\BSP>svn rm *.h
> svn: E200005: Use --force to override this restriction (local modifications
> may be lost)
> svn: E200005: 'E:\workspace\BSP\B' is not under version control
>
> Like before, it seems to find only the first letter of the filename.
>
> Now if I go over to my Mac...
>
> $ ls -1 *.h
> BSP-Global.h
> BSP-Main.h
> DigitalInputs.h
> DigitalInputsAutoGen.h
> DigitalOutputs.h
> DigitalOutputsAutoGen.h
> DmaChannels.h
>
> $ svn rm *.h
> D BSP-Global.h
> D BSP-Main.h
> D DigitalInputs.h
> D DigitalInputsAutoGen.h
> D DigitalOutputs.h
> D DigitalOutputsAutoGen.h
> D DmaChannels.h
>
> Caveat: My Mac is running svn 1.8.19; the misbehaving Windows machine
> is running 1.10.2.
>
> Any other thoughts?

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.

-- Brane
Received on 2018-09-04 00:31:16 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.