Some PKGBUILDs of packages in our repositories make use of soname dependencies in the global `depends`, `makedepends` or `optdepends` array.
This unfortunately is prone to ELF architecture confusion.
See the sonamev1 specification for details: https://alpm.archlinux.page/specifications/alpm-sonamev1.7.html

To not match sonames of a wrong ELF architecture, we need to apply the best practices outlined in the specification's example section on "depending on a soname": https://alpm.archlinux.page/specifications/alpm-sonamev1.7.html#depending-on-a-soname
Effectively, this usually means to remove the soname dependency from the global `depends` array (it should also not be present in `makedepends` or `optdepends`) and instead add it in an override in the `package` function to the `depends` array, e.g.:

```
package() {
depends+=(example libexample.so)
}
```

If your package uses sonames in optional dependencies, consider to split out components depending on the soname into separate packages (if possible), or to pull in the soname dependency as direct dependency instead (see above), as this ensures robust dependency tracking.

Note, that the below list of packages has been retrieved manually from dependents of lib32-* packages in our repositories and constitutes packages that are 64bit.
It has not been checked whether the pulled in soname (from the set of 64bit packages) is actually in use by the package (please verify yourself)!

The package rebuilds can go straight to the stable repositories (if permissable).