ports/102499: lftp asc file checksum mismatch
kris at obsecurity.org
Wed Jan 24 22:17:28 UTC 2007
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.
> Pav Lucistnik wrote:
> >So, what's the status on this one? My opinion is that the whole ticket
> >is bogus and should be closed.
> No, it shouldn't. Sorry I didn't have enough time to investigate the
> problem further,
> but it is a real pain for port distribution. IIRC the point I've reached
> 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 conversion
> 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
> So the problem not in the port itself but in the set of conditions. And
> 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20070124/3b8c4110/attachment.pgp
More information about the freebsd-ports