-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/27/2015 12:31 PM, Ron W wrote: > HOWEVER, the new repository will have the same repository ID as > the original.
The project-code is easy to change. Often at work I deal with silliness where TCP can be initiated from computer A to computer B, but not from computer B to computer A. Normally this isn't a huge problem since I'll just run sync on whichever computer can start the connection, but I'm in trouble when I want to clone to a computer that can't start the connection. My solution is to create a new, empty repository (no initial empty commit), use sqlite3 to change the project-code to match the repository I wish to clone, then push to it from the other computer. Obtaining the project-code: $ fossil info | grep ^project-code project-code: 80b5e4d3dd1a8a82fe2620a20f5df25de04afcfd Setting the project-code: $ fossil sqlite3 sqlite3> update config set value = '80b5e4d3dd1a8a82fe2620a20f5df25de04afcfd' where name = 'project-code'; I'm sure a more thorough solution exists, but this works. - -- Andy Goth | <andrew.m.goth/at/gmail/dot/com> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUyAI4AAoJELtYwrrr47Y41qQIAN1Z5omf4MIwFuOfeojYo3Rp tYDMqkVZM2Sg6UCqxDzAL/J3iU/V7gScrsctqFxTwgp/9BtwkH3abxbvLCx6BgLF dKIlkE9GQvLmmZk2e7Cqg1n/XZmu0xvRe2+Vepao/CVIgEItOUGIfOQ1dKaEEhO5 JPk8gxJ/dgDGeyebtH1vCLH5vIIdXQibACtvVTVBz5z1XB4Tl26rnsbl0ip/3D4l 8OJMDFEkLWXrbdBpjO7PQsycq9n3Mbog0BDcxl4vEXWcnmaKeVeS1UawPIoa7Und 5UjnlH0Cl/wc8UWEv7ONEhlltzihtpAzcLGNdqX9mSc9kFJJgEhdJo4xYgI9QSQ= =AL/c -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
