23.01.2021 11:31, Stefan Seyfried пишет:
On 23.01.21 00:51, Matthias G. Eckermann wrote:
On 2021-01-22 T 12:21 +0100 Richard Biener wrote:
Oh, I see, then my comments do not apply and it's the ususal SLE "problem".
Other people would say "SLE value" of stability. SCNR:-)
Don't get me started. Config changes in a base package (LVM2) breaking SUSE's very own tools for everyone, with a bug reference that's (of course, as always) non-public.
"Stability?" "SLES?" Whom are you kidding here? Obviously this thing has gone out with zero QA testing.
Nowadays I'm really not sure if "more and more SLES in Leap" brings benefits or only pain and seriously consider switching my private servers to Tumbleweed. If I report an error against Tumbleweed, it will at least be publicly visible and often be fixed timely.
P.S: The lvm2 changelog entry * Di Jan 05 2021 heming.zhao@suse.com - lvm2 should use 'external_device_info_source="udev"' by default (bsc#1179691) - change lvm.conf item external_device_info_source from none to udev
Yes, this references to "private" bugs are also full of fun :-) Once somebody even sent me a submit request to erlang package fixing such a bug, which I could not even read :-)
The kiwi issue I had to solve to get my SLES15-SP2 images to build again: https://github.com/OSInside/kiwi/issues/1665 I don't even dare to report the issue to our DSE to get a fix for kiwi in SLES as I'm building my own version anyway.
Sorry for the rant, but SLE management being totally out of sync with reality and then spreading "alternative facts" just makes me angry.