Bug#867816: marked as done (Apt arm64 problem with chroot to arm64)
Your message dated Fri, 19 Apr 2019 01:53:09 +0000
with message-id <AM6PR06MB50632CFBA8388C6A64904B2DA1270@AM6PR06MB5063.eurprd06.prod.outlook.com>
and subject line fixed
has caused the Debian Bug report #867816,
regarding Apt arm64 problem with chroot to arm64
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 owner@bugs.debian.org
immediately.)
--
867816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867816
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.5~beta
Apt-get fails with this version, but not with 1.4.6.
I do Debian testing Xfce SD card images for the Amlogic S912 TV box.
There is /usr/bin/qemu-aarch64-static in the destination file system.
Armbian distribution build script uses
the following command in lib/deboostrap-ng.sh:
eval 'LC_ALL=C LANG=C chroot $CACHEDIR/$SDCARD /bin/bash -c
"DEBIAN_FRONTEND=noninteractive apt-get -y -q -m \ $apt_extra
$apt_extra_progress --no-install-recommends install $PACKAGE_LIST"'
After installing successfully several packages, in the logs there is:
Selecting previously unselected package gnome-icon-theme.
Preparing to unpack .../070-gnome-icon-theme_3.12.0-2_all.deb ...
Unpacking gnome-icon-theme (3.12.0-2) ...
dpkg: error processing
archive /tmp/apt-dpkg-install-sQZDkO/070-gnome-icon-theme_3.12.0-2_all.deb
(--unpack): corrupted filesystem tarfile - corrupted package archive
And apt-get fails to install any additional packages.
I debootstrapped Debian base system using
stretch where is apt 1.4.6. Then chroot works ok with testing packages.
--- End Message ---
--- Begin Message ---
fixed
--- End Message ---
Reply to: