On Wednesday, 5 May 2021 22.00.06 CEST Thorsten Kukuk wrote:
On Wed, May 05, Jimmy Berry wrote:
At this point it is a matter of semantics.
No, there is one clear bug in the container runtime.
- Is the bug against TW since it updated a package such that the container would be incompatible with other hosts such as Leap and thus break the fundamental feature of a TW container.
No, the change in TW was correct.
Or
- Is the bug against Leap since it has not made updates to be compatible with the TW container?
It's a bug in the container runtime/seccomp handling of Leap.
If the first the bug was filed correctly. If the second either a) circle back to my comment about blocking the update, or b) at the very least the maintainer who knowingly made the incompatible change could file a maintenance bug.
Neither one. The bug is in the container runtime, and that is different on every product. So you need single bugs for every product which contains this bug to track that a fix get's released there.
Right, and it should be obvious that users need help by experts in the corresponding field creating these bug reports because – call me stupid, if you like – but even being a SUSE QA engineer I would not be able to achieve that by myself for every issue that I hit. Regards, Oliver