On Wednesday, May 5, 2021 1:11:58 PM CDT Thorsten Kukuk wrote:
That's TW, neither Leap nor SLE, so maintenance and others are not getting informed and nobody has on the radar that other products are affected, too.
If there is a bug on a product, report that bug for that product, so that everybody can track it correct, and don't hope that by accident the right people stumble about such bug reports.
At this point it is a matter of semantics. - 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. Or - Is the bug against Leap since it has not made updates to be compatible with the TW container? 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. The product against which the bug should be filed is not quite straight forward. At this point since the TW change is not going to be rolled back a Leap bug certainly makes sense, but originally a rollback of TW package was the most responsible. If I need to file a separate bug let me know, just hoping this is fixed and per my other email where TW stands on breaking container changes being blocked. -- Jimmy