Bug 199350 - Lzma library error: Corrupted input data
Summary: Lzma library error: Corrupted input data
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Many People
Assignee: Xin LI
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-10 13:05 UTC by Juraj Lutter
Modified: 2015-04-15 22:14 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juraj Lutter freebsd_committer freebsd_triage 2015-04-10 13:05:44 UTC
After recent import of LZMA I'm getting:

 Lzma library error: Corrupted input data

when running "tar xvjf filename.txz"

On ARM:
Tested on Raspberry PI and qemu-static-arm.

System:
FreeBSD rpitest 11.0-CURRENT FreeBSD 11.0-CURRENT #34 r281320M: Thu Apr  9 22:04:36 CEST 2015     root@rpibuild:/data/rpibuild/output/obj/arm.armv6hf/data/rpibuild/src/fbsd-11/sys/RPI-B-OTIS  arm


On AMD64:
root@rpibuild:/usr/ports/audio/xmms-flac # make
===>   xmms-flac-1.3.1 depends on file: /usr/local/sbin/pkg - found
=> flac-1.3.1.tar.xz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch http://downloads.xiph.org/releases/flac/flac-1.3.1.tar.xz
flac-1.3.1.tar.xz                             100% of  919 kB  269 kBps 00m03s
===> Fetching all distfiles required by xmms-flac-1.3.1 for building
===>  Extracting for xmms-flac-1.3.1
=> SHA256 Checksum OK for flac-1.3.1.tar.xz.
flac-1.3.1/src/libFLAC/lpc_intrin_sse.c: Lzma library error: Corrupted input data
tar: Error exit delayed from previous errors.
*** Error code 1


Problem occurs in r281320.

Works OK on 10-STABLE/amd64.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2015-04-15 17:39:48 UTC
delphij: is this the problem addressed by the reversion in http://svnweb.freebsd.org/base?view=revision&revision=281372 ?
Comment 2 Xin LI freebsd_committer freebsd_triage 2015-04-15 17:41:04 UTC
This was fixed by r281372.
Comment 3 Juraj Lutter freebsd_committer freebsd_triage 2015-04-15 22:14:32 UTC
Yes, the problem is fixed now.