From owner-freebsd-ports Sun Sep 15 2:54:18 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D75337B400 for ; Sun, 15 Sep 2002 02:54:16 -0700 (PDT) Received: from south.nanolink.com (south.nanolink.com [217.75.134.10]) by mx1.FreeBSD.org (Postfix) with SMTP id 5ECAA43E6A for ; Sun, 15 Sep 2002 02:54:14 -0700 (PDT) (envelope-from roam@ringlet.net) Received: (qmail 97271 invoked by uid 85); 15 Sep 2002 10:02:37 -0000 Received: from discworld.nanolink.com (HELO straylight.ringlet.net) (217.75.135.248) by south.nanolink.com with SMTP; 15 Sep 2002 10:02:33 -0000 Received: (qmail 3286 invoked by uid 1000); 15 Sep 2002 09:52:57 -0000 Date: Sun, 15 Sep 2002 12:52:57 +0300 From: Peter Pentchev To: Alan E Cc: FreeBSD Ports List , FreeBSD Port Mgr , obrien@freebsd.org Subject: Re: bash2 ports Message-ID: <20020915095256.GC375@straylight.oblivion.bg> Mail-Followup-To: Alan E , FreeBSD Ports List , FreeBSD Port Mgr , obrien@freebsd.org References: <20020914202751.GA78262@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cmJC7u66zC7hs+87" Content-Disposition: inline In-Reply-To: <20020914202751.GA78262@wwweasel.geeksrus.net> User-Agent: Mutt/1.5.1i X-Virus-Scanned: by Nik's Monitoring Daemon (AMaViS perl-11d ) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --cmJC7u66zC7hs+87 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 14, 2002 at 04:27:52PM -0400, Alan E wrote: > I am currently hosting the bash2 port files on >=20 > http://people.freebsd.org/~alane/bash2/ >=20 > but do not wish to do so indefinitely. >=20 > The default ipfw firewall and inetd configuration will not allow > fetching the files for this port, due to the policies of the master > hosting site. >=20 > I find this to be an intolerable situation, and either we need to modify > our shipped inetd.conf and rc.firewall to accomodate this port (hahaha) > or we need to find a permanent home on a freebsd server for its files. I think this problem should, in a sense, disappear very soon, most probably at the next package build cycle - I believe that this is the time when ftp.FreeBSD.org's /pub/FreeBSD/ports/distfiles/ directory is updated. Thus, at the next package build, bash2's patchfiles will make it to ftp.FreeBSD.org, and everyone who is using it as a backup site (which, IIRC, is the default configuration) should be able to fetch them again. Other than that, I am more and more inclined to think that the problem lies with CWRU's ftp server more than with the FreeBSD firewall's default settings; there are simply too many places on the Internet where (questionable) policy decisions mandate dropping incoming connections, and unreasonable as such a policy may be, it currently bars everyone affected from using the CWRU FTP server. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This would easier understand fewer had omitted. --cmJC7u66zC7hs+87 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9hFh47Ri2jRYZRVMRApRJAKCbO4FVkASI69FNRfGSL8RP/WQBmgCfW8Ot PVj2mYNhSWJ+hiylCxG9xqE= =uom7 -----END PGP SIGNATURE----- --cmJC7u66zC7hs+87-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message