Date: Tue, 31 Jan 2006 14:06:34 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Joe Kelsey <joe@zircon.seattle.wa.us> Cc: ports@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: Who marked ksh93 unfetchable and did not tell me? Message-ID: <20060131190634.GA11401@xor.obsecurity.org> In-Reply-To: <1138688287.36627.20.camel@zircon.zircon.seattle.wa.us> References: <1138681494.36627.7.camel@zircon.zircon.seattle.wa.us> <20060131045841.GA74951@xor.obsecurity.org> <1138688287.36627.20.camel@zircon.zircon.seattle.wa.us>
next in thread | previous in thread | raw e-mail | index | archive | help
--wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 30, 2006 at 10:18:07PM -0800, Joe Kelsey wrote: > On Mon, 2006-01-30 at 23:58 -0500, Kris Kennaway wrote: > > On Mon, Jan 30, 2006 at 08:24:54PM -0800, Joe Kelsey wrote: > > > Someone marked ksh93 unfetchable without sending me a notice. ksh93 = is > > > NOT unfetchable, just the automatic script that checks for fetchabili= ty > > > is broken and cannot fetch ksh93. > >=20 > > No, I sent you mail on Friday. Perhaps you're still blocking my > > emails? >=20 > My filter either did not work or the message had some other error. Did > the subject contain the string "ksh"? Yes. > > > Whoever is running the port fetchability script needs to remove ksh93 > > > from the test. ksh93 is always fetchable and always will be fetchabl= e. > >=20 > > No, it is not fetchable. >=20 > I have updated the port. Install the update and everything should work > fine. Thanks. Kris --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD37U6Wry0BWjoQKURAlY2AJ4nb0al8ahicvim5rkuCjLSyWwatgCgrFj+ Wqm3GdImV+jACqYqrUZxcTI= =7wF7 -----END PGP SIGNATURE----- --wac7ysb48OaltWcw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060131190634.GA11401>