https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #33 from Martin Steigerwald <mar...@lichtvoll.de> --- I understand your frustrations, Flossy Cat. I truly do. KDEPIM has been a big trigger of frustrations for me as well. I am still also facing this bug, cause Devuan Ceres which is based on Debian Unstable also does not yet have a fixed version. Unless in Debian Experimental for Plasma 6 and KDE Gear 6 and KF 6. Soon enough I bet I have it. But I also get that you do not like to run a rolling distro. It is rough these days with the very fast development speed of the Linux kernel and other components. But I do also appreciate that the KDEPIM development team is very small. And they care about their software. That can be seen again and again like for example in the blog posts about the recent meetup they had. Also I see that the change implemented by David has more than 160 new lines and changes more than 30 other lines. That IMHO is quite a bit for a backport. But… another approach would be, to talk with openSUSE people whether a backport can be done and maybe try to bring forth a back port in cooperation between upstream and distro developers? From what I read openSUSE volunteer based team is also quite small and I am not sure whether KDEPIM is a focus for the enterprise variants of SUSE, however that could be an approach where you could use your energy in a constructive manner to resolve the issue at hand for you and others. Especially also if that fix is required by enterprises that use KDEPIM… have you consider to ask for or organize some paid development work on making a back port? Remember a lot of work on KDEPIM is volunteer work. That means it is often enough work done by people who also have to do something else to earn money. If its really the case the KDEPIM is used by a lot of enterprise customers who are affected by this bug, I think it could be possible to raise some money for a paid backport of some sort? -- You are receiving this mail because: You are watching all bug changes.
