Date: Mon, 06 Jun 2005 09:36:16 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: FreeBSD MailingLists <freebsd.ml@gmail.com> Cc: questions <freebsd-questions@freebsd.org> Subject: Re: patch errors Message-ID: <42A40B00.5060204@dial.pipex.com> In-Reply-To: <ded8d71705060519296324c6b8@mail.gmail.com> References: <ded8d71705060508243413765@mail.gmail.com> <20050605170340.GA14827@gothmog.gr> <ded8d71705060517464861413d@mail.gmail.com> <20050606010129.GA57493@xor.obsecurity.org> <ded8d71705060519296324c6b8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
FreeBSD MailingLists wrote: >on all other servers I cvsup the src and ports tree, but for some >reason the internet connection at the location of this particular >server gets kicked when I start cvsup. so I had to resort to this >method. > >I am not entirely convinced that it is a stale patch issue for 2 reasons. >1) I have untar'd the same file on 2 different servers and only this >one has issues updating the ports >2) I have tar'd up the /usr/ports dir from a different server that >updates via cvsup. The original server updates fine but when untar'd >on this particular server the same exact patch errors appear. > >which leads me to believe the error is outside the ports tree itself. > > Did you delete the ports tree before untaring? You don't mention that. (You could also investigate rsync or rdist to keep this machine's port tree up to date since that will do the deletions for you). --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42A40B00.5060204>