Hi! On Sat, 2020-08-15 at 07:29:42 -0400, The Wanderer wrote: > Package: dpkg > Version: 1.20.5 > Severity: normal
> During a routine 'apt-get dist-upgrade' against testing, I got (in > part): > > > Preparing to unpack .../73-locales-all_2.31-3_amd64.deb ... > Unpacking locales-all (2.31-3) over (2.31-2) ... > dpkg-deb (subprocess): decompressing archive member: lzma error: > compressed data is corrupt > dpkg-deb: error: <decompress> subprocess returned error exit status 2 > dpkg: error processing archive > /tmp/apt-dpkg-install-EMKBka/73-locales-all_2.31-3_amd64.deb (--unpack): > cannot copy extracted data for './usr/lib/locale/ja_JP.eucjp/LC_CTYPE' > to '/usr/lib/locale/ja_JP.eucjp/LC_CTYPE.dpkg-new': unexpected end of > file or stream > > ... > > Errors were encountered while processing: > /tmp/apt-dpkg-install-EMKBka/73-locales-all_2.31-3_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > After this, a run of 'apt-get -f install' did not appear to act on the > locales-all package, and did not fail. A subsequent repeat of the > dist-upgrade command saw locales-all as the only package available to be > upgraded, and proceeding let it upgrade without a repeat of the error. Did the subsequent upgrade download the package again? If so the local one could have been damaged, but a redownload would have fixed that. If you do not have access to the supposedly "faulty" package as it was just after the dpkg error, then I'm not sure there is much we can do at this point though. :/ > I have not thus far found anything elsewhere in the system (e.g. dmesg, > for underlying disk errors) which might explain why this unexpected EOF > occurred. > > I am not at all sure which package might be responsible for this; > locales-all (and thus glibc) is a possibility, but at a glance I think > this looks more like a dpkg issue, and I can't rule out that it's > something else entirely. Please feel free to reassign - or, if e.g. this > is likely a one-off local error which is not likely to recur for others, > close - as you see fit. > > At least at the moment, I can no longer reproduce this failure, but just > in case it isn't a one-off I didn't want to let it go unreported. I'm not sure if this could be related to some recent fixes in apt where it previously was not fully fetching all data from remote sites. What I can do though, is add a bit more information to the error message, such as the .deb name and size, so that if the file had been truncated then we'd be able to immediately know. Ideally a checksum would also be printed but hmmm. Thanks, Guillem
