Re c, we did consider exactly what you said. My personal opinion is that on, e.g., s390x "package not found" for the metapackage is a better UX than the metapackage install being intentionally broken by "dependency not found", but open to discussion there. I guess I wonder if metapackage existing but install being broken will cause issues with tooling as well. Could it cause the meta getting stuck in proposed on future update?
More on a & b coming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2141744 Title: [needs-packaging] cuda-13-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cuda-cccl-13-1/+bug/2141744/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
