https://bugs.kde.org/show_bug.cgi?id=500584
--- Comment #8 from Sergio <sergio.calleg...@gmail.com> --- Sorry if this appears as a bit of an aside, here, but I am trying to collect information to make a more appropriate report. LibO developers have closed the corresponding issue on their application indicating that also https://bugs.kde.org/show_bug.cgi?id=488208 is a Qt5 bug. Now the interesting bit is that they say that the bug is present on distros like arch that build Qt5 almost unpatched from the sources in the KDE repository https://invent.kde.org/qt/qt/qt5 which I understand is a repo where KDE accumulates Qt5 patches that do not make it upstream. Conversely, they say that the bug *is not present* on debian derivatives, that build Qt5 from the upstream Qt sources carrying a large number of debian-specific downstream patches (most of which, I would say, are from the KDE repo). See: https://bugs.documentfoundation.org/show_bug.cgi?id=148019#c9 > It's unclear to me why the bug doesn't show on Debian these days > (while I could reproduce there in the past), but still does on Arch. > It might e.g. be Debian has a different set of patches applied So a fix may be already floating around, remaining missed because of the quirky development model of Qt5 where at this point there seems to be no full agreement on what should be considered "upstream" and on who should review and apply patches, so that patches remain downstream-only and may get lost. So my questions are: - What is the current development model of Qt5? Is it now happening at Qt or at KDE via a soft fork? I understand it got moved at KDE because Qt stopped releasing updates to Qt5, is it still the case? - Is there a tracker to report bugs for the KDE Qt5 tree? -- You are receiving this mail because: You are watching all bug changes.
