Your message dated Fri, 17 May 2019 18:32:27 +0100
with message-id <20190517173227.ga17...@tack.einval.com>
and subject line Re: Bug#929100: decompressing archive member: lzma error:
compressed data is corrupt
has caused the Debian Bug report #929100,
regarding decompressing archive member: lzma e
Get: 1 http://opensource.nchc.org.tw/debian experimental/main amd64 cpp-8 amd64
8.3.0-13 [8,909 kB]
Get: 2 http://opensource.nchc.org.tw/debian experimental/main amd64 gcc-8-base
amd64 8.3.0-13 [191 kB]
Get: 3 http://opensource.nchc.org.tw/debian experimental/main amd64 rclone
amd64 1.47.0+ex1-5
Preparing to unpack .../gcc-9-base_9.1.0-2_amd64.deb ...
Unpacking libobjc4:amd64 (9-20190428-1) over (8.3.0-7) ...
dpkg-deb (subprocess): decompressing archive member: lzma error: compressed
data is corrupt
dpkg-deb: error: subprocess returned error exit status 2
dpkg: error processing archive
I can't make sense of the error messages either.
Processing control commands:
> severity -1 minor
Bug #929100 [gcc-9-base] decompressing archive member: lzma error: compressed
data is corrupt
Severity set to 'minor' from 'critical'
--
929100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929100
Debian Bug Tracking System
Contact ow...@bug
Control: severity -1 minor
sorry, I can't take bug reports with such exaggerations as serious. Even more
if your issue looks like a local problem.
On 17.05.19 08:26, 積丹尼 Dan Jacobson wrote:
> Package: gcc-9-base
> Version: 9.1.0-2
> Severity: critical
>
> E: Invalid archive member header...
> E
6 matches
Mail list logo
