Re: svn.haxx.se is going away
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. Cheers, Greg Stein Infrastructure Administrator, ASF
Re: svn.haxx.se is going away
Hey Daniel, I think the best place for this content is on mbox-vm.a.o. That is where we have our permanent list archives in mbox format. We can then arrange to ship them off to lists.a.o. If you concur, then I'll ask the team to get you access. You can preserve all the data you want into your homedir, and we can sort from there. You indicate a desire to maintain URLs. Do you have some ideas on that? Would we be able to have the DNS record for svn.haxx.se CNAME'd to one of our boxes which simply generates 301 responses? (from your email, it implies we don't have confirmation of that yet?) Cheers, Greg Stein Infrastructure Administrator, ASF On Tue, Nov 24, 2020 at 7:04 PM Daniel Shahaf wrote: > Nathan Hartman wrote on Tue, 24 Nov 2020 21:27 +00:00: > > On Tue, Nov 24, 2020 at 2:56 AM Daniel Sahlberg > > wrote: > > > Den tors 12 nov. 2020 kl 17:46 skrev Daniel Sahlberg < > daniel.l.sahlb...@gmail.com>: > > >> Could ASF provide this server space (basically a VirtualHost)? The > archive is about 6.5 GB so it is not a huge amount. > > > > > > Any thoughts on this? > > > > I am looking into this; waiting for a reply... > > In the circumstances — it's Nov 25 and the site says it'll be taken down > "in November 2020", not specifying a date — I'd say, better ask > forgiveness than permission. Let's go ahead and grab all the data we > need to stand up the site (we have the mboxes, but not the mapping of > *.shtml files to message-id's, nor any of the HTML/CSS/images), and if > possible, also set it up (on svn-qavm.a.o or wherever) to ensure we've > got everything and to prepare for a DNS repointing, if Daniel agrees. > We can figure out the "paperwork", Puppet PRs, etc., later. > > I'd say the highest priority is to save the mapping of .shtml URLs to > message-id's (which are available as comments in the source HTML), > whether via a recursive wget(1) invocation, or by asking Daniel to run > an appropriate grep, or however else. Without that info, we won't be > able to preserve old URLs. > > Maybe there's also a button we can press to sic the archive.org spider > on svn.haxx.se. > > (We can't derive the message<->.shtml mapping from the mboxes we have. > I only grabbed mboxes through the transition to ASF; for anything after > that point, the order of .shtml files would be the order in which list > mails reached haxx.se's MX, and we have no backups of that info.) > > Cheers, > > Daniel > > P.S. Yes, it's a bit https://m.xkcd.com/2337/ of me to refer to both > Daniel and Daniel as "Daniel". :) >
Re: svn.haxx.se is going away
On Tue, Nov 24, 2020 at 8:04 PM Daniel Shahaf wrote: > Nathan Hartman wrote on Tue, 24 Nov 2020 21:27 +00:00: > > On Tue, Nov 24, 2020 at 2:56 AM Daniel Sahlberg > > wrote: > > > Den tors 12 nov. 2020 kl 17:46 skrev Daniel Sahlberg < > daniel.l.sahlb...@gmail.com>: > > >> Could ASF provide this server space (basically a VirtualHost)? The > archive is about 6.5 GB so it is not a huge amount. > > > > > > Any thoughts on this? > > > > I am looking into this; waiting for a reply... > > In the circumstances — it's Nov 25 and the site says it'll be taken down > "in November 2020", not specifying a date — I'd say, better ask > forgiveness than permission. Let's go ahead and grab all the data we > need to stand up the site (we have the mboxes, but not the mapping of > *.shtml files to message-id's, nor any of the HTML/CSS/images), and if > possible, also set it up (on svn-qavm.a.o or wherever) to ensure we've > got everything and to prepare for a DNS repointing, if Daniel agrees. > We can figure out the "paperwork", Puppet PRs, etc., later. Just FYI it looks like yes, we will get the server space, but I don't know details yet. The 1st order of business is to save the data... @Daniel Sahlberg since you've previously reached out to the operator of svn.haxx.se about saving the site, could you perhaps ask for a way to download the data efficiently? Nathan
Re: Source Code Build Errors?
Branko Čibej wrote on Tue, 24 Nov 2020 18:44 +00:00: > On 24.11.2020 19:05, Alan Fry wrote: > > 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). > > > > Knowing little about linux, I managed to get this far, the results of > > make checks > > > > Last part of the make check: > > > > At least one test FAILED, checking > > /home/svn/Documents/subversion-1.14.0/tests.log > > FAIL: error-test 3: test svn_error_symbolic_name > > FAIL: locks-test 14: lock/unlock when 'write-lock' couldn't be obtained > > FAIL: commit_tests.py 48: set revision props during remote property edit > > FAIL: prop_tests.py 1: write/read props in wc only (ps, pl, pdel, pe) > > FAIL: prop_tests.py 16: property operations on a URL > > FAIL: update_tests.py 38: update --accept automatic conflict resolution > > Summary of test results: > > 2508 tests PASSED > > 162 tests SKIPPED > > 81 tests XFAILED (17 WORK-IN-PROGRESS) > > 6 tests FAILED > > Python version: 3.8.5. > > SUMMARY: Some tests failed > > > > Are these errors something I need to dig into, indicating that my > > build is no good? I was reading in the "INSTALL" document, there is > > mention that some errors are expected. Is there a way to determine if > > these are expected errors? > > Expected test failures are tagged as XFAIL, not FAIL. So these are > "real" failures. Also the summary line would read "All tests succeeded" > if there were only expected failures. > > You should look at tests.log (the test driver hepfully prints the whole > path) to see why those tests failed, it could be something trivial. It's > not likely that there's a problem with the code, we'd have noticed that. Since the test harness existed successfully, you can also look in fails.log, which is created next to tests.log at the end of a test run, and contains only "real" failures. Cheers, Daniel
Re: svn.haxx.se is going away
Nathan Hartman wrote on Tue, 24 Nov 2020 21:27 +00:00: > On Tue, Nov 24, 2020 at 2:56 AM Daniel Sahlberg > wrote: > > Den tors 12 nov. 2020 kl 17:46 skrev Daniel Sahlberg > > : > >> Could ASF provide this server space (basically a VirtualHost)? The archive > >> is about 6.5 GB so it is not a huge amount. > > > > Any thoughts on this? > > I am looking into this; waiting for a reply... In the circumstances — it's Nov 25 and the site says it'll be taken down "in November 2020", not specifying a date — I'd say, better ask forgiveness than permission. Let's go ahead and grab all the data we need to stand up the site (we have the mboxes, but not the mapping of *.shtml files to message-id's, nor any of the HTML/CSS/images), and if possible, also set it up (on svn-qavm.a.o or wherever) to ensure we've got everything and to prepare for a DNS repointing, if Daniel agrees. We can figure out the "paperwork", Puppet PRs, etc., later. I'd say the highest priority is to save the mapping of .shtml URLs to message-id's (which are available as comments in the source HTML), whether via a recursive wget(1) invocation, or by asking Daniel to run an appropriate grep, or however else. Without that info, we won't be able to preserve old URLs. Maybe there's also a button we can press to sic the archive.org spider on svn.haxx.se. (We can't derive the message<->.shtml mapping from the mboxes we have. I only grabbed mboxes through the transition to ASF; for anything after that point, the order of .shtml files would be the order in which list mails reached haxx.se's MX, and we have no backups of that info.) Cheers, Daniel P.S. Yes, it's a bit https://m.xkcd.com/2337/ of me to refer to both Daniel and Daniel as "Daniel". :)
Re: svn.haxx.se is going away
On Tue, Nov 24, 2020 at 2:56 AM Daniel Sahlberg wrote: > Den tors 12 nov. 2020 kl 17:46 skrev Daniel Sahlberg < > daniel.l.sahlb...@gmail.com>: > >> Could ASF provide this server space (basically a VirtualHost)? The >> archive is about 6.5 GB so it is not a huge amount. >> > > Any thoughts on this? > I am looking into this; waiting for a reply... Thanks for the nudge. Nathan
Re: Source Code Build Errors?
On 24.11.2020 19:05, Alan Fry wrote: 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). Knowing little about linux, I managed to get this far, the results of make checks Last part of the make check: At least one test FAILED, checking /home/svn/Documents/subversion-1.14.0/tests.log FAIL: error-test 3: test svn_error_symbolic_name FAIL: locks-test 14: lock/unlock when 'write-lock' couldn't be obtained FAIL: commit_tests.py 48: set revision props during remote property edit FAIL: prop_tests.py 1: write/read props in wc only (ps, pl, pdel, pe) FAIL: prop_tests.py 16: property operations on a URL FAIL: update_tests.py 38: update --accept automatic conflict resolution Summary of test results: 2508 tests PASSED 162 tests SKIPPED 81 tests XFAILED (17 WORK-IN-PROGRESS) 6 tests FAILED Python version: 3.8.5. SUMMARY: Some tests failed Are these errors something I need to dig into, indicating that my build is no good? I was reading in the "INSTALL" document, there is mention that some errors are expected. Is there a way to determine if these are expected errors? Expected test failures are tagged as XFAIL, not FAIL. So these are "real" failures. Also the summary line would read "All tests succeeded" if there were only expected failures. You should look at tests.log (the test driver hepfully prints the whole path) to see why those tests failed, it could be something trivial. It's not likely that there's a problem with the code, we'd have noticed that. -- Brane
Source Code Build Errors?
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). Knowing little about linux, I managed to get this far, the results of make checks Last part of the make check: At least one test FAILED, checking /home/svn/Documents/subversion-1.14.0/tests.log FAIL: error-test 3: test svn_error_symbolic_name FAIL: locks-test 14: lock/unlock when 'write-lock' couldn't be obtained FAIL: commit_tests.py 48: set revision props during remote property edit FAIL: prop_tests.py 1: write/read props in wc only (ps, pl, pdel, pe) FAIL: prop_tests.py 16: property operations on a URL FAIL: update_tests.py 38: update --accept automatic conflict resolution Summary of test results: 2508 tests PASSED 162 tests SKIPPED 81 tests XFAILED (17 WORK-IN-PROGRESS) 6 tests FAILED Python version: 3.8.5. SUMMARY: Some tests failed Are these errors something I need to dig into, indicating that my build is no good? I was reading in the "INSTALL" document, there is mention that some errors are expected. Is there a way to determine if these are expected errors?
