Date: Thu, 04 Oct 2012 11:08:20 -0400 From: Greg Larkin <glarkin@FreeBSD.org> To: Howard Leadmon <howard@leadmon.net> Cc: freebsd-questions@FreeBSD.org, Trond.Endrestol@fagskolen.gjovik.no Subject: Re: Trouble updating Sources via subversion? Message-ID: <506DA664.5010707@FreeBSD.org> In-Reply-To: <034801cda23c$fe73c5b0$fb5b5110$@leadmon.net> References: <031201cda233$f7fd3210$e7f79630$@leadmon.net> <alpine.BSF.2.00.1210041536200.26151@mail.fig.ol.no> <034001cda23a$df12b340$9d3819c0$@leadmon.net> <506D9CD6.40405@FreeBSD.org> <034801cda23c$fe73c5b0$fb5b5110$@leadmon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/4/12 10:31 AM, Howard Leadmon wrote: >> >> [...] >> >> Hi Howard, >> >> I know this doesn't answer the question about the svn problems >> you've been encountering, but have you considered using portsnap >> to keep your /usr/ports tree up to date? One of it's advantages >> is that you'll save space by not housing the /usr/ports/.svn >> directory created by "svn checkout". >> >> Once portsnap has populated the tree the first time, it's >> super-fast keeping it up to date, and it's easily invoked from a >> nightly cron job. >> >> Hope that helps, Greg >> > In theory that seems like an OK idea, but I figured I would > probably setup a mirror as I update a bunch of servers, so getting > one to house a local copy for the others to sync to seemed like a > decent goal. > > Also, and by all means correct me if I am wrong, but I want to sync > not only with /usr/ports, but also with /usr/src, and /usr/doc, and > I was under the impression that portsnap was only for ports, which > would still leave me holding the bag on the OS sources and such.. > > > --- Howard Leadmon - howard@leadmon.net > Unless you're trying to save bandwidth (and probably not too much anyway), I wouldn't set up a local portsnap mirror. It's very fast to sync from multiple machines. If you need to guarantee that every machine has the exact same /usr/ports, then you can rsync from a designated master to the others. As you mentioned, portsnap is only for the ports tree. For production machines, I use freebsd-update to keep /usr/src up to date, but that's only necessary when new base system patches are released. If you're tracking -STABLE or -CURRENT, then I agree that svn is the right solution. To solve the node conflict problem, here are some suggestions/questions to ponder: - - Check that your system clock is in sync with a good NTP source - - Make absolutely sure that a cron job or some other hidden process is not touching the /usr/ports, /usr/src and /usr/doc directories (mentioned by a previous poster) - - To verify that the directories haven't changed, try running this command immediate after the initial checkout: find /usr/ports/ -type f -print | sort | xargs md5 > /tmp/ports-md5-1.txt Wait a while, then run these commands: find /usr/ports/ -type f -print | sort | xargs md5 > /tmp/ports-md5-2.txt diff /tmp/ports-md5-[12].txt What is the output of the diff command? - - Does this problem show up consistently on more than one of your machines or just a subset? Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBtpmQACgkQ0sRouByUApDWCQCeNdJMNHM8dDbk+5KR4kdTHaaI b+kAoJn5F+w9BI2uWoKgeSvYIzF82etJ =uQPq -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?506DA664.5010707>