On Tue, Jun 5, 2012 at 8:54 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name>wrote:
> Stefan Sperling wrote on Mon, Jun 04, 2012 at 14:52:59 +0200:
> > On Mon, Jun 04, 2012 at 05:50:11AM -0700, Skylar Thompson wrote:
> > > It looks like ages ago I added an svn:keywords line in the autoprop
> > > section of ~/.subversion/config and had since forgotten about it.
> >
> > Ah, that explains it. Thanks!
>
> Should we patch the reproduction template to account for this, then?
>
> Index: publish/docs/community-guide/repro-template.sh
> ===================================================================
> --- publish/docs/community-guide/repro-template.sh (revision 1339099)
> +++ publish/docs/community-guide/repro-template.sh (working copy)
> @@ -22,6 +22,11 @@
> SVNADMIN=`which svnadmin`
> fi
>
> +# Make sure we don't use $HOME/.subversion/.
> +SVN="${SVN} --config-dir=./svn-repro-config-dir"
> +SVNADMIN="${SVNADMIN} --config-dir=./svn-repro-config-dir"
> +SVNSERVE="${SVNSERVE} --config-dir=./svn-repro-config-dir"
> +
> # Use English output.
> LC_ALL=C; export LC_ALL
>
>
> (Ideally we would have "--no-config-dir" of some sort, but the above
> works with existing released code
>
>
>
I'd like to put a big vote up for "--no-config-dir" When verifying a new
user's account against a common repository, I *do not want* Subversion to
check against or touch my existing $HOME/.subversion, or anyone else's. It
would be particularly useful for the Nagios "check_svn" utility, where
using saved configurations would conflict with the command line operations
and potentially provide the "nagios" user..... inappropriate access to the
tested repository on an ongoing basis.
Received on 2012-06-06 03:07:36 CEST