Date: Mon, 6 Jun 2005 14:55:50 -0400 From: Kris Kennaway <kris@obsecurity.org> To: FreeBSD MailingLists <freebsd.ml@gmail.com> Cc: questions <freebsd-questions@freebsd.org>, Kris Kennaway <kris@obsecurity.org> Subject: Re: patch errors Message-ID: <20050606185550.GA18094@xor.obsecurity.org> 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
--6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 06, 2005 at 11:29:35AM +0900, 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. >=20 > 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 Because you have stale files underneath. > 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. Because you have stale files underneath. > which leads me to believe the error is outside the ports tree itself. Highly unlikely. Kris --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCpJw2Wry0BWjoQKURAp9/AJsH07H14cIZjLz+WB+8O3MAWt553wCglpJ6 iXX3ZfdRa0t8qaead3WfXsk= =uL8j -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050606185550.GA18094>