Comment # 13 on bug 1230958 from Stefan Hundhammer

I understand, but frankly, I am very unsure whom to reassign this to.

The Qt5 libs maintainer?
Whoever puts together the Slowroll versions? (Who is that?)

This bug report may have identified a conceptual problem of Slowroll: It is
hard to pick versions consistently from Factory / Tumbleweed that are
consistent as a whole, while using reasonably new versions.

Yes, that is indeed hard; the problem with Tumbleweed is that there is ALWAYS
something that is slightly broken, at least for a little while. I used it for
many years, and at some point I was sick and tired of playing the "zypper dup"
lottery and the constant breakages.

Sometimes the sound was broken because of PulseAudio problems (i.e. no more
daily video conferences with the international team all over Europe), sometimes
the kernel was too new (say good-bye to the NVidia driver and thus to X11 and
having a desktop), sometimes the "avahi" process went berserk with 100% CPU for
hours. There was always something that was broken.

Lesson learned: A rolling release is not for the faint of heart, and you need
to be able and willing to fix things that you need for your daily work.


Slowroll is the promise to take away at least most of that trouble; because
it's rolling slower, and hopefully, somebody else will have been hit by the
problem already in Tumbleweed, and somebody will already have come up with a
fix.

But it's just delaying problems, not a guarantee at all. The brave adventurers
in the first line of battle (TW) tend to kill most of the orks that keep
coming, but some may still get through to the second line (Slowroll).

It's SLE / Leap that promises a life in peace, but even there there are some
problems. But the tradeoff is getting much older versions.