For perhaps up to the past two weeks since today, September 11, 2019, my Debian_Unstable repositories have been unable to build any packages for architectures i586 and x86_64. They are marked as “unresolvable,” with the reason code “nothing provides multi-arch.”
I have done a small amount of looking around, and found a few other people’s repositories are also experiencing this for the Debian Unstable repos. I can share links if needed.
Is anyone else experiencing this? Do I need to adjust my configuration somehow? I only target Debian unstable so I have no personal experience with other Debian environments.
I didn’t initially realize there were other forums on this site. I arrived here at the “Forums” link on the wonderful, public Open Build System at https://build.opensuse.org/.
I use the OBS for only Debian_Unstable. I realize the fact that it is unstable means that sometimes things break, and I gave it at least a good week before deciding to ask.
I can build packages on my Devuan Beowulf/Ceres (akin to Debian Unstable) local install, so I don’t think this is a Debian repos problem.
Unfortunately on the OBS, when I get that error message, I cannot see any verbose output or logs to find out what needs the multi-arch package. It only has the little text, “Nothing provides multi-arch,” (which is the name of a package in Debian; I don’t quite understand it yet really). I think the error represents a failure of the repositories serving the build containers.
So the problem occurs when I use only the one “repository path:” Debian:Next/standard. Please help me understand the Debian stuff; I’m coming from the Fedora world. I don’t know exactly which release of Debian is “Next.” Is that “Unstable” as in Sid, or “Testing” which is Bullseye or 11? I wish they just used version numbers only…
When I added the repository path “Debian:Testing/update” my packages built. But now I think that means my packages are pegged to Debian 11 and not the “Debian Sid” that is my goal.