Research Why does it take longer with armbian buster to update packages?

[guidol]

I dont know if it real (but for me it feels like) that updating packaged (fetching/reading the list) takes much longer than on stretch or a bionic version.

(also on buster creating locales via armbian-config - I use de,gb and us - does take longer to generate)

 

While do a apt update I did see that buster do get package/content lists will come for armhf and aarm64 - is that OK or to much?

 

Get:8 http://cdn-fastly.deb.debian.org/debian buster/main arm64 Packages [7728 kB]

 

Get:9 https://apt.armbian.com buster/main armhf Packages [69.6 kB]
Get:10 https://apt.armbian.com buster/main arm64 Packages [67.4 kB]
Get:11 https://apt.armbian.com buster/main armhf Contents (deb) [2728 kB]

 

Get:12 http://cdn-fastly.deb.debian.org/debian buster/main armhf Packages [7690 kB]

 

Get:13 http://cdn-fastly.deb.debian.org/debian buster/main armhf Contents (deb) [35.2 MB]

 

Get:14 https://apt.armbian.com buster/main arm64 Contents (deb) [2742 kB]
Get:15 https://apt.armbian.com buster/buster-utils arm64 Packages [3459 B]
Get:16 https://apt.armbian.com buster/buster-utils armhf Packages [3749 B]
Get:17 https://apt.armbian.com buster/buster-utils arm64 Contents (deb) [572 B]
Get:18 https://apt.armbian.com buster/buster-utils armhf Contents (deb) [572 B]
Get:19 https://apt.armbian.com buster/buster-desktop arm64 Packages [403 B]
Get:20 https://apt.armbian.com buster/buster-desktop armhf Packages [1531 B]
Get:21 https://apt.armbian.com buster/buster-desktop arm64 Contents (deb) [60 B]

Get:22 https://apt.armbian.com buster/buster-desktop armhf Contents (deb) [213 B]

 

Get:23 http://cdn-fastly.deb.debian.org/debian buster/main arm64 Contents (deb) [35.3 MB]

[guidol]

I checked with dpkg -l the count of packages for arm64, armhf and all on a NanoPi Neo2 (H5 64Bit) and a NanoPi Neo (H3 32Bit)

and got no armhf packages on the NanoPi Neo2

NanoPi Neo2 H5 CPU - 64Bit - 4*Cortex-A53
# =============================================================================================
root@npi-neo2-22(192.168.6.22):~# dpkg -l|grep arm64|wc -l
441
root@npi-neo2-22(192.168.6.22):~# dpkg -l|grep armhf|wc -l
0
root@npi-neo2-22(192.168.6.22):~# dpkg -l|grep all|wc -l
92

root@npi-neo2-22(192.168.6.22):~# dpkg --print-foreign-architectures
armhf
# =============================================================================================

and no arm64 packages on NanoPi Neo,

NanoPi Neo H3 CPU - 32Bit - 4*Cortex-A7
# =============================================================================================
root@npi-neo(192.168.6.25):~# dpkg -l|grep armhf|wc -l
432
root@npi-neo(192.168.6.25):~# dpkg -l|grep arm64|wc -l
0
root@npi-neo(192.168.6.25):~# dpkg -l|grep all|wc -l
89
# =============================================================================================

but on the NanoPi Neo2 is armhf configured as foreign-architecture:

root@npi-neo2-22(192.168.6.22):~# dpkg --print-foreign-architectures
armhf

The Neo hasnt an additional foreign-architecture:

root@npi-neo(192.168.6.25):~# dpkg --print-foreign-architectures
root@npi-neo(192.168.6.25):~#

So I did according to the following pages

https://askubuntu.com/questions/978677/why-is-my-ubuntu-trying-to-fetch-aarch64-packages-on-x86-64-system
https://askubuntu.com/questions/66875/how-to-disable-multiarch-support

remove the armhf from my NanoPi Neo2:

sudo dpkg --remove-architecture armhf

Now the NanoPi Neo2 only collects arm64 package-lists (or also "all"?)

@Igor Do you think  that will cause any trouble?

 

I can re-add with:
 

dpkg --add-architecture armhf

or is it better to change it in /etc/apt/sources.list like (sample from https://wiki.debian.org/Multiarch/HOWTO):

deb [arch=armel,armhf] http://ports.ubuntu.com/ubuntu-ports quantal main universe

Note: There is a bug in apt versions >=0.9.7 and <0.9.7.2 which means that putting 'arch=armel,armhf' on one line didn't work - you needed two separate entries.

[sfx2000]

On 10/31/2019 at 5:44 AM, guidol said:

I dont know if it real (but for me it feels like) that updating packaged (fetching/reading the list) takes much longer than on stretch or a bionic version.

(also on buster creating locales via armbian-config - I use de,gb and us - does take longer to generate)

 

In my experience - debian-stable is a bit slower to pull in upstream on stable vs Ubuntu, even on Ubuntu-LTS builds.

 

debian is good on patching security issues.

[Igor]

On 11/1/2019 at 10:49 AM, guidol said:

Do you think  that will cause any trouble?

It shouldn't.