On 09.02.2018 13:17, H.Merijn Brand wrote:
On Fri, 9 Feb 2018 12:59:31 +0100, Lars Marowsky-Bree <lmb@suse.com> wrote:
On 2018-02-08T10:40:35, Luca Beltrame <lbeltrame@kde.org> wrote:
Mesa wrote broken caches, but you don't notice when they are written, but when they are read back (program restarts etc.). That's why even after the update you have to remove the cache: the crashy data has been already written to disk.
And someone decided that manual intervention instead of fixing the programs to detect this and clean it up automatically was the way to go? Sigh. We're trying to drive users away, right?
TumbleWeed is bleeding edge. I hope you are aware that problems may arise. If you want automatic fixes, stick to Leap.
Your points are valid for sure. But at the same time Tumbleweed promised to deliver only stable Software. This usualy means released stuff, not Beta, not RC. Waiting for the official release *may* have prevented the Mesa18 Fallout. I love Tumbleweed for being bleeding edge while keeping a balance. In the last weeks I had the feeling some packagers are getting a bit overly confident to release early because openQA tells them *it works*. libreoffice RC => worked plasma 5.12 Beta => worked Mesa 18 RC => failed Next time we might not be so lucky to get 2 out of 3 right. my2cents, tomme -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org