I am a very happy user of Manjaro on all kinds of platforms (Desktop, Laptop, Pinebook Pro, Raspberry Pi, Pinephone, …). As packaging is such a breeze in Arch/Manjaro, I set up a personal repository for my software on GitLab (which I can’t link to here unfortunately). I have now run into a very strange problem, namely pacman installing packages of an invalid architecture , but only when this package is installed as a depenency, not when trying to install it directly.
In particular, my repository contains an automatically built
x86_64 version of
python-thunarx from the AUR. I also have an arch-independent package dependent on that, called
Now if I add the repository on one of my Manjaro ARM machines (a Raspberry PI 4 here, but it’s the same on the Pinebook Pro), the following happens:
sudo pacman -Syu python-thunarx # refuses to install due to incompatible architecture sudo pacman -Syu python-thunar-plugins-git # happily installs python-thunarx x86_64 as a dependency (which doesn't work obviously)
--arch "$(uname -m)" also doesn’t change anything.
This shouldn’t be, right? I mean, why would
pacman install a package that is clearly built for a different architecture and is thus guaranteed to not work?
╰─➤ pacman --version .--. Pacman v5.2.2 - libalpm v12.0.2 / _.-' .-. .-. .-. Copyright (C) 2006-2020 Pacman Development Team \ '-. '-' '-' '-' Copyright (C) 2002-2006 Judd Vinet '--' Dieses Programm darf unter Bedingungen der GNU General Public License frei weiterverbreitet werden.