That's... not very helpful, is it? If it's a bug, then a bug report should be filed, regardless of the concerned release branch. In fact, the actual maintainer seems to agree since he has already pushed a fix for it: https://salsa.debian.org/qt-kde-team/kde/plasma-framework/-/commit/40d2d1c64ea7b807e441f0a0c9490be5852a4fe5.
I've been using testing for years without trouble, so it's more stable than you make it to be. Also, the experimental -> unstable -> testing -> stable release train model is there exactly for these situations, and testing is not an upload target nor is it a deployment dump no-one cares about, especially considering it is right before stable. Please refrain from such harsh comments in the future. Also, if you have something that should actually be shared, please send your messages to 1088...@bugs.debian.org as well so it can be properly taken into account in the mailing lists and archive at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088674. ________________________________ From: Cosmo <co...@gnumerica.org> Sent: Friday, November 29, 2024 1:04 PM To: Paul Mabileau <paul.mabil...@harfanglab.fr> Cc: debian-qt-kde@lists.debian.org <debian-qt-kde@lists.debian.org> Subject: Re: Bug#1088674: plasma-framework: 5.115.0-6 breaks Plasma It's all normal, that's why it's called testing. If you can't handle testing you should stick to stable regards -- Cosmo
