th doesn't exist.
>
> If the address actually resolves to something, it is impossible to say if
> that result is wrong (compared to what you expect). Thus the error message
> can only say "we found a server at the requested address but it doesn't
> want to speak to us"
Den ons 19 apr. 2023 kl 16:47 skrev Ian Miller :
> This is not a problem on the server. As I wrote in my original e-mail,
> there is no network traffic at all between the client and server in the
> failure case.
>
> I have confirmed this by reproducing the problem when the server has its
> networ
O/S to Debian 11, and with it the subversion client to
> version 1.14.1 (r1886195), I started getting
> the following error whenever I tried to access the server:
>
> svn: E175003: The server at 'http://svn/singularis/trunk
> <http://svn/singularis/trunk>' does not supp
> the following error whenever I tried to access the server:
>
> svn: E175003: The server at 'http://svn/singularis/trunk' does not
> support the HTTP/DAV protocol
>
> I checked to see what the network traffic associated with this and found
> that there was none. I get
: The server at 'http://svn/singularis/trunk' does not support the
HTTP/DAV protocol
I checked to see what the network traffic associated with this and found that
there was none. I get the same error attempting make a new checkout. However
if I substitute the server’s IP address into
On Fri, 17 Mar 2023 10:06:18 +, "Kumar, Pradeep (Baker Hughes Contractor)
via users" wrote:
>HI Support Team,
>
>Can someone please respond on this and help us on the below issue.
>
>Regards,
>Pradeep Kumar.
>
You will not get any help until you post a
HI Support Team,
Can someone please respond on this and help us on the below issue.
Regards,
Pradeep Kumar.
From: Pallapati, Raja (Baker Hughes Contractor)
Sent: 16 March 2023 17:26
To: users@subversion.apache.org
Cc: Kumar, Pradeep (Baker Hughes Contractor)
Subject: Need Support for Error
On Thu, 16 Mar 2023 11:55:46 +, "Pallapati, Raja (Baker Hughes Contractor)
via users" wrote:
>Hi Team,
This is not a support forum but a user peer-to-peer mail list!
>
>While doing a check-out in the SVN subversion working copy we are receiving
>"serialized has
Hi Team,
While doing a check-out in the SVN subversion working copy we are receiving
"serialized hash missing terminator" error, and unable to update the content.
This is delaying our work.
Kindly support on this to resolve the issue as early as possible.
[cid:image001.png@01D9582
On Fri, Apr 1, 2022 at 3:08 AM Ashim Kapoor wrote:
>
> Dear Mark,
>
> Could you please answer my query about the isolation level for
> transactions in Subversion?
> Is it always the highest which does not allow for any transaction
> anomalies ? Is there a switch which lowers the isolation level in
Dear Mark,
Could you please answer my query about the isolation level for
transactions in Subversion?
Is it always the highest which does not allow for any transaction
anomalies ? Is there a switch which lowers the isolation level in
Subversion transactions (at the risk of introducing transaction
Dear Mark,
Many thanks for the explanation.
Best Regards,
Ashim
On Thu, Mar 31, 2022 at 4:45 PM Mark Phippard wrote:
>
> On Thu, Mar 31, 2022 at 5:47 AM Ashim Kapoor wrote:
>
> > My fs-type is fsfs.
> >
> > My svn version is 1.10.4
> >
> > I am using a project management tool called Redmine wh
On Thu, Mar 31, 2022 at 5:47 AM Ashim Kapoor wrote:
> My fs-type is fsfs.
>
> My svn version is 1.10.4
>
> I am using a project management tool called Redmine which is the front
> end for SVN projects and which in turn is relying on Apache as a web
> server.
>
> 1. I wish to use :
>
> svnadmin du
But does SVN
support concurrency while using svnadmin dump? I do not mind losing
out information on that ONE commit since the next day that ONE
particular commit will get dumped into my-repository-backup.dump.
Is there any disadvantage to doing an svndump on a LIVE system ? Will
we experience transact
Hello,
thanks for answers.
On Wed, 18 Dec 2019, Daniel Shahaf wrote:
Honza Maly wrote on Tue, 17 Dec 2019 20:04 +00:00:
I don't see it in issue tracker: do you have any plans on adding support
for ssh agent as way to store password encrypted, possibly based on what
Jack Whitham pre
Honza Maly wrote on Tue, 17 Dec 2019 20:04 +00:00:
> I don't see it in issue tracker: do you have any plans on adding support
> for ssh agent as way to store password encrypted, possibly based on what
> Jack Whitham prepared?
>
> https://www.jwhitham.org/2017/03/svn-pass
Hello,
I don't see it in issue tracker: do you have any plans on adding support
for ssh agent as way to store password encrypted, possibly based on what
Jack Whitham prepared?
https://www.jwhitham.org/2017/03/svn-password-store-using-ssh-agent.html
https://github.com/jwhitham/safeu
I
Subversion's missing piece is the patch-review system, agreed. Rietveld
was 11.5 years ago (and Mondrian was 2 years before that - Perforce
admittedly), so we have plenty of things to be inspired by. In the last
year a "shelve" facility has been perfected for Subversion -
https://cwiki.apache.org/
wuzhouhui wrote on Tue, 17 Dec 2019 04:38 +00:00:
> From: "Daniel Shahaf"
> > To do this, I guess you'll want to write a script that automatically
> > commits a patch series along with log messages (from `quilt header -e`)?
> > If you do, please consider publishing it; it's not the first time this
> -Original Messages-
> From: "Daniel Shahaf"
> Sent Time: 2019-12-17 09:29:22 (Tuesday)
> To: wuzhouhui
> Cc: subversion
> Subject: Re: quilt-like feature, to support patch series
>
> wuzhouhui wrote on Mon, 16 Dec 2019 06:57 +00:00:
> > I do
wuzhouhui wrote on Mon, 16 Dec 2019 06:57 +00:00:
> I don't want to commit changes until I think the changes are good enough.
> After
> all, commit to a branch is also a commit.
There is no technical requirement that commits to branches be as stable
as commits to trunk; that's purely a social con
> -Original Messages-
> From: "Daniel Shahaf"
> Sent Time: 2019-12-16 12:37:07 (Monday)
> To: wuzhouhui
> Cc: Subversion
> Subject: Re: quilt-like feature, to support patch series
>
> Nathan Hartman wrote on Sun, Dec 15, 2019 at 22:06:03 -0500:
&
Nathan Hartman wrote on Sun, Dec 15, 2019 at 22:06:03 -0500:
> On Sun, Dec 15, 2019 at 5:03 AM wuzhouhui
> wrote:
>
> > Hi,
> >
> > Can Subversion support patch series, like quilt. So I can split a
> > big change to small pieces before submit all of them, and po
On Sun, Dec 15, 2019 at 5:03 AM wuzhouhui
wrote:
> Hi,
>
> Can Subversion support patch series, like quilt. So I can split a
> big change to small pieces before submit all of them, and post-commit
> review will be more easy.
Not yet. (At least not that I know of.)
Can you u
Hi,
Can Subversion support patch series, like quilt. So I can split a
big change to small pieces before submit all of them, and post-commit
review will be more easy.
Thanks.
On Sun, Dec 8, 2019 at 7:03 PM Nathan Hartman
wrote:
>
> The 1.9.x CHANGES file details what bug fixes (and other improvements)
> there are in 1.9.9, 1.9.10, and 1.9.12. (1.9.8 and 1.9.11 were not
> released.) Only you can make the judgment call if you prefer to stick
> with 1.9.7 or want to use
upported" means that the branch continues to receive bug fixes, with
these being delivered in a point release.
"Unsupported" doesn't mean you can't use it anymore. It just means
that there won't be new point releases in that line.
There are two kinds of releases:
Long Te
> From: Paul Hammant [mailto:p...@hammant.org]
> Sent: den 8 december 2019 11:26
> To: Bo Berglund
> Subject: Re: SVN version - confused about support
>
>
> First of all, get good at backups, and **practice** restores to another
> machine.
>
That is another reall
> From: Paul Hammant [mailto:p...@hammant.org]
> Sent: den 8 december 2019 10:10
> To: Bo Berglund
> Subject: Re: SVN version - confused about support
>
>
> What is stopping you from getting fully up to date with Svn - client and
> server?
>
Well, *how* can I
I am managing 2 svn servers, one on Windows 16 server (VisualSVN) and one on
Ubuntu Server 18.04 LTS (Apache SVN) which is used as a mirror of the first
using svnsync.
On my Windows 7 dev laptop I installed the Collabnet command line svn back when
I started using SVN.
These are all running 1.9
On 06.08.2019 16:08, ken edward wrote:
> Hello,
>
> As I read the SVN LTS policy, it states that support ends 4 years
> after the initial release. Since Subversion 1.9 was released on Aug 5,
> 2015, does that now mean subversion 1.9 will not longer receive
> security patches (
Hello,
As I read the SVN LTS policy, it states that support ends 4 years
after the initial release. Since Subversion 1.9 was released on Aug 5,
2015, does that now mean subversion 1.9 will not longer receive
security patches (now that it is Aug 6th)?
Thank you,
Ed
On Tue, Nov 06, 2018 at 11:09:53AM +0100, Branko Čibej wrote:
> On 06.11.2018 10:20, Dr. Rolf Jansen wrote:
> > Said all this, I would have simply amended this error message by a hint.
> > „... check the URL is pointing to a SVN repository!“.
>
> ... and this hint implies that only the URL could
On 06.11.2018 10:20, Dr. Rolf Jansen wrote:
> For a DAV noob, this error message is IMHO indeed not very helpful. You need
> to know that DAV is heavily based on XML. However, I have my doubts, that the
> other message „does not support the HTTP/DAV protocol“ is much more helpful
&
lained about the
„misleading“ error message „Malformed XML in response,“ when pointing SVN to a
plain web server, one which does not serve a SVN repository.
For a DAV noob, this error message is IMHO indeed not very helpful. You need to
know that DAV is heavily based on XML. However, I have my d
Dr. Rolf Jansen wrote on Tue, 06 Nov 2018 00:27 -0200:
> FYI, RFC 2518 has been obsoleted since 11 years by RFC 4918, and the
> relevant chapter moved to 10.1:
> https://tools.ietf.org/html/rfc4918#section-10.1, and yes there is still
> written "the DAV server MUST return the DAV header". Howeve
> Am 05.11.2018 um 21:57 schrieb Branko Čibej:
>
>>> Am 05.11.2018 um 20:43 schrieb Stefan Sperling:
>>>
>>> On Mon, Nov 05, 2018 at 08:21:20PM -0200, Dr. Rolf Jansen wrote:
>>>> and of course the GitHub server does support HTTP/DAV.
>
> N
> Am 05.11.2018 um 21:55 schrieb Nico Kadel-Garcia :
>
> On Mon, Nov 5, 2018 at 6:28 PM Dr. Rolf Jansen wrote:
>>
>>> Am 05.11.2018 um 20:43 schrieb Stefan Sperling :
>>>
>>> On Mon, Nov 05, 2018 at 08:21:20PM -0200, Dr. Rolf Jansen wrote:
>>>
On 06.11.2018 00:28, Dr. Rolf Jansen wrote:
>> Am 05.11.2018 um 20:43 schrieb Stefan Sperling :
>>
>> On Mon, Nov 05, 2018 at 08:21:20PM -0200, Dr. Rolf Jansen wrote:
>>> and of course the GitHub server does support HTTP/DAV.
No it does not. It does not implement the
On Mon, Nov 5, 2018 at 6:28 PM Dr. Rolf Jansen wrote:
>
> > Am 05.11.2018 um 20:43 schrieb Stefan Sperling :
> >
> > On Mon, Nov 05, 2018 at 08:21:20PM -0200, Dr. Rolf Jansen wrote:
> >> and of course the GitHub server does support HTTP/DAV.
> >
>
> Am 05.11.2018 um 20:43 schrieb Stefan Sperling :
>
> On Mon, Nov 05, 2018 at 08:21:20PM -0200, Dr. Rolf Jansen wrote:
>> and of course the GitHub server does support HTTP/DAV.
>
>> # svn co https://github.com/cyclaero/ContentCGI.git/trunk ContentCGI
>> svn: E
ports system, and I built and installed subversion 1.11.0 from the upstream
sources (thats’s yours) - see below. Needless to say that 1.10.3 does not show
the issue below, and of course the GitHub server does support HTTP/DAV.
If you check the list archives, you'll see that the t
On Mon, Nov 05, 2018 at 08:21:20PM -0200, Dr. Rolf Jansen wrote:
> and of course the GitHub server does support HTTP/DAV.
> # svn co https://github.com/cyclaero/ContentCGI.git/trunk ContentCGI
> svn: E170013: Unable to connect to a repository at URL
> 'https://github.com/cyclae
built and installed subversion 1.11.0 from the upstream
sources (thats’s yours) - see below. Needless to say that 1.10.3 does not show
the issue below, and of course the GitHub server does support HTTP/DAV.
# fetch
http://mirror.nbtelecom.com.br/apache/subversion/subversion-1.11.0.tar.bz2
# tar
Ryan Schmidt wrote on Tue, 21 Aug 2018 14:16 -0500:
> On Aug 21, 2018, at 05:43, Daniel Shahaf wrote:
> > j...@beniston.com wrote on Tue, 21 Aug 2018 09:40 +0100:
> >> This patch adds @ to the end of the filename, to make it work.
> >
> > Thanks jon. Committed with tweaks in r1838539.
>
> It see
On Aug 21, 2018, at 05:43, Daniel Shahaf wrote:
> j...@beniston.com wrote on Tue, 21 Aug 2018 09:40 +0100:
>> This patch adds @ to the end of the filename, to make it work.
>
> Thanks jon. Committed with tweaks in r1838539.
It seems something like this was suggested before:
https://svn.haxx
Nico Kadel-Garcia wrote on Tue, 21 Aug 2018 08:39 -0400:
> On Tue, Aug 21, 2018 at 6:43 AM, Daniel Shahaf
> wrote:
> > j...@beniston.com wrote on Tue, 21 Aug 2018 09:40 +0100:
> > Your MUA seems to have mangled the patch. The easiest way to avoid this
> > is to send patches as attachments named
On Tue, Aug 21, 2018 at 6:43 AM, Daniel Shahaf wrote:
> j...@beniston.com wrote on Tue, 21 Aug 2018 09:40 +0100:
>> This patch adds @ to the end of the filename, to make it work.
>
> Thanks jon. Committed with tweaks in r1838539.
>
>> --- svn_load_dirs.pl.in.old.txt 2018-08-21 09:33:02.557893300
j...@beniston.com wrote on Tue, 21 Aug 2018 09:40 +0100:
> This patch adds @ to the end of the filename, to make it work.
Thanks jon. Committed with tweaks in r1838539.
> --- svn_load_dirs.pl.in.old.txt 2018-08-21 09:33:02.557893300 +0100
>
> +++ svn_load_dirs.pl.in 2018-08-21 09:33:12.33900570
Hi,
It seems svn_load_dirs.pl doesn't support filenames with @ in. You get an
error such as:
's...@2x.png': a peg revision is not allowed here
This patch adds @ to the end of the filename, to make it work.
Cheers,
Jon
--- svn_load_dirs.pl.in.old.txt 2
Daniel Shahaf writes:
> In principle, if svn were built without lz4 (which isn't supposed to be
> allowed by the stock configure) then it won't be able to read or produce
> svndiff2 deltas, which are used on the wire and may be used in FSFS f8
> on-disk data.
If committed r1829344 so that config
> > What should I pass to "configure" to PREVENT detection & usage of lz4
> > library installed in system? `--without-lz4' doesn't work.
Yes, I can reproduce this. '--without-lz4' results in:
configure: lz4 configuration via prefix
checking for LZ4_compress_default in -llz4... yes
which is not
--with-lz4=internal may be what you want.
From what I can gather lz4 is the future so I would be surprised if you can
prevent it’s usage.
Jonathan
> On 13 Apr 2018, at 16:13, Lev Serebryakov wrote:
>
>
> What should I pass to "configure" to PREVENT detection & usage of lz4
> library instal
What should I pass to "configure" to PREVENT detection & usage of lz4
library installed in system? `--without-lz4' doesn't work.
--
// Black Lion AKA Lev Serebryakov
Dear all,
the hook-script check-mime-type.pl [A] doesn't work on the Windows
platform as Windows does not support openfork.
Additionally files/paths with spaces have to be put in quotes.
Plus getting the temp dir should be left to the related Perl functions.
[A]
https://svn.apache.org/v
Unfortunately, it's gotten too expensive for me to do. There are
several factors. The big one is the updated requirements with each
major release. Using more recent new technologies, like serf, and
SQLite are understandable upstream changes, but it means integrating
support for them for a
es, but it means integrating
support for them for another set of RPM's for those components, and
building up the support chains for tools like updated serf, multiplies
the work and threatens other stable tools which might use serf. It's
an old issue for many projects, but the return on inves
I'm trying to use svn:externals to include a directory from repo B in
working copies of repo A. I can change only repo A. The external
directory is huge, but I want only a few immediate children. Is there a
way to get what this implies from svn:externals?
% svn proplist -v .
Properties on '.
Thank you Dave,
I have tried with the binaries compiled from Apache Haus and it works fine.
I'm also using the mod_authnz_sspi.so extension from my friend Ennio.
First I tried the 64bits binaries but it failed, said it was not a valid win32
application !
Finally I decided to use the 32bits binar
On 2015-01-06 10:57, Thierry LEPINE wrote:
Not the official for sure but the most common download site
http://sourceforge.net/projects/wampserver/
http://sourceforge.net/projects/win32svn/
http://www.wampserver.com/en/ says "Once WampServer is installed, you
can manually add aditionals Apach
>> We are only using official binaries to avoid mistake, so with official
>> ones it does not work , that is my status and the reason of my request!
>
> There are no official binaries; the only official release is the source
> code. Where did you get your binaries? Did you get Apache and
> Subver
Thierry LEPINE writes:
> We are only using official binaries to avoid mistake, so with official
> ones it does not work , that is my status and the reason of my request!
There are no official binaries; the only official release is the source
code. Where did you get your binaries? Did you get A
> Locking does work in 1.8. This problem has only ever been reported by
> people using Windows and it appears to be some binary incompatibity
> between Apache and Subversion caused by the way they have been compiled.
> Using different binaries has been reported to solve the problem.
For sure, but
Thierry LEPINE writes:
> We have switched last week to
> - subversion 1.8.11 server (Msi) over wamp 2.5 (apache server 2.4.9 - 32bits
> ) on Windows Server 2012 64bits
> The error-log on the apache server contains
> [Tue Jan 06 14:34:39.169863 2015] [dav:error] [pid 3760:tid 1164] [client
>
What we had from 2006 :
- subversion 1.3.0 server (Msi) over apache web serveur 2.0.55 on Windows SBS
2003 32bits
- Tortoise SVN 1.8.x clients connected to subversion on https
We could do every svn operation and also get / release lock, commit with lock.
We have switched last week to
- subver
I am looking forward to it.
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
连接SQL Server
DBconnect.Provider = "SQLOLEDB.1"
DBconnect.ConnectionString = "DATABASE= ;SERVER= ;UID= ;PWD= ;"
或者可以使用 DBconnect.Open "SERVER" , "USERID" , "PASSWORD"
DBConnect.Open/
# Non-members may check out a read-only working copy anonymously over HTTP.
svn checkout http://svnbook.googlecode.com/svn/trunk/ svnbook-read-only
compatibility work to support older servers was harder than I
anticipated. But a lot of the missing ground work that made it that difficult
back then is now implemented)
I’m not sure which Subversion client you use for your ‘svn ls’, but recently I
compared an 1.6 an 1.8 client over http:// and
ng copies, "depth=dirs" probably
doesn't make much sense.
> Once you've defined what "depth=dirs" means for all the commands that
support depth, you're about 10% done ... you'd have to review the
implementation for every use of the depth parameter and ei
aces, not just in "svn list";
whatever enhancement you come up with must at least fit the other uses.
Depth was invented to describe sparse working copies, and was only later
adapted to other commands. For sparse working copies, "depth=dirs"
probably doesn't make much sense.
On
On May 3, 2014, at 22:32, Ryan Schmidt wrote:
> On May 3, 2014, at 21:25, Dan Ellis wrote:
>
>> Its really a performance concern. We need to do this fairly regularly on a
>> large repository (over a WAN I might add) and asking the server for all
>> files and directories when we really only ne
On May 3, 2014, at 21:25, Dan Ellis wrote:
> Its really a performance concern. We need to do this fairly regularly on a
> large repository (over a WAN I might add) and asking the server for all files
> and directories when we really only need a directory listing is really a huge
> time sink (
On Sat, May 3, 2014 at 7:16 PM, Ryan Schmidt wrote:
>
> On May 3, 2014, at 20:13, Dan Ellis wrote:
>
> > The svn command line list command currently accepts --depth arguments of
> files, infinity, and immediates (and empty, but that is really a no-op).
> I'm in need of being able to list directo
On May 3, 2014, at 20:13, Dan Ellis wrote:
> The svn command line list command currently accepts --depth arguments of
> files, infinity, and immediates (and empty, but that is really a no-op). I'm
> in need of being able to list directory entries only in a repository, but I'm
> not sure there
Hi,
The svn command line list command currently accepts --depth arguments of
files, infinity, and immediates (and empty, but that is really a no-op).
I'm in need of being able to list directory entries only in a repository,
but I'm not sure there is any good way to accomplish that as-is. I've
se
Dear Stefan，
Thank you for your quick and detailed explanations.
I got it. And we don't need professional support.
Best Regards
She Hanbing (Eric She)
ABeam Global Development Centre
4F, Building.23,498# GuoShouJing Rd. Pudong,Shanghai, 2
er 2003, before upgrade, we have some
> concerns and would like to consult with you:
>
> 1. Does SVN support Windows 2008 R2 (x86)?
> 2. If no, which version can support it? And how to upgrade it to the
> Support-Version?
> 3. If there is a support period for
. Does SVN support Windows 2008 R2 (x86)?
2. If no, which version can support it? And how to upgrade it to the
Support-Version?
3. If there is a support period for SVN in Windows 2003 (x86)? If yes,
when is the support end date?
4. If there is a support period for SVN "Su
Adam Daughterson writes:
> On 12/05/2013 10:25 AM, Les Mikesell wrote:
>> On Thu, Dec 5, 2013 at 11:07 AM, Adam Daughterson
>> wrote:
>>> Checkouts on the local disk do work, and checkouts to Samba shares (not
>>> Windows) work as well. I've only found operations on WC living on a Windows
>>>
On Dec 5, 2013, at 11:32 AM, Adam Daughterson
wrote:
> On 12/05/2013 10:25 AM, Les Mikesell wrote:
>> On Thu, Dec 5, 2013 at 11:07 AM, Adam Daughterson
>> wrote:
>>> Checkouts on the local disk do work, and checkouts to Samba shares (not
>>> Windows) work as well. I've only found operations
{st_mode=S_IFREG|0755, st_size=0, ...}) = 0
> close(3)= 0
> write(2, "svn: E200030: sqlite[S22]: large"..., 58svn: E200030:
> sqlite[S22]: large file support is disabled
> ) = 58
You could try to run Process Monitor during the access of your te
On Thu, Dec 5, 2013 at 11:32 AM, Adam Daughterson
wrote:
>
>>> Checkouts on the local disk do work, and checkouts to Samba shares (not
>>> Windows) work as well. I've only found operations on WC living on a
>>> Windows
>>> share to not work.
>>
>> This is starting to sound like one of those "if i
On 12/05/2013 10:25 AM, Les Mikesell wrote:
On Thu, Dec 5, 2013 at 11:07 AM, Adam Daughterson
wrote:
Checkouts on the local disk do work, and checkouts to Samba shares (not
Windows) work as well. I've only found operations on WC living on a Windows
share to not work.
This is starting to soun
On Thu, Dec 5, 2013 at 11:07 AM, Adam Daughterson
wrote:
>
> Checkouts on the local disk do work, and checkouts to Samba shares (not
> Windows) work as well. I've only found operations on WC living on a Windows
> share to not work.
This is starting to sound like one of those "if it hurts, don't
0030: sqlite[S22]: large"..., 58svn: E200030: sqlite[S22]:
large file support is disabled
) = 58
That's odd. The open, fstat64, close all succeed so what triggered the
error? The message corresponds to SQLITE_NOLFS in the sqlite
amalgamation, so I guess it's the code in findInodeIn
/wc.db",
> {st_mode=S_IFREG|0755, st_size=0, ...}) = 0
> open("/mnt/cns/Users/adaughterson/tmp/Tools/.svn/wc.db",
> O_RDWR|O_CREAT|O_LARGEFILE|O_CLOEXEC, 0644) = 3
> fstat64(3, {st_mode=S_IFREG|0755, st_size=0, ...}) = 0
> close(3) = 0
&
On 2013-12-05 1:16 AM, David Kelly wrote:
Repeat adding -s to ls. I think that will list the position of EOF. I
think you have a sparse file which physically occupies 119k but has
massive holes which have yet to be assigned disk blocks.
It's the other way around-- ls -l shows the logical lengt
yThing/trunk myThing
> svn: E200030: sqlite[S22]: large file support is disabled
>
> I've verified that I can perform this same operation on a Linux samba share
> with the new clients, and nothing has changed on the Windows side of things.
>
> The really interesting part
On Dec 4, 2013, at 7:54 PM, Adam Daughterson
wrote:
> The really interesting part is that the db file is only 119k, so that's nice
> and weird...
>
> me@here:myThing$ ls -alh .svn
> total 144K
> drwxr-xr-x 4 adaughterson adaughterson 4.0K 2013-12-02 15:42 .
> drwxr-xr-x 9 adaughterson adaug
large file support is disabled
I've verified that I can perform this same operation on a Linux samba share
with the new clients, and nothing has changed on the Windows side of things.
The really interesting part is that the db file is only 119k, so that's nice
and weird...
me@here:myThin
> -Original Message-
> From: Ben Reser [mailto:b...@reser.org]
> Sent: zaterdag 2 november 2013 23:58
> To: d...@sent.com; users@subversion.apache.org
> Subject: Re: IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6
>
> On 11/2/13 10:48 AM, d...@sent.c
On 11/2/13 10:48 AM, d...@sent.com wrote:
> reading @
>
> @
>
> http://www.wandisco.com/svnforum/threads/54273-svn-error-when-checkout-from-ipv6-url
>
> IPv6 support is (?) in svn v>1.8
That post is actually not particularly helpful. It looks like there
> suggest you take that question to the APR developers; it's
> d...@apr.apache.org.
done, @ http://www.mail-archive.com/dev%40apr.apache.org/msg25430.html
thx!
On Sat, Nov 2, 2013, at 01:09 PM, Branko Čibej wrote:
> Also, which version of APR you're using (and how it was compiled) is
> fairly important. You can determine the former by running the command
>
> svn --version --verbose
>
> with the 1.8.x client, or
>
> apr-1-config --version
>
> a
On 02.11.2013 21:06, d...@sent.com wrote:
> On Sat, Nov 2, 2013, at 10:55 AM, Mark Phippard wrote:
>> I believe support for IPv6 in the SVN client is based solely on how the
>> APR library was compiled. It has to have IPv6 support compiled in as it
>> does the TCP connections
On 02.11.2013 20:00, Dave Huang wrote:
> On Nov 2, 2013, at 12:48, d...@sent.com wrote:
>
>> With my resolvers set to IPv6
>>
>> cat /etc/resolv.conf
>> nameserver 2600:3c01::2
>> nameserver 2600:3c01::3
>> options rotate
>> in short, 'everything' IPv6 w
On Sat, Nov 2, 2013, at 10:55 AM, Mark Phippard wrote:
> I believe support for IPv6 in the SVN client is based solely on how the
> APR library was compiled. It has to have IPv6 support compiled in as it
> does the TCP connections etc.
It appears to be a problem with SVN's ability t
On Nov 2, 2013, at 12:48, d...@sent.com wrote:
> With my resolvers set to IPv6
>
> cat /etc/resolv.conf
> nameserver 2600:3c01::2
> nameserver 2600:3c01::3
> options rotate
> in short, 'everything' IPv6 works here ... except for subversion,
FWIW
I believe support for IPv6 in the SVN client is based solely on how the APR
library was compiled. It has to have IPv6 support compiled in as it does the
TCP connections etc.
> On Nov 2, 2013, at 1:48 PM, d...@sent.com wrote:
>
> With my resolvers set to IPv6
>
>cat /
1 - 100 of 268 matches
Mail list logo
