From 205241edc8c0bbdbda55e9eb5e65b93128d140c2 Mon Sep 17 00:00:00 2001 From: Eitan Adler Date: Sat, 16 Jun 2018 20:20:34 +0000 Subject: [PATCH] Committer guide: remove non-exististant seed reference The seed file referenced does not exist anymore. --- .../articles/committers-guide/article.xml | 59 +++---------------- 1 file changed, 8 insertions(+), 51 deletions(-) diff --git a/en_US.ISO8859-1/articles/committers-guide/article.xml b/en_US.ISO8859-1/articles/committers-guide/article.xml index df65cc3dea..5d4ec1a739 100644 --- a/en_US.ISO8859-1/articles/committers-guide/article.xml +++ b/en_US.ISO8859-1/articles/committers-guide/article.xml @@ -599,11 +599,14 @@ You need a Passphrase to protect your secret key. local repository's UUID has to occur before it is possible to start using it. - The hassle of a local - svnsync mirror probably is not worth it - unless the network connectivity situation or other factors - demand it. If it is needed, see the end of this chapter for - information on how to set one up. + The hassle of a local svnsync mirror + probably is not worth it unless the network connectivity + situation or other factors demand it. Starting + a fresh mirror from empty takes a long time. + Expect a minimum of 10 hours with high speed connectivity. + If international links are involved, expect this to take + four to ten times longer. Another option is to use the + git mirror. @@ -1860,52 +1863,6 @@ U stable/9/share/man/man4/netmap.4 This is a waste. - - Setting up a <application>svnsync</application> - Mirror - - Avoid setting up a svnsync - mirror unless there is a very good reason for it. Such - reasons might be to support multiple local read-only client - machines, or if the network bandwidth is limited. Starting - a fresh mirror from empty would take a very long time. - Expect a minimum of 10 hours for high speed connectivity. - If international links are involved, expect this to take - four to ten times longer. - - A far better option is to grab a seed file. It is large - (~1GB) but will consume less network traffic and take less - time to fetch than a svnsync will. There are several ways - to do this: - - &prompt.user; rsync -va --partial --progress freefall:/home/peter/svnmirror-base-r179637.tbz2 . - - &prompt.user; rsync -va --partial --progress rsync://repoman.freebsd.org:50873/svnseed/svnmirror-base-r215629.tar.xz . - - &prompt.user; fetch ftp://ftp.freebsd.org/pub/FreeBSD/development/subversion/svnmirror-base-r221445.tar.xz - - Extract the file to somewhere like - home/svnmirror/base/. - Then, update it, so that it fetches changes since the last - revision in the archive: - - &prompt.user; svnsync sync file:///home/svnmirror/base - - Now, set that up to run from &man.cron.8;, do - checkouts locally, set up a svnserve server for local - machines to talk to, etc. - - The seed mirror is set to fetch from - svn://svn.freebsd.org/base. The - configuration for the mirror is stored in - revprop 0 on the local mirror. To see - the configuration, try: - - &prompt.user; svn proplist -v --revprop -r 0 file:///home/svnmirror/base - - Use propset to change things. - - Committing High-<acronym>ASCII</acronym> Data