Your message dated Tue, 31 May 2016 12:02:40 -0600 (MDT) with message-id <20160531180240.90b81bc3...@rover.gag.com> and subject line not a bug has caused the Debian Bug report #823748, regarding tar: illegal hardware instruction breaks apt-get upgrade to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 823748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: tar Version: 1.28-2.2 Severity: critical Justification: breaks unrelated software Dear Maintainer, upgrading tar breaks apt-get/dpkg due to "illegal instruction" errors. * What led up to the situation? tar was upgraded: tar (1.28-2.1 => 1.28-2.2) * What exactly did you do (or not do) that was effective (or ineffective)? apt-get dist-upgrade * What was the outcome of this action? All packages upgraded after tar failed during unpack: dpkg-deb: error: subprocess tar was killed by signal (Illegal instruction) dpkg: error processing archive /var/cache/apt/archives/libssl1.0.2_1.0.2h-1_i386.deb (--unpack): subprocess dpkg-deb --control returned error exit status 2 dpkg-deb: error: subprocess tar was killed by signal (Illegal instruction) dpkg: error processing archive /var/cache/apt/archives/ntp_1%3a4.2.8p7+dfsg-3_i386.deb (--unpack): subprocess dpkg-deb --control returned error exit status 2 dpkg-deb: error: subprocess tar was killed by signal (Illegal instruction) dpkg: error processing archive /var/cache/apt/archives/libselinux1_2.5-2_i386.deb (--unpack): subprocess dpkg-deb --control returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libssl1.0.2_1.0.2h-1_i386.deb /var/cache/apt/archives/ntp_1%3a4.2.8p7+dfsg-3_i386.deb /var/cache/apt/archives/libselinux1_2.5-2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) * What outcome did you expect instead? All package upgrades should have succeeded. I could temporarily resolve the problem by copying the previous tar version from another box. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 4.4.7 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tar depends on: ii libacl1 2.2.52-3 ii libc6 2.22-7 ii libselinux1 2.5-2 tar recommends no packages. Versions of packages tar suggests: ii bzip2 1.0.6-8 pn ncompress <none> pn tar-scripts <none> ii xz-utils 5.1.1alpha+20120614-2.1 -- no debconf information
--- End Message ---
--- Begin Message ---This appears to be a consequence of the change announced on 7 May 2016 in which the minimum CPU features for the i386 architecture moved to 686-class for the stretch release cycle. Anyone using an older CPU should probably stop trying to track unstable/testing upgrades as more things are likely to break as more packages get uploaded built against the new compilers. Since I don't see any evidence that this is an actual bug in tar, I'm closing this bug with no further action taken. Bdale
--- End Message ---
