On 2007.11.16 12:00:02 +0100, Wincent Colaiuta wrote: > El 15/11/2007, a las 22:13, Benoit Sigoure escribió: >> Hi Wincent, >> Can you reproduce this deterministically? If yes, can you re-run the test >> with the --verbose flag and post the gzipped output (or send it to me if >> the list doesn't like this sort of attachment). > > Inspecting the output of --verbose has allowed me to the point where things > are failing; look at the very first test in t9101-git-svn-props.sh and > witness the following: > > - before the test we are at revision 1 > - there are 3 "svn commits" in the test > - but it looks like only 2 of the commits proceed > - so the revision number goes up to 2 then 3, when it should be 4 > - as a result, in one of the later tests we fail because the test expects > revision 8 but we only have revision 7 > > Checked out revision 1. > * ok 1: checkout working copy from svn > > * expecting success: cd test_wc && > echo Greetings >> kw.c && > poke kw.c && > svn commit -m "Not yet an Id" && > echo Hello world >> kw.c && > poke kw.c && > svn commit -m "Modified file, but still not yet an Id" && > svn propset svn:keywords Id kw.c && > poke kw.c && > svn commit -m "Propset Id" && > cd .. > Sending kw.c > Transmitting file data . > Committed revision 2. > Sending kw.c > Transmitting file data . > Committed revision 3. > property 'svn:keywords' set on 'kw.c' > * ok 2: setup some commits to svn > > That last commit is a no-op because, for some reason, the svn propset > before it is also a no-op: > > svn propset svn:keywords Id kw.c > > In other words, it echos "property 'svn:keyword' set on 'kw.c'" but if I > insert an "svn status" as the next command then I get no output at all. If > I run the exact same commands manually from the terminal then they work > (ie. it is not a no-op and "svn status" shows that the file is modified). > > Actually, it's not really a no-op, because if I insert an "svn proplist -v > kw.c" I get: > > Properties on 'kw.c': > svn:keywords : Id It _is_ a no-op. At least here. Because I got an auto-props setting in my ~/.subversion/config to automatically add Id for *.c files. So that property was already there before we explicitly ask for it and the propset turns into a no-op. If I remove that line from the subversion configuration, the test succeeds. Same for you I guess. That said, I had a quick glance over the subversion CLI help, but it didn't tell me how to ignore/override ~/.subversion/config. Anyone less clueless than me around, having a smart idea how to work around that "bug"? Björn - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
