Smart doesn't detect 'armel' architecture correctly

[Sidnei da Silva]

Apparently 'arm' is toast, long live to 'armel. Smart though assumes that anything that startswith('arm') should be 'arm'.

From the information on Debian's ArmEabiPort, seems like anything later than 'armv4te' should be 'armel':

"""
So Debian armel runs on a minimum CPU of ARMv4t and by default the Debian armel GCC generates code for armv4t (rather than the usual default ARM target of armv5t).
""" -- From: http://wiki.debian.org/ArmEabiPort

[Sidnei da Silva (sidnei)]

FWIW, in smart/backends/deb/base.py:getArchitecture():

   - sysconf.get("deb-arch") returns None
   - ... elif arch.startswith("arm"): return "arm"
     - Should probably be 'armel' here by default, and 'arm' only for
       'StrongARM' or earlier than 'ARMv4'

[Sidnei da Silva (sidnei)]

Due to misdetection of 'arm' vs 'armel' landscape-client doesn't see any available packages, it only sees a subset of the ones installed. Once 'armel' is returned correctly, the smart cache needs to be blown away for smart to see the right packages, and subsequently for landscape-client to upload the correct package information.

[Anders F Björklund (afb)]

dpkg debian archtable says:
i486-linux-gnu i386
x86_64-linux-gnu amd64
arm-linux-gnu arm
arm-linux-gnueabi armel

ostable:
# <Debian name> <GNU name> <config.guess regex>
gnueabi-linux linux-gnueabi linux[^-]*-gnueabi
gnu-linux linux-gnu linux[^-]*(-gnu.*)?

[🤖 Landscape Builder (landscape-builder)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

Landscape Team