Re: Asking for an exception to include a feature into 17.08
On 04.08.2017 22:54, Alexey Min wrote: Hi, I just wanted to ask if it is acceptable to push https://phabricator.kde.org/D6319 to 17.08 branch before release? In short, it would improve user experience by not making them manually edit config file ~/.config/krfbrc. In details: after removing old "x11" plugin and replacing it with "xcb" (which was done in https://phabricator.kde.org/D5211 ) that config file may have remaining incorrect "x11" saved setting, or as I suggested in https://bugs.kde.org/show_bug.cgi?id=356782#c6, "qt". With D6319, users having "x11" will be automatically switched to "xcb", and those having "qt", may go to "Settings -> Configure Desktop Sharing..." and change preference there; in both cases avoiding manual editing of config file. Sorry for an inconvenience. Cheers, Alexey Minnekhanov Hi Alexey, nobody raised any concern. If you are confident that the patch improves more than it breaks, you are granted the exception for the Applications/17.08 branch of 'krfb'. We are really tight to tagging, so I suggest to commit it as soon as you are reading this. Otherwise, the new strings might released untranslated. With some luck, it also gives us a week to do final testing of your work. Thanks, Christoph Feck
Re: KF 5.37 requiring Qt 5.7
El dilluns, 7 d’agost de 2017, a les 9:46:59 CEST, Rex Dieter va escriure: > David Faure wrote: > > On mercredi 2 août 2017 22:55:10 CEST Rex Dieter wrote: > >> David Faure wrote: > >> > According to the policy that KF5 should work with the last 3 releases > >> > of Qt5.x, it is time now for upcoming releases of KF5 to drop support > >> > for Qt 5.6. > >> > > >> > Packagers: is that acceptable? > >> > >> I'd prefer to continue to allow 5.6 awhile, to continue to allow support > >> for rhel 7. > > > > That's curious, how do you package the parts of KDE Applications or > > Workspace that already require Qt 5.7 ? > > I haven't packaged those pieces yet. > > Sounds like you may have moved forward anyway, so I guess I'll have to start > the process of removing KF5 from the EPEL addon repository for rhel7. I > shame, I and a few others did a fair amount of work to get that in. Maybe you should try helping with the Flatpack builds, i guess/hope rhel7 as support for flatpack so for me it seems the more natural way to provide rhel7 users with up to date KDE software. Cheers, Albert > > -- Rex
Re: KF 5.37 requiring Qt 5.7
David Faure wrote: > On lundi 7 août 2017 18:25:35 CEST Rex Dieter wrote: >> David Faure wrote: >> >> > Isn't it an option to leave it in, at version 5.36, rather than >> >> > removing it completely ? >> >> >> >> In the short-term, yes. >> >> >> >> Long term, I'm not willing to ship (and support) this if it's not >> >> supported upstream either (where bugs are usually fixed in newer >> >> releases). >> > >> > I thought you said that long term you were looking at upgrading to Qt >> > 5.9... >> >> I may or may not be successful. >> >> > In any case I'm not sure why Qt's promise to maintain 5.6 for 3 years >> > means that all Qt-based libraries must promise the same. >> >> , you asked for feedback, and I gave it. I'm just spelling out >> the results of implementing the change now => dropping support for RHEL7 > > That's unfortunate, which is why I'm still trying to discuss and find > solutions with you, but we just can't support Qt 5.6 forever. > > Does RHEL have additional optional repos that allow upgrading (e.g. to a > newer Qt), like OpenSuSE has? Then it wouldn't be "completely dropping out > of RHEL7", but "requiring an extra repo". Not as good as a core package, > but still a possibility for those who might need it. Policy for any official-ish addon repos is that they cannot replace any core packages (Qt5 is that). So, in general no. I see no alternatives for *now*. This is why I'd suggested waiting until we knew more, but I can also accept letting kf5 move forward and waiting/hoping for a better Qt5 solution on our end too. -- Rex
Re: KF 5.37 requiring Qt 5.7
On lundi 7 août 2017 18:25:35 CEST Rex Dieter wrote: > David Faure wrote: > >> > Isn't it an option to leave it in, at version 5.36, rather than > >> > removing it completely ? > >> > >> In the short-term, yes. > >> > >> Long term, I'm not willing to ship (and support) this if it's not > >> supported upstream either (where bugs are usually fixed in newer > >> releases). > > > > I thought you said that long term you were looking at upgrading to Qt > > 5.9... > > I may or may not be successful. > > > In any case I'm not sure why Qt's promise to maintain 5.6 for 3 years > > means that all Qt-based libraries must promise the same. > > , you asked for feedback, and I gave it. I'm just spelling out the > results of implementing the change now => dropping support for RHEL7 That's unfortunate, which is why I'm still trying to discuss and find solutions with you, but we just can't support Qt 5.6 forever. Does RHEL have additional optional repos that allow upgrading (e.g. to a newer Qt), like OpenSuSE has? Then it wouldn't be "completely dropping out of RHEL7", but "requiring an extra repo". Not as good as a core package, but still a possibility for those who might need it. > It's up to you if you choose to implement changes that means some downstream > distros cannot (reasonably) use your (latest/supported) software anymore. s/some/one/. Everyone else said OK, so I went ahead. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: KF 5.37 requiring Qt 5.7
David Faure wrote: >> > Isn't it an option to leave it in, at version 5.36, rather than >> > removing it completely ? >> >> In the short-term, yes. >> >> Long term, I'm not willing to ship (and support) this if it's not >> supported upstream either (where bugs are usually fixed in newer >> releases). > > I thought you said that long term you were looking at upgrading to Qt > 5.9... I may or may not be successful. > In any case I'm not sure why Qt's promise to maintain 5.6 for 3 years > means that all Qt-based libraries must promise the same. , you asked for feedback, and I gave it. I'm just spelling out the results of implementing the change now => dropping support for RHEL7 It's up to you if you choose to implement changes that means some downstream distros cannot (reasonably) use your (latest/supported) software anymore. -- Rex
Re: KF 5.37 requiring Qt 5.7
On lundi 7 août 2017 17:36:05 CEST Rex Dieter wrote: > David Faure wrote: > > On lundi 7 août 2017 16:46:59 CEST Rex Dieter wrote: > >> David Faure wrote: > >> > On mercredi 2 août 2017 22:55:10 CEST Rex Dieter wrote: > >> >> David Faure wrote: > >> >> > According to the policy that KF5 should work with the last 3 > >> >> > releases of Qt5.x, it is time now for upcoming releases of KF5 to > >> >> > drop support for Qt 5.6. > >> >> > > >> >> > Packagers: is that acceptable? > >> >> > >> >> I'd prefer to continue to allow 5.6 awhile, to continue to allow > >> >> support for rhel 7. > >> > > >> > That's curious, how do you package the parts of KDE Applications or > >> > Workspace that already require Qt 5.7 ? > >> > >> I haven't packaged those pieces yet. > >> > >> Sounds like you may have moved forward anyway, so I guess I'll have to > >> start > >> the process of removing KF5 from the EPEL addon repository for rhel7. I > >> shame, I and a few others did a fair amount of work to get that in. > > > > Isn't it an option to leave it in, at version 5.36, rather than removing > > it completely ? > > In the short-term, yes. > > Long term, I'm not willing to ship (and support) this if it's not supported > upstream either (where bugs are usually fixed in newer releases). I thought you said that long term you were looking at upgrading to Qt 5.9... In any case I'm not sure why Qt's promise to maintain 5.6 for 3 years means that all Qt-based libraries must promise the same. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: KF 5.37 requiring Qt 5.7
David Faure wrote: > On lundi 7 août 2017 16:46:59 CEST Rex Dieter wrote: >> David Faure wrote: >> > On mercredi 2 août 2017 22:55:10 CEST Rex Dieter wrote: >> >> David Faure wrote: >> >> > According to the policy that KF5 should work with the last 3 >> >> > releases of Qt5.x, it is time now for upcoming releases of KF5 to >> >> > drop support for Qt 5.6. >> >> > >> >> > Packagers: is that acceptable? >> >> >> >> I'd prefer to continue to allow 5.6 awhile, to continue to allow >> >> support for rhel 7. >> > >> > That's curious, how do you package the parts of KDE Applications or >> > Workspace that already require Qt 5.7 ? >> >> I haven't packaged those pieces yet. >> >> Sounds like you may have moved forward anyway, so I guess I'll have to >> start >> the process of removing KF5 from the EPEL addon repository for rhel7. I >> shame, I and a few others did a fair amount of work to get that in. > > Isn't it an option to leave it in, at version 5.36, rather than removing > it completely ? In the short-term, yes. Long term, I'm not willing to ship (and support) this if it's not supported upstream either (where bugs are usually fixed in newer releases). -- Rex
Re: KF 5.37 requiring Qt 5.7
On lundi 7 août 2017 16:46:59 CEST Rex Dieter wrote: > David Faure wrote: > > On mercredi 2 août 2017 22:55:10 CEST Rex Dieter wrote: > >> David Faure wrote: > >> > According to the policy that KF5 should work with the last 3 releases > >> > of Qt5.x, it is time now for upcoming releases of KF5 to drop support > >> > for Qt 5.6. > >> > > >> > Packagers: is that acceptable? > >> > >> I'd prefer to continue to allow 5.6 awhile, to continue to allow support > >> for rhel 7. > > > > That's curious, how do you package the parts of KDE Applications or > > Workspace that already require Qt 5.7 ? > > I haven't packaged those pieces yet. > > Sounds like you may have moved forward anyway, so I guess I'll have to start > the process of removing KF5 from the EPEL addon repository for rhel7. I > shame, I and a few others did a fair amount of work to get that in. Isn't it an option to leave it in, at version 5.36, rather than removing it completely ? -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: KF 5.37 requiring Qt 5.7
David Faure wrote: > On mercredi 2 août 2017 22:55:10 CEST Rex Dieter wrote: >> David Faure wrote: >> > According to the policy that KF5 should work with the last 3 releases >> > of Qt5.x, it is time now for upcoming releases of KF5 to drop support >> > for Qt 5.6. >> > >> > Packagers: is that acceptable? >> >> I'd prefer to continue to allow 5.6 awhile, to continue to allow support >> for rhel 7. > > That's curious, how do you package the parts of KDE Applications or > Workspace that already require Qt 5.7 ? I haven't packaged those pieces yet. Sounds like you may have moved forward anyway, so I guess I'll have to start the process of removing KF5 from the EPEL addon repository for rhel7. I shame, I and a few others did a fair amount of work to get that in. -- Rex
