Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Apr 2015 10:25:20 -0700
From:      Xin Li <delphij@delphij.net>
To:        Jung-uk Kim <jkim@FreeBSD.org>, Matteo Riondato <matteo@freebsd.org>,  Xin LI <delphij@freebsd.org>
Cc:        svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org
Subject:   Re: svn commit: r281316 - in head: contrib/xz contrib/xz/src/common contrib/xz/src/liblzma/api/lzma contrib/xz/src/liblzma/common contrib/xz/src/liblzma/lz contrib/xz/src/liblzma/lzma contrib/xz/src/xz...
Message-ID:  <55280780.1040104@delphij.net>
In-Reply-To: <552803B6.4000005@FreeBSD.org>
References:  <201504091803.t39I3R4Y042146@svn.freebsd.org> <CA%2BfiBi7hYTfqSWeG3%2B9qLwtHw2BLSTbYk=gpzf0V3-agfXNaAA@mail.gmail.com> <552803B6.4000005@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 04/10/15 10:09, Jung-uk Kim wrote:
> On 04/10/2015 12:05, Matteo Riondato wrote:
>> Could this update be causing this error when trying to upgrade
>> the installed packages using "pkg upgrade" ?
> 
>> [1/27] Extracting glib-2.42.2:  99% pkg: archive_read_extract(): 
>> Lzma library error: Corrupted input data [1/27] Extracting 
>> glib-2.42.2: 100% [1/27] Deleting files for glib-2.42.2: 100%
> 
>> ? I tried removing the fetched archives from /var/cache/pkg and 
>> having pkg fetch them again, so that doesn't seem to be the
>> issue.
> 
> Actually libarchive(3) seems broken.
> 
> # tar tf tar-1.28.tar.xz > /dev/null || echo FAILURE! tar:
> Truncated input file (needed 976896 bytes, only 0 available) tar:
> Error exit delayed from previous errors. FAILURE!
> 
> The same file is fine with GNU tar.

I have see this too.

It seems like the libmd implementation of SHA256 is doing something
differently than the bundled one and libarchive(3) is expecting a
different behavior (not 100% sure yet, still figuring it out).

The strange part is that xz's 'make check' passed just fine and the
same archive processed by xz(1) as expected, so yes it's possible that
we hit a libarchive bug.

As a precaution I have reverted the SHA256 portion of the change and
the library should work fine with libarchive now.

Cheers,
- -- 
Xin LI <delphij@delphij.net>    https://www.delphij.net/
FreeBSD - The Power to Serve!           Live free or die
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1.2 (FreeBSD)

iQIcBAEBCgAGBQJVKAeAAAoJEJW2GBstM+nsRSwP/3GhfVOYIIqG3CZ8duB++4he
IURodWRl11uJnagRaOnZnoR9LpDWBoLgx6SK53DDoOkxDGr8PKXr6WxBuX7zTR4P
h2Bqu0ibmhPrEPTC3YfLn5nn8IoxtRj8nZZlkD/hU4dGnwiKzaH/9krFVdmGrePn
HkdNUkdANp8bDu+AiBxPgSXf+GFYOuDs+fpDIvWCrIaB/MLzD4zrsQZCWdT4p7J3
c8IwzNHW2z0T5dULlEssaxG5bYc+P/RhCC8mRqhj73WpGb7UbNHjcY2ICDA15Hb8
IZYu3quprLx/F40qhGxBUgdgOEyPNqzdBvcUl325N0AqvAnama6zPE4eeZutHioQ
LMt8lnllIr5xnmuHaN3+YyyPDuEg03SmyihbjD9vbA+5/M9Y6fLSOWHY/ns/2AUF
laO32LZjZiOz0h5r2S5ipJbSWD4vHzWtFPFNW3FwpqPsXsD7ikE2vsJLowMJf6p9
ww4qFzsecXv1YG4tDrUubqci6S06UYNtI+u3Icm7LFJqwMVzAxWCF9IYbzZl5Kqd
4Rcmej8JVA0qC7hheESs5lEN6/6LQ64S89c76M2yxW+H54E2X5VfKGOIVNa1Geuc
DtKVz24tjXCspu18RJFPlcsCA+MJOIMVN5oBhll+vPiDu1HOGhykmo0m23sY5UiK
ON61a59e3GwA7Ydgp4AC
=1Hhm
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55280780.1040104>