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
Re: KF 5.37 requiring Qt 5.7
On mercredi 2 août 2017 22:57:31 CEST Christoph Feck wrote: > On 02.08.2017 22:47, 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? > > > > Normally I would have just gone ahead with applying the policy, but after > > my recent finding that even some very recent distributions are still on > > Qt 5.6 LTS, I just want to make sure. > > > > (On the other hand I guess it's fine in the actual case I know about, > > given > > that the OpenSuSE KDE:Frameworks5 repo is based on Qt 5.9) > > According to https://en.wikipedia.org/wiki/Qt_version_history#Qt_5 the > 5.7 release is no longer maintained, so we have 5.6, 5.8, and 5.9 (5.5 > is still maintained, but we only support 3 three releases). The replies so that quite some distros use 5.7, so, independently from what TQC says, requiring 5.7 rather than 5.8 seems like a better idea to me. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: KF 5.37 requiring Qt 5.7
On Wed, 2 Aug 2017, 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? Normally I would have just gone ahead with applying the policy, but after my recent finding that even some very recent distributions are still on Qt 5.6 LTS, I just want to make sure. (On the other hand I guess it's fine in the actual case I know about, given that the OpenSuSE KDE:Frameworks5 repo is based on Qt 5.9) I don't see an issue for Slackware. Officially we do not even ship Plasma 5 yet (nor do we ship Qt 5) and my 'unofficial' Plasma 5 package repository is already being built against Qt 5.9. Cheers, Eric -- Eric Hameleers Home: http://alien.slackbook.org/blog/
Re: KF 5.37 requiring Qt 5.7
On 08/02/17 22:47, 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? We already have 5.9.1 in our repos and thus also have no problem with requiring 5.7. Cheers, Heiko
Re: KF 5.37 requiring Qt 5.7
On Wednesday, 2 August 2017 at 22:47, 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? Certainly no objection from Gentoo. Qt 5.7.1 is stable keyworded here and eventually will move on to 5.9.1. With Plasma-5.10.4 and Applications 17.04.3 in the process of being stabilised, a majority of packages depends on Qt 5.7 already, anyway. Regards, Andreas
Re: KF 5.37 requiring Qt 5.7
Le 2017-08-02 22:47, David Faure a écrit : 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? Normally I would have just gone ahead with applying the policy, but after my recent finding that even some very recent distributions are still on Qt 5.6 LTS, I just want to make sure. (On the other hand I guess it's fine in the actual case I know about, given that the OpenSuSE KDE:Frameworks5 repo is based on Qt 5.9) Hello, in mageia 6 we use qt 5.6 LTS but i will work on updating to Qt 5.9 LTS ( when plasma 5.12.x will be out ). So for us this is not a real problem. -- Regards, Nicolas Lécureuil Mageia KDE Team
Re: KF 5.37 requiring Qt 5.7
Also fine for FreeBSD, where on 5.7.1. mfg Tobias On 4 August 2017 at 10:09, Bernhard Rosenkraenzer wrote: > On Wednesday, August 02, 2017 22:47 CEST, 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? > > Works for OpenMandriva. We're on 5.9 on cooker (development branch) and > will release an update to 5.9 alongside the next KF and Plasma updates for > the stable branch. > > ttyl > bero > >
Re: KF 5.37 requiring Qt 5.7
On Wednesday, August 02, 2017 22:47 CEST, 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? Works for OpenMandriva. We're on 5.9 on cooker (development branch) and will release an update to 5.9 alongside the next KF and Plasma updates for the stable branch. ttyl bero
Re: KF 5.37 requiring Qt 5.7
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 ? -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: KF 5.37 requiring Qt 5.7
On 02.08.2017 22:47, 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? Normally I would have just gone ahead with applying the policy, but after my recent finding that even some very recent distributions are still on Qt 5.6 LTS, I just want to make sure. (On the other hand I guess it's fine in the actual case I know about, given that the OpenSuSE KDE:Frameworks5 repo is based on Qt 5.9) According to https://en.wikipedia.org/wiki/Qt_version_history#Qt_5 the 5.7 release is no longer maintained, so we have 5.6, 5.8, and 5.9 (5.5 is still maintained, but we only support 3 three releases).
Re: KF 5.37 requiring Qt 5.7
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. And in the meantime, will push them to rebase to something newer (5.9?) for the next point release. -- Rex
