On 2/3/14, 2:26 PM, Marc MERLIN wrote:
> On my personal system, I got a new svn and as prompted by "your repo is
> too old", upgraded it to the new format (svn 1.7.13).
You mean working copy, there is no such message about repositories. We support
repositories all the way back to 1.0.
> And now
Howdy,
On my personal system, I got a new svn and as prompted by "your repo is
too old", upgraded it to the new format (svn 1.7.13).
And now I'm very hosed.
legolas:/var/local/scr# svn update
svn: E155037: Previous operation has not finished; run 'cleanup' if it was
interrupted
legolas:/var/loc
Hi everyone.
I got curious to see if they are using my VC6 build of Subversio a.k.a.
Win32SVN. And my suspision it true, it's the Win32SVN 1.8.4 build for
Apache 2.4.x that's is included in the Bitnami Redmine Windows installer.
Building Win32SVN and testing is done against a httpd built at the
Guten Tag Ben Reser,
am Montag, 3. Februar 2014 um 17:49 schrieben Sie:
> Sorry, I thought you realized they'd added it because the link you provided
> documented how to use custom keywords.
No, I totally missed that feature and therefore didn't even read the
documentation again. Thanks for the h
On 2/3/14, 4:19 AM, Branko Čibej wrote:
> The patch isn't needed for 1.8, the feature is now standard in Subversion.
http://subversion.apache.org/docs/release-notes/1.8.html#custom-keywords
On 2/1/14, 1:24 AM, Thorsten Schöning wrote:
> I wasn't criticizing anything. Just thought that expanding $FreeBSD$
> may have been a feature the FreeBSD guys patched into Subversion on
> their own, because some days ago it has been mentioned that FreeBSD
> patches subversion to get some features t
On 2/3/14, 7:33 AM, t...@bbschk.com wrote:
> The TortoiseSVN user group is sure this stems from subversion itself, and
> after
> reading through this mailing list, it seems this problem may be due to the
> Apache version on my system, which happen to be Apache 2.2.25, which as I
> understand it ha
Ah - with a bit of digging around the binary libraries, I can see that it looks
like subversion was still built using vc6, and apache using a mix of 2008
and/or 2010.
This being the case, I'd say that this is a prime candidate for what's causing
the problem (based upon the comments in the secon
Adding a file with a space in the file name and committing it works fine,
however any subsequent edit and commit of this file will fail with:
"Error: Delta source ended unexpectedly"
A file with identical content and name, except with no space in the file
name, works perfectly, I can edit and com
All of the Apache and Subversion binaries came from the Bitnami download. I
could ask their support people exactly what compiler was used if you think that
would help? Anything else I should be asking them at the same time?
Thanks for your time on this
Regards - Steve
-Original Message
Steve Davis writes:
> Response:
>
> svn: E200035: sqlite[S19]: LOCK.lock_token may not be NULL
> svn: E200035: Additional errors:
> svn: E200035: sqlite[S19]: LOCK.lock_token may not be NULL
I can generate this error with the 1.8 client by patching mod_dav_svn to
return 400:
Index: sw/subversio
On Mon, Feb 3, 2014 at 1:09 PM, Mehboob Ahmed wrote:
> hi Nico Kadel-Garcia-2
>
> i want to restrict user to commit any kind of data not individual file a
> complete commit. and i want it because in my office developers commit data
> more than a GB i want them to restrict and commit less than a GB
On 03.02.2014 13:09, Mehboob Ahmed wrote:
> hi Nico Kadel-Garcia-2
>
> i want to restrict user to commit any kind of data not individual file a
> complete commit. and i want it because in my office developers commit data
> more than a GB i want them to restrict and commit less than a GB can you
> p
Hi Ben -
To try to answer as many of the questions you raised as possible:
In the httpd error_log I'm seeing this each time I attempt to lock a file and
fail:
[Mon Feb 03 10:58:52.092999 2014] [dav:error] [pid 2776:tid 1160] [client
xx.xx.xx.xx:x] Tried to attach multiple locks to a resou
I don't have such a tool. I see some pre-commit scripts in the
subversion source tree that might be a starting place, but nothing
aimed at measuring and restricting file size. If you're restricting
the complete diff size, not just individual files, you're going to
need to have a look that adds up a
> -Original Message-
> From: Branko Čibej [mailto:br...@wandisco.com]
> Sent: 02 February 2014 06:42
> To: users@subversion.apache.org
> Subject: Re: expanding custom keywords in dump
>
> On 02.02.2014 04:14, Nico Kadel-Garcia wrote:
> > On Sat, Feb 1, 2014 at 1:07 AM, Ben Reser wrote
On 03.02.2014 13:00, Tony Sweeney wrote:
> It certainly appears to be the case that one of the FreeBSD patches is to
> expand this keyword in Subversion 1.6 and 1.7.
> The actual patches are available here:
>
> svn://svn0.us-east.freebsd.org/ports/head/devel/subversion16
> svn://svn0.us-east.fre
hi Nico Kadel-Garcia-2
i want to restrict user to commit any kind of data not individual file a
complete commit. and i want it because in my office developers commit data
more than a GB i want them to restrict and commit less than a GB can you
provide me a complte pre-commit hook.
so far i have d
> -Original Message-
> From: Thorsten Schöning [mailto:tschoen...@am-soft.de]
> Sent: 01 February 2014 09:24
> To: Subversion
> Subject: Re: expanding custom keywords in dump
>
> Guten Tag Ben Reser,
> am Samstag, 1. Februar 2014 um 07:07 schrieben Sie:
>
> > So if you're going to cri
Hi Bert -
Firstly - is this content posting into a forum somewhere? It might be easier
for me to view it there than in email each time...
Answering your suggestions are easy; I am creating the repository completely
manually using
svnadmin create f:\svn_repository\Testrepo
so, there is no
20 matches
Mail list logo
