Error E170013: The server unexpectedly closed the,connection.
Hi, A user of SmartSVN with SVN 1.14 reports a problem in connecting to the SVN server while it works in the browser. I redirected him to use our self-built SVN 1.14 binaries and he reports following error MacBook-Pro:user$ svn update Updating '.': *svn: E170013*: Unable to connect to a repository at URL ' https://svn.workapps.com/svn/OneWorkbook/trunk' *svn: E120108*: Error running context: The server unexpectedly closed the connection. How to diagnose the problem? Is it a problem of SVN or the server? Thanks in advance. -- Best regards, Thomas Singer
Re: svn.haxx.se is going away
On Wed, 25 Nov 2020, Nathan Hartman wrote: I would suggest a CNAME to svn-haxx.apache.org, which Infra would further CNAME to (say) svn-qavm. That would mean Mr Stenberg wouldn't ever need to alter his CNAME record, while the ASF could repoint svn-haxx.a.o at-will over time. Today, the "301 mapping server" could be svn-qavm, but maybe we'd do something different in a few years. That sounds like a perfect solution from my point of view. I've admined the haxx.se domain for two decades already and for all I know, I will probably do it for a few more so the svn.haxx.se name should be okay for a good while ahead. If you do what you need to do in your end to get everything setup, and when you think you're good to go I'll be ready to turn it into a CNAME on your call. There's no immediate hurry, the machine will be running for a while longer, most likely through the rest of the year and a little more. I'll leave the rsync setup there for now if you want to update anything during the transition period. Some old-timers may remember: I was involved in the Subversion project early on, and I did a few commits and it was in that period I figured I'd setup an archive of the lists to make it easier to search and link to posts. I then dropped off the project, but I've left the archive running. The simple reason I stop now is that this service runs on a very old physical machine that we fear will die at some point and we're moving everything over elsewhere before that happens, and I just couldn't muster the will to do the necessary work for this site to do the jump. I hope you understand. The fact that you want to work on maintaining the archive at least tells me it has been a good service and that it has servered the project - and that warms my heart. -- / daniel.haxx.se
Re: svn.haxx.se is going away
Hi all, I'm CC'ing Daniel Stenberg of svn.haxx.se fame, as it will be easier to have everyone in the loop. Excuse me for using last names but we have at least 3 Daniel S's in the conversation :-) Just to update everyone, Mr. Stenberg very kindly setup a rsync that allowed Mr. Sahlberg and I to download the entire svn.haxx.se site. This was a 6.5 GB download of ~450,000 files comprising all the mbox files and all the .shtml files, which are generated by hypermail 2.2.0. This backup should alleviate any concerns about preserving the URLs found throughout our code, site, logs, and the mail archives themselves. @Mr. Stenberg, would the following be agreeable to you: On Wed, Nov 25, 2020 at 10:41 AM Greg Stein wrote: > > I would suggest a CNAME to svn-haxx.apache.org, which Infra would further > CNAME to (say) svn-qavm. That would mean Mr Stenberg wouldn't ever need to > alter his CNAME record, while the ASF could repoint svn-haxx.a.o at-will > over time. Today, the "301 mapping server" could be svn-qavm, but maybe > we'd do something different in a few years. > Cheers, Nathan
Re: svn.haxx.se is going away
On Wed, Nov 25, 2020 at 8:52 AM Daniel Sahlberg wrote: >... > As for the question in your other mail (the reply to Daniel Shahaf) > regarding the desire to keep the URLs. My initial question to Daniel > Stenberg was if they would consider CNAME:ing svn.haxx.se to my server > and he seemed ok with that, however we have not reached a formal agreement. > I assume it would be even easier for him to CNAME it to a server provided > by the ASF. > I would suggest a CNAME to svn-haxx.apache.org, which Infra would further CNAME to (say) svn-qavm. That would mean Mr Stenberg wouldn't ever need to alter his CNAME record, while the ASF could repoint svn-haxx.a.o at-will over time. Today, the "301 mapping server" could be svn-qavm, but maybe we'd do something different in a few years. Cheers, -g
Re: Source Code Build Errors?
Den tis 24 nov. 2020 kl 19:06 skrev Alan Fry : > Having some time finally to work on building SVN (thanks all who helped me > get this far), I setup a VM with Ubuntu. (Also setup a Windows 10 machine > w/ Visual studio, but have not started on that effort yet). > As for building on Windows, I would recommend to get the TortoiseSVN sources and go from there. It imports the official subversion repository using svn:externals (currently https://svn.apache.org/repos/asf/subversion/tags/1.14.0) and it has some very good building instructions - just downloading a bunch of tools and then running nant. It builds the CLI tools in addition to all the GUI stuff from TSVN. I haven't tried to run the test suite though.
Re: svn.haxx.se is going away
Den ons 25 nov. 2020 kl 07:22 skrev Greg Stein : > On Thu, Nov 12, 2020 at 10:47 AM Daniel Sahlberg < > daniel.l.sahlb...@gmail.com> wrote: > >> Den tors 5 nov. 2020 kl 15:31 skrev Julian Foad : >> >>> Main point: Thanks to everyone helping this preservation effort. >>> >>> > * updating the 63+87 links in the site and source to point to links >>> hosted on ASF hardware >>> > >>> Observation: s/hardware/domain/. While the ASF has long promoted "on our >>> own hardware", the more critical and often under-valued key to keeping >>> control of one's Internet assets is "on our own domain name". That's >>> assumed in this context, but something to keep in mind elsewhere. >>> >> >> Agreeing with Julian's point on "on our own domain name", however this is >> as it is. If we can get an agreement regarding keeping svn.haxx.se >> pointing to a server where, at least, the old mailing list archive is >> available then we would be better off. >> >> Could ASF provide this server space (basically a VirtualHost)? The >> archive is about 6.5 GB so it is not a huge amount. >> > > Well, svn-qavm.a.o already exists, and DShahaf has already moved content > there. I think the larger concern is if a "redirect mapping" server were > stood up to capture svn.haxx.se clicks and redirect them, then to ... > where? > > In INFRA-20213, we noted that mail-archives.a.o is going away. Our end > goal is lists.a.o, so that is where the content needs to be migrated. > > We (Infra) have a lot of issues with loading archival data onto lists.a.o. > We have a bunch of it, there are permalink issues, and it is going to a > long slog. So there is also the issue for the svn community to determine > whether it wants to fill the gap or maybe throw in some volunteer infra > time to help sort through our backlog. (access to archival messages has > generally been lower priority; volunteers welcome) > > No issues on the storage. It's all about servicing up a landing page for > $oldHaxxLink.ยด > Wouldn't the easiest way be to just serve up the old HTML pages (that has been generated from the mbox:es by hypermail)? Then we won't need to consider permalinks, redirects, etc. There would be some duplicate storage but a lot less time required to set it up. No need to have it updated with recent mails, just put a note that mails newer than [some date] can be found at lists.a.o. As for the question in your other mail (the reply to Daniel Shahaf) regarding the desire to keep the URLs. My initial question to Daniel Stenberg was if they would consider CNAME:ing svn.haxx.se to my server and he seemed ok with that, however we have not reached a formal agreement. I assume it would be even easier for him to CNAME it to a server provided by the ASF. Kind regards, Daniel Sahlberg
