On Fri, Apr 14, 2006 at 05:08:52PM +0100, Dave Korn wrote: >On 14 April 2006 16:59, Christopher Faylor wrote: > >> ----- Forwarded message from Cron Daemon <[EMAIL PROTECTED]> ----- >> >> Invalid header block at offset unknown at >> >/export/u0/sourceware/sourceware/libre/infra/bin/cygwin/Cygwin/Setup/Listing.p >m >> line 186 Invalid header block at offset unknown at >> >/export/u0/sourceware/sourceware/libre/infra/bin/cygwin/Cygwin/Setup/Listing.p >m >> line 186 Invalid header block at offset unknown at >> >/export/u0/sourceware/sourceware/libre/infra/bin/cygwin/Cygwin/Setup/Listing.p >m >> line 186 No data could be read from file at >> >/export/u0/sourceware/sourceware/libre/infra/bin/cygwin/Cygwin/Setup/Listing.p >m >> line 186 PROBLEMS WITH release/w32api/w32api-3.7-1-src.tar.bz2 >> >> ----- End forwarded message ----- >> >> I've been noticing this error message for a couple of days. >> I wonder if it has something to do with the new version of tar? > > The message itself comes from bunzip2. If tar is somehow now piping stuff >to or from it in textmode when using -j, .... ouch! The phrase "at offset >unknown" suggests fseek-vs-textmode trouble as well. > >> So far, it has cropped up for monotone, coreutils, and, now, w32api. >> Unpacking/repacking the files on sourceware.org seems to "fix" the >> problem. > >... which is a native LF-speaking linux box...
And the actual error is coming from a native LF-speaking linux box. It's hard to see how this could be a CRLF issue. cgf