Date: Mon, 23 Jul 2012 18:25:13 +1000 From: John Marshall <john.marshall@riverwillow.com.au> To: "Simon L. B. Nielsen" <simon@freebsd.org> Cc: ports@freebsd.org, "doc@FreeBSD.org" <doc@freebsd.org> Subject: Re: Svn mirror seed has UUID wrong Message-ID: <20120723082513.GB38880@rwpc15.mby.riverwillow.net.au> In-Reply-To: <C18591FD-9073-4ED8-AA6B-8DB8256D2099@FreeBSD.org> References: <00F17B37-EE7E-43DA-8079-4E492323FBB3@FreeBSD.org> <C18591FD-9073-4ED8-AA6B-8DB8256D2099@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, 21 Jul 2012, 22:31 +0100, Simon L. B. Nielsen wrote: > Sorry, I forgot to mention that any svn checkout from a repository with t= he incorrect UUID will not work with the repository after the UUID has been= changed. >=20 > It's possible svn can be convinced to work with a 'new' repository, sorry= - I have no idea. I just consulted Google and found the following. It "worked for me" with Subversion 1.7.5. sqlite3 .svn/wc.db 'update REPOSITORY set uuid=3D"<new-repo-uuid>" where = id=3D1' Example: $ svn update doctree Updating 'doctree': svn: E170009: Repository UUID 'c2e8774f-c49f-e111-b436-862b2bbc8956' doesn'= t match expected UUID '8026a357-cfce-e111-996c-001c23d10e55' $ sqlite3 doctree/.svn/wc.db 'update REPOSITORY set uuid=3D"c2e8774f-c49f-e= 111-b436-862b2bbc8956" where id=3D1' $ svn update doctree Updating 'doctree': At revision 39236. --=20 John Marshall --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlANCmkACgkQw/tAaKKahKLXNgCgy/qmDO+XUQjRFGPHNKdlPhkt YVUAn3nuJ4lz0r56rIid8JSYeJ6U97j1 =kcgs -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120723082513.GB38880>