Date: Wed, 4 Jan 2006 05:36:19 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Mark Kane <mark@mkproductions.org> Cc: freebsd-ports@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: amd64 package builds (Re: A few ports fail to rebuild after cvsup) Message-ID: <20060104103618.GA35685@xor.obsecurity.org> In-Reply-To: <43BB50EB.2010901@mkproductions.org> References: <43B4E30C.6020604@mkproductions.org> <20051230103131.GA88660@sysmon.tcworks.net> <43B56BC0.3090603@mkproductions.org> <43BAC111.3080604@mkproductions.org> <20060104041348.GA25767@xor.obsecurity.org> <43BB50EB.2010901@mkproductions.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jan 03, 2006 at 10:36:59PM -0600, Mark Kane wrote: > I see what you are saying about builds and machines, but do you know why > this port is broken? I'm not trying to use packages, I want to use > ports. In other words, if it's been broken for a long time (especially > for all architectures) why wouldn't it be marked as broken? Do you know > of a planned fix for the port? It's broken because the maintainer and/or person responsible for the breakage has ignored my emails reporting the fact and requesting it be marked BROKEN. Please contact the maintainer directly if you want to know more about the reasons they haven't fixed it. Kris --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDu6UhWry0BWjoQKURAvVWAJ9VJoK5f/ouvxmb6hzvCMc6a3oQ4QCeNgOr kPi5tY652NUO3SoYZHLQaDI= =EdIf -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060104103618.GA35685>