Debian do have 32-bit armhf repositories but they will not work with the Pi 1 or Pi Zero, so some hard working people created Raspbian (by recompiling all of the Debian software with different options) which does work with Pi 1 and Zero. Raspberry Pi use the Raspbian software for their 32-bit OS - apart from the bits they add themselves.I see your point: "Raspbian" is associated with 32 bit for sure. But are you sure its also the other way around, i.e. is "Debian" also a warranty for 64 bit? I ask this (as a Windows guy moving tho Debian and an Intel guy moving to ARM) because I thought the introduction of RPi OS was ment to be the end of Raspbian (being a rebranding operation) and that the latter would be succeeded by 'RPi OS ARMHF'. And that it therefore not was to be expected to find any reference to "Raspbian" under the hood after a fresh RPi OS ARMHF install.You've got "Debian" in your os-release file, which is used for the 64-bit version of Raspberry Pi OS. The 32-bit version would show "Raspbian" instead.
dpkg refers to software.I guess you're right: the output gives me 'arm64'. And the dpkg manpage litteraly says:
--print-architecture: Print architecture of packages dpkg installs (for example, "i386").
I checked manpage because print-architecture could also have referred to hardware architecture, not software architecture.
But then it looks like I cannot install 32 bit software on my 64 bit RPi. At least not without tweaking Aptitude. Am I right?
You can run multi-arch by adding the 32-bit architecture. You might find it is already set up. dpkg --print-foreign-architectures
The 64-bit version can run 32-bit software using that, but (as far as I know) the 32-bit arm OS can't run 64-bit software (maybe with an emulator?)
Statistics: Posted by rpdom — Mon Jul 15, 2024 11:49 am