From owner-freebsd-ports@FreeBSD.ORG Wed Jan 24 22:17:28 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 93C5616A409; Wed, 24 Jan 2007 22:17:28 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 5836913C467; Wed, 24 Jan 2007 22:17:28 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 2C8F11A4D83; Wed, 24 Jan 2007 14:17:28 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9CD405156B; Wed, 24 Jan 2007 17:17:23 -0500 (EST) Date: Wed, 24 Jan 2007 17:17:23 -0500 From: Kris Kennaway To: Roman Kurakin Message-ID: <20070124221723.GA39811@xor.obsecurity.org> References: <1169641247.96993.10.camel@pav.hide.vol.cz> <45B7D5BD.4070400@inse.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <45B7D5BD.4070400@inse.ru> User-Agent: Mutt/1.4.2.2i Cc: rik@FreeBSD.org, ports@freebsd.org, pav@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: ports/102499: lftp asc file checksum mismatch X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 22:17:28 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 25, 2007 at 12:55:09AM +0300, Roman Kurakin wrote: > I am crossposting this to both bugs@ and ports@ so all who will join this > discussion keep this in mind if you'll reply. >=20 > Pav Lucistnik wrote: > >So, what's the status on this one? My opinion is that the whole ticket > >is bogus and should be closed. > > =20 > No, it shouldn't. Sorry I didn't have enough time to investigate the=20 > problem further, > but it is a real pain for port distribution. IIRC the point I've reached= =20 > was: > all software works correctly. All files correct but port can't be build. = The > reason that default behaviors are not the same on all levels and conversi= on > of new line from single char to double could occur. The solution is to > request text file as binary than all layers will bypass it without > modifications or to convert newline explicitly for all text files before > computation of checksum to the one default value (I guess to single-char > variant). >=20 > So the problem not in the port itself but in the set of conditions. And= =20 > probably > this bug report should be reopened with other description. I didnt see earlier mails in the thread, but I assume the problem is that lftp gets a corrupted distfile when fetching through a squid proxy. This is because in the default configuration squid fetches all plain text files in ftp ascii mode, which does CR/LF translation and botches up the checksum. IMO this is a bug in the squid configuration. Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFt9rzWry0BWjoQKURAl5VAKCOqGZ9DwIh8fj3LfPdvFM4fDvQ9ACg+sjz lc5QIcL+KnZs2NTW0Qi2ARQ= =z1fX -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx--