e /path1 URL).
If you comment out that 2nd rule then they'll be able to checkout the repo
and get most
everything BUT those things excluded in the /path1 tree by the wildcards.
Would be nice to get that bug fixed at some point as that's a bit of an
ugly discontinuity.
More info on w
sion of 1.14.4.
While the "wandisco.com" link will continue to work for the foreseeable
future, please start using the new link:
https://opensource.cirata.com/
Please let me know if you have any questions?
Cheers.
Doug
--
*Doug Robinson* Senior Product Manager
P +1 925 3
>
> I don't know if it would be possible to relax this restriction but feel
> free to take a look at the code and send a patch to
> d...@subversion.apache.org.
>
> It is not possible to switch back to the old authz parse code in version
> 1.14.
>
> Kind regards,
David:
On Mon, Jul 10, 2023 at 7:41 AM David Aldrich
wrote:
> We currently have around 100 svn users, all of whom are authenticated by
> password.
>
>
>
> Password authentication is fine when using a GUI client, but at the
> command line it becomes tedious. I have tried using Gnome keyring but i
Daniel:
On Tue, May 23, 2023 at 8:58 AM Daniel Sahlberg
wrote:
> From the paths in the error message, it seems you are running your server
> on Windows. There are two different vendors listed on the Binary packages
> webpage [3], you can probably download one of them and configure to use the
> e
Sean:
On Thu, Sep 22, 2022 at 3:59 PM Sean McBride
wrote:
> Our svn repo is about 110 GB for a full checkout. Larger on the server of
> course, with all history, weighting about 142 GB.
>
> There haven't been any performance issues, it's working great.
>
> But now some users are interested in co
Thorsten:
It works as you'd expect so you should only require one SVNParentPath
directive assuming that all of your repositories are within that single
tree.
I suspect the wording needs a bit of a revamp.
Cheers.
Doug
On Tue, Jun 11, 2019 at 2:15 PM Thorsten Schöning
wrote:
> Hi all,
>
> I'm
Tue, Nov 7, 2017 at 6:55 PM, Nico Kadel-Garcia wrote:
>
>
> On Tue, Nov 7, 2017 at 8:16 AM, Doug Robinson
> wrote:
>
>> Kushal:
>>
>> Just as a slight possibility, you might check to see that the SELinux
>> stuff is turned off (use the "sestatus"
Kushal:
It's not you who needs to access it: it is the account that Apache is
running as - at least when running as Apache.
As for "svnserve", it depends on how you've got that setup so to help we
need more details.
Cheers.
Doug
On Tue, Nov 7, 2017 at 8:05 AM, kushal bhattacharya <
bhattacharya
Kushal:
Just as a slight possibility, you might check to see that the SELinux stuff
is turned off (use the "sestatus" command). If it's not disabled/off then
you're going to have to allow the http account to access that data by
setting the appropriate security context throughout all directories f
would really
> appreciate if you can turn the 32-bit CentOS 6 builds back on.
>
> Thanks,
> Alfred
>
>
> On Apr 11, 2017, at 8:26, Doug Robinson
> wrote:
>
> Alfred:
>
> You can blame me for the decision to prune out the 32-bit platform support
> from WANdisco.
Alfred:
You can blame me for the decision to prune out the 32-bit platform support
from WANdisco.
I can easily admit to being premature, but I'm finding less demand for
32-bit and really
question why anyone would continue to run 32-bit at this time? If you
could help me understand
then perhaps I
-8 and the other way around.
>
>
>
> Bert
>
>
>
> *From:* Doug Robinson [mailto:doug.robin...@wandisco.com]
> *Sent:* maandag 10 april 2017 22:17
> *To:* Branko Čibej
> *Cc:* users@subversion.apache.org
> *Subject:* Re: Using UTF8 in repos
://en.wikipedia.org/wiki/Percent-encoding
I'm beginning to wonder if it is even possible (sort of similar to what
Mac/OS does to UTF8 text...)?
Thank you.
Doug
On Mon, Apr 10, 2017 at 8:53 AM, Branko Čibej wrote:
> On 10.04.2017 14:44, Doug Robinson wrote:
> > Folks:
> >
> &
Folks:
I understand that UTF8 is the standard inside of Subversion repositories.
My question is whether having the repository name itself be UTF8? For
instance zh_CN.utf8 ? I googled around a bit and don't see an answer.
If it is supported, is there some Apache setting that is required?
Thanks
Stefan:
Thank you. I've created SVN-4661
<https://issues.apache.org/jira/browse/SVN-4661> for this.
Doug
On Fri, Nov 11, 2016 at 10:55 AM, Stefan Sperling wrote:
> On Fri, Nov 11, 2016 at 10:29:16AM -0500, Doug Robinson wrote:
> > Committers:
> >
> > Can we f
Committers:
Can we file a bug on this? Seems easily reproducible and broken.
Thoughts?
Thanks in advance!
Doug
On Mon, Nov 7, 2016 at 1:14 AM, Quan Liang wrote:
> Hello,
>
>
> We hit an issue when running svn-mergeinfo-normalizer with the following
> error:
>
>
> svn-mergeinfo-normalizer: s
Johan, et. al.:
I have created JIRA SVN-4646
<https://issues.apache.org/jira/browse/SVN-4646> for this issue.
Thank you.
Doug
On Fri, Aug 5, 2016 at 3:11 PM, Johan Corveleyn wrote:
> On Wed, Aug 3, 2016 at 7:23 PM, Doug Robinson
> wrote:
> >
> > Folks:
> >
>
Will do.
On Friday, August 5, 2016, Johan Corveleyn wrote:
> On Wed, Aug 3, 2016 at 7:23 PM, Doug Robinson
> > wrote:
> >
> > Folks:
> >
> > The issue is when create copy/branch/tag from a local working copy
> > path using "svn copy", if the par
Folks:
The issue is when create copy/branch/tag from a local working copy
path using "svn copy", if the parent path of the copying target
does not exist, the "svn copy" command fails with a misleading error
message saying that the copy source (working copy directory) "is out
of date" while that is
Thank you for the update!
On Thu, Jun 16, 2016 at 3:57 PM, Pavel Lyalyakin <
pavel.lyalya...@visualsvn.com> wrote:
> Hello Doug,
>
> On Thu, Jun 16, 2016 at 8:51 PM, Doug Robinson
> wrote:
> >
> > Folks:
> >
> > Does anyone know if (or when) svnbook.red
Folks:
Does anyone know if (or when) svnbook.red-bean.com is going to
update/support SVN 1.9 ? It is still listing SVN 1.7 as "current", SVN 1.8
as "nightly" and SVN 1.9 is nowhere to be seen.
Thank you.
Doug
--
*DOUGLAS B. ROBINSON* SENIOR PRODUCT MANAGER
*T *925-396-1125
*E* doug.robin...@w
One thing to remember: if revision properties are being changed (i.e. the
pre-revprop-change hook allows them) then those changes will need to be
captured and replayed into the loaded repository "somehow" or changes to
revisions prior to -rNEXTREV will be lost.
On Thu, Jun 16, 2016 at 6:49 AM, Joh
;re right, with
enough knowledge you can work around the system.
In this case, they're likely being "smarter than themselves" - since
ultimately they're just delaying
the pain.
But nice points!
Doug
On Tue, Jun 14, 2016 at 1:10 PM, Andrew Reedick wrote:
> > From: Doug Ro
Johan:
On Mon, Jun 13, 2016 at 2:30 PM, Johan Corveleyn wrote:
> On Mon, Jun 13, 2016 at 5:29 PM, Doug Robinson
> wrote:
> >
> > Johan:
> >
> > The "svn lock" enables all people considering working with a file to
> > be able to see who curre
o top-posting on this list. Preferably put your reply inline
> or at the bottom. I've reshuffled your replies a bit. More below. ]
>
> >> On Fri, Jun 10, 2016 at 8:15 PM, Doug Robinson <
> doug.robin...@wandisco.com> wrote:
> >>>
> >>> The dichot
y done "p4 edit" on
> the file.
>
> cheers
> Mark
>
> On Fri, Jun 10, 2016 at 8:15 PM, Doug Robinson > wrote:
>
>> The dichotomy is due to the expression of "knowing who is actually
>> working on a file".
>>
>> I agree that if locking
At least one problem with "svnsync" is that it, by design, does not
propagate the locks. So a sync'd repo cannot replace the sync'd-from
repository without losing all of the locks.
On Thu, Jun 2, 2016 at 9:28 AM, Daniel Shahaf
wrote:
> Michael Schwager wrote on Wed, Jun 01, 2016 at 09:58:18 -05
nd many others
> allow to get your edits in via merging mechanisms of various kinds, so I am
> just curious what the use case scenario would be where locking is
> absolutely essential.
>
> Cheers,
>
> Boris.
>
>
> On Mon, Jun 6, 2016 at 10:19 AM, Jan Keirse wrote:
>
Jan:
Thanks for the note about CVS watches. I was unaware of that feature.
Interesting.
I agree, such a feature would tend to go directly against the requirements
for a DVCS.
Doug
On Mon, Jun 6, 2016 at 10:19 AM, Jan Keirse wrote:
>
> On Mon, Jun 6, 2016 at 3:47 PM, Doug Robinson
&
at changes they were making unless you had
access to their view.
Thank you.
Doug
On Tue, Jun 7, 2016 at 9:54 AM, Branko Čibej wrote:
> On 06.06.2016 15:47, Doug Robinson wrote:
> > Andreas:
> >
> > On Mon, Jun 6, 2016 at 3:50 AM, Andreas Stieger
> > mailto:andrea
PM, Andreas Stieger
wrote:
> Doug,
>
> Doug Robinson wrote:
> > To be more precise, you can know who, in the past, has made changes to
> files and
> > checked those change into the repository. You cannot know who has made
> changes
> > in their working copy and has
Andreas:
On Mon, Jun 6, 2016 at 3:50 AM, Andreas Stieger
wrote:
> > or knowing who is actually working on a file.
>
> Incorrect, this is shown in both TortoiseSVN and svn cli.
>
To be more precise, you can know who, in the past, has made changes to
files
*and*checked those change into the repos
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
> *From: *Doug Robinson
> *Sent: *woensdag 27 april 2016 22:57
> *To: *users@subversion.apache.org
> *Subject: *A verbose option to "svn update"?
>
&g
Folks:
A suggestion from one of our customers:
I see that "svn update" does not have a -v (verbose) option either. That
would be helpful, because verbose output of what svn update is doing file
by file would help narrow in on what is going on much faster. Something
like this:
> svn -v update
Upd
35 matches
Mail list logo
