Date: Thu, 06 Nov 2008 09:59:25 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: "fire jotawski" <jotawski@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: cvsup: local Message-ID: <4463n0j3xu.fsf@be-well.ilk.org> In-Reply-To: <c583719d0811050058m3205b11n245536e4c4cb1262@mail.gmail.com> (fire jotawski's message of "Wed\, 5 Nov 2008 15\:58\:33 %2B0700") References: <c583719d0811050058m3205b11n245536e4c4cb1262@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"fire jotawski" <jotawski@gmail.com> writes: > i have my small box, 10.3.1.25 ip, that cvsup-ed files from repository into > it. it use cvs-supfile in /usr/share/examples/cvsup/ to collect files. > now that i want my other machine to cvsup 6.2-release source files from the > one mentioned above. > > my trial was > > cvsupd -b /var/db -c sup > > for box, 10.3.1.25 ip, and for other machine > > cvsup -g -L 2 -h 10.3.1.25 sup-file > > what i got was 'Server message: Unknown collection "src-all" ' message. > and later on > > Running > Skipping collection src-all/cvs > Skipping collection doc-all/cvs > Shutting down connection to server > Finished successfully > > very strange indeed. > > any helps and hints in setting cvsup server would highly be appreciated. To run cvsupd, you need the whole cvs tree for the collections you're handling, not just the checked-out files. Assuming these machines are attached by a protected network, a better approach (easier, anyway) would probably be to cvsup the changes to just one machine, then NFS-mount that machine's ports tree from the other machine. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4463n0j3xu.fsf>