An issue here is Virtualmin packaging.
I think it is fair to state Virtualmin packaging is unclear. Maybe you can clarify, instead of getting annoyed.
There is so much that is unclear in Virtualmin. It is not funny.
I installed Virtualmin on aarch64 a few months ago. Installation worked great.
When VIRTUALMIN packages needed to be updated I got failure. The architecture is not supported.
So, what else I am expected to conclude, other than VIRTUALMIN packages install from source but VIRTUALMIN packages update from non source architecure dependenant packaging that usually (but not necessarily) contain binary code?
What if we could choose to update from an experimental repository that has all Virtualmin Debian packages relabelled as '‘noarch’?
It looks like Virtualmin is nearly 100% there to using aarch64.
Why not let us focus on this?
Please accept that Virtualmin has a lot of issues with regard to clarity and just let us move on.