[opensuse-kde] KDE:Qt5, KDE:Frameworks5, KDE:Applications publishing disabled
Hello, as the subject says, this was done to allow checking in the latest Qt 5.9.1 without causing breakage. Publishing will be re-enabled once we made sure Qt 5.9.1 builds correctly. -- Luca Beltrame - KDE Forums team GPG key ID: A29D259B -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Samstag, 1. Juli 2017, 10:21:21 CEST schrieb Luca Beltrame:
Hello,
as the subject says, this was done to allow checking in the latest Qt 5.9.1 without causing breakage.
Publishing will be re-enabled once we made sure Qt 5.9.1 builds correctly.
...actually... on KDE:Frameworks5 publishing is enabled for Leap 42.2. Breaks installations on every 42.2 system that uses KDE:Frameworks5. Still, the general idea is right.
Am Sonntag, 2. Juli 2017, 11:06:23 CEST schrieb Mathias Homann:
...actually... on KDE:Frameworks5 publishing is enabled for Leap 42.2. You are wrong, publishing is disabled: https://build.opensuse.org/repositories/KDE:Frameworks5
Breaks installations on every 42.2 system that uses KDE:Frameworks5. It definitely didn't "break" mine... ;-) Actually, I saw no problem at all here.
Still, the general idea is right. Maybe it would also be good to disable *building* in KDE:Qt5 for Leap in such cases. I think that's how it was done in the past... This will prevent other repos already building against the new version (and publishing the packages) while KDE:Qt5 is not published yet.
Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 2. Juli 2017, 12:01:06 CEST schrieb Wolfgang Bauer:
Am Sonntag, 2. Juli 2017, 11:06:23 CEST schrieb Mathias Homann:
...actually... on KDE:Frameworks5 publishing is enabled for Leap 42.2.
You are wrong, publishing is disabled: https://build.opensuse.org/repositories/KDE:Frameworks5
Breaks installations on every 42.2 system that uses KDE:Frameworks5.
It definitely didn't "break" mine... ;-) Actually, I saw no problem at all here.
Still, the general idea is right.
Maybe it would also be good to disable *building* in KDE:Qt5 for Leap in such cases. I think that's how it was done in the past... This will prevent other repos already building against the new version (and publishing the packages) while KDE:Qt5 is not published yet.
Maybe it would be a good thing if the build service would look at the "publish" setting of a repo to determine which version of the packages to use for building against, in other repos? Cheers Mathias
On Jul 02 2017, Mathias Homann
Maybe it would be a good thing if the build service would look at the "publish" setting of a repo to determine which version of the packages to use for building against, in other repos?
That's the useforbuild flag. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 02.07.2017 14:58, Andreas Schwab wrote:
On Jul 02 2017, Mathias Homann
wrote: Maybe it would be a good thing if the build service would look at the "publish" setting of a repo to determine which version of the packages to use for building against, in other repos? That's the useforbuild flag.
I thought the useforbuild setting only affects other packages in the same repository? Cheers MH -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 01/07/17 09:21, Luca Beltrame wrote:
Hello,
as the subject says, this was done to allow checking in the latest Qt 5.9.1 without causing breakage.
Publishing will be re-enabled once we made sure Qt 5.9.1 builds correctly.
I take it publishing has been re-enabled? "zypper -v dup" reports this: 2 Problems: Problem: nothing provides libqt5-qtcharts = 5.9.1 needed by libQt5Charts5-5.9.1-3.1.x86_64 Problem: nothing provides libqt5-qtcharts = 5.9.1 needed by libQt5Charts5-5.9.1-3.1.x86_64 Problem: nothing provides libqt5-qtcharts = 5.9.1 needed by libQt5Charts5-5.9.1-3.1.x86_64 Solution 1: keep obsolete libQt5Charts5-5.9.0-2.1.x86_64 Solution 2: break libQt5Charts5-5.9.1-3.1.x86_64 by ignoring some of its dependencies This is with the following enabled repos: http://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_... http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.2/ http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_42.... http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_42.2 -- Regards, Vadym -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Mittwoch, 5. Juli 2017, 09:12:08 schrieb Vadym Krevs:
I take it publishing has been re-enabled?
Yes, on Sunday already.
"zypper -v dup" reports this:
2 Problems: Problem: nothing provides libqt5-qtcharts = 5.9.1 needed by libQt5Charts5-5.9.1-3.1.x86_64 Problem: nothing provides libqt5-qtcharts = 5.9.1 needed by libQt5Charts5-5.9.1-3.1.x86_64
That's a new problem, unrelated to the update. The libqt5-qtcharts package has been removed yesterday (because it only contained a license file), but the dependencies were wrong afterwards, libQt5Chart5 still required libqt5-qtcharts by mistake. Should be fixed by now. If you still get a conflict, choose to uninstall libqt5-qtcharts. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 05/07/17 12:24, Wolfgang Bauer wrote:
... That's a new problem, unrelated to the update. The libqt5-qtcharts package has been removed yesterday (because it only contained a license file), but the dependencies were wrong afterwards, libQt5Chart5 still required libqt5-qtcharts by mistake.
Should be fixed by now.
If you still get a conflict, choose to uninstall libqt5-qtcharts.
Kind Regards, Wolfgang
Thanks, that fixed it. On an unrelated note, plasmashell appears to leak memory 5-7 mb every 10 seconds (according to the Memory column in System Activity) after the latest updates. An hour ago I killed an 18Gb plasmashell process, and within minutes of restarting plasmashell's memory usage is over 800Mb. -- Regards, Vadym -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (5)
-
Andreas Schwab
-
Luca Beltrame
-
Mathias Homann
-
Vadym Krevs
-
Wolfgang Bauer