@zhjs A few questions to further complete my understanding of potential ripple effects in the go model, these thoughts are no priority, just for my curiosity.
While the -dev is arch:all would, due to the problem any ppc64el build depending on golang-github-dgraph-io-badger-dev also fail if we'd run it right now? Or is this only affecting src:badger itself? I understand that will depend on the kind of issue, this one here is a test fail. While the first question usually then is if only the test is broken or if something is really bad on ppc64 it might still "infect" anything that build-depends on it. Do dependent builds in the go ecosystem run the tests of what they B-D on? And outside of this problem but more in general. To what extend does usually anything that has a B-D on a go package also go FTBFS if the package depended on goes FTBFS (which could be the counterpart of dynamic linked ecosystems having to remove dependencies)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078313 Title: Remove badger on ppc64el from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/badger/+bug/2078313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
