From: Brad King <brad.king@kitware.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-svn: teach dcommit about svn auto-props
Date: Sat, 26 Jul 2008 10:08:05 -0400 [thread overview]
Message-ID: <488B2FC5.4080801@kitware.com> (raw)
In-Reply-To: <20080726054547.GA20494@untitled>
Eric Wong wrote:
> Brad King <brad.king@kitware.com> wrote:
>> Signed-off-by: Brad King <brad.king@kitware.com>
>
> Acked-by: Eric Wong <normalperson@yhbt.net>
Great, thanks!
>> ---
>> Eric Wong wrote:
>>> I haven't had the chance to look at this. Can anybody else shed more
>>> light on that bug? It's really strange that the tests won't run because
>>> of it. Are you unable to run some git-svn tests or all of them?
>> Just that one fails. All others (including the one in the patch below) pass.
>
> Exactly which test fails for you? Perhaps it's some setting in your
> ~/.subversion/config that's causing it to fail. Maybe we should set
> $HOME and use a clean ~/.subversion/config for git-svn tests regardless
> if that turns out to be the case...
$ cd $gitsrc/t
$ export SVNSERVE_PORT=5432
$ ./t9113-git-svn-dcommit-new-file.sh
* ok 1: start tracking an empty repo
* FAIL 2: create files in new directory with dcommit
mkdir git-new-dir &&
echo hello > git-new-dir/world &&
git update-index --add git-new-dir/world &&
git commit -m hello &&
start_svnserve &&
git svn dcommit
* failed 1 among 2 test(s)
I hacked the test script to log the dcommit output to a file, and I see
this:
Committing to svn://127.0.0.1:5432 ...
Use of uninitialized value in concatenation (.) or string at
/usr/lib/perl5/SVN/Core.pm line 584.
Authorization failed: at $gitsrc/t/../git-svn line 3329
(I replaced my git source dir full path with $gitsrc).
The version of libsvn-perl is: 1.5.0dfsg1-4
Please let me know if you need more info.
I tried moving my ~/.subversion/config out of the way but it makes no
difference. However, I agree we should block the user's home svn config
when running other dcommit tests now that we have auto-props. Perhaps
just using the --config-dir option with an empty directory would be enough.
-Brad
next prev parent reply other threads:[~2008-07-26 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 21:40 [PATCH 1/2] git-svn: teach dcommit about svn auto-props Brad King
2008-07-25 6:00 ` Eric Wong
2008-07-25 15:32 ` [PATCH] " Brad King
2008-07-26 5:45 ` Eric Wong
2008-07-26 14:08 ` Brad King [this message]
2008-08-03 22:02 ` [RFH] - git-svn auth bug (possibly SVN 1.5.0-related) Eric Wong
2008-08-04 14:18 ` Dmitry Potapov
2008-08-04 15:14 ` Dmitry Potapov
2008-08-04 15:30 ` [PATCH] correct access right for git-svn-dcommit test Dmitry Potapov
2008-08-04 15:44 ` Brad King
2008-08-05 3:18 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=488B2FC5.4080801@kitware.com \
--to=brad.king@kitware.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).