https://bugs.kde.org/show_bug.cgi?id=386665
--- Comment #18 from Martin Steigerwald <mar...@lichtvoll.de> --- (In reply to David Edmundson from comment #17) > My previous stance was that we can't/shouldn't port until pulseaudio > upstream has something to port to. It seems everyone seems to have different expectations here: - Pulseaudio project appears to expect that people port over to gsettings at the *first* release with gsettings module, maybe due to technical difficulties of providing both modules (and synchronisation between them). - Debian Pulseaudio package maintainer just uploaded Pulseaudio to upstream, instead of providing it in experimental in order to allow packages to be ported, arguing that gconf module has been deprecated (without proper replacement) since a long time. - KDE upstream expects to have something stable to port to before starting the work. All totally valid expectations, each with their own reasons. Just they do not go well together. Clearly communication about how to coordinate this migration has been missing. I am just trying to make up for that now as the past is how it is. So instead of trying to point at each over in an attempt to fix the past, I think it is helpful to work constructively to resolve the issue in the here and now. > That is now the case, so I'll make the port. No need to keep flooding my > inbox. It won't happen before 5.14. So that means dropping gconf module support seems to be the only valid option. My question at what functionality would break for our users from Comment #7 remains unanswered so far. Does anyway actually now it? Sure one can argue they are "just" Debian Testing/Sid users, but leaving important functionality broken for them for a extended period of time is not nice to their willingness to take some risk in order to test the development versions of Debian. Also depending on release schedule and Debian Qt/KDE team decision Plasma 5.14 may *not* end up in next Debian stable, meaning that the affected functionality may be broken for the next stable release. Plus all Ubuntu releases depending Debian at a certain point in time. I.e. for *years* to come. So can anyone answer whether any important functionality breaks when building without gconf support (and any replacement for it)? -- You are receiving this mail because: You are watching all bug changes.
