Date: Sat, 16 Jul 2005 10:15:52 +0200 From: Michael Nottebrock <lofi@freebsd.org> To: legalois@acm.org Cc: Anton Berezin <tobez@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: portupgrade problems on 4.x Message-ID: <200507161015.56587.lofi@freebsd.org> In-Reply-To: <42D8364F.5040106@acm.org> References: <42D7AB39.30803@acm.org> <200507151534.03865.lofi@freebsd.org> <42D8364F.5040106@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1157397.OJ9GYH3Jy3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday, 16. July 2005 00:18, Jake Lloyd wrote: > Mine are 4.9-RELEASE > Sure, I knew support for these would start to run out, finally. > just putting off spending an afternoon with mergemaster. Well, you can just use the workaround Brandon posted ... > But this has been the first real hitch with this aging version, > and I still don't understand the spontaneous way the problem came up. The bug is only triggered rather rarely. If you'd delete a few random port= =20 directories from /usr/ports (or if you'd trace portsdb, find out the exact= =20 portdir it crashes on and delete that), the dataset would probably be=20 sufficiently different to not trigger the crash. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1157397.OJ9GYH3Jy3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC2MI8Xhc68WspdLARAifEAJ9QcclRYKzwhFBBP/Kruy0PVQiFZQCfbdSk HXOb8pnby/ekChED2x21Epw= =DCNi -----END PGP SIGNATURE----- --nextPart1157397.OJ9GYH3Jy3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507161015.56587.lofi>