Cannot search for most ARM packages

[Adriankhl]

Problem: Theoretically, there are "openSUSE Factory ARM" package on https://software.opensuse.org/, but this only contains some very old packages. For example, if I searched for "networkmanager", click "view" and then "expert download", there is no "aarch64" rpm package available. The package definitely exists and downloadable from (https://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/aarch64/).

I have described this problem in the mailing list https://lists.opensuse.org/archives/list/arm@lists.opensuse.org/thread/7D2YBI2A6ECAYTPEHUWYBT6DQC5WXWPO/. While I was trying to debug it myself, I found myself too inexperience in ruby and it is pretty hard for me to exactly locate the bug. It seems like it is not related to the filter (#296).

Further analysis: There is a way to search the package from the obs (https://build.opensuse.org/). Suppose you want to search for "networkmanager", and you arrive the openSUSE:Factory (https://build.opensuse.org/package/show/openSUSE:Factory/NetworkManager), the build result only shows x86_64 and i586. You can see that the package is maintained at GNOME:Factory (https://build.opensuse.org/package/show/GNOME:Factory/NetworkManager). From there you can go to "Repositories" and click "openSUSE_ARM" to find the rpm package.

I conjecture that this bug is caused by the non-standard location and api of ARM packages from the obs. It doesn't exist in the openSUSE:Factory, and while it should be located at the ARM Factory (https://build.opensuse.org/project/show/openSUSE:Factory:ARM), the "NetworkManager" package belongs to the "Inherited Packages" instead of the ordinary "Packages" (located here: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/NetworkManager, and you can't download the rpm package there, it is only available at the GNOME:Factory), therefore the website cannot retrieve it like how it retrieve the x86 packages.

I think this somewhat duplicate (#695), but it seems like there is no progress in that issue so I open this new issue for a more detailed description of the problem.