[opensuse-kde] Team meeting planned for Tuesday 24 September 18:30 UTC
Dear Listmates, It has already been quite some time that we had a team meeting and given the upcoming 13.1 release, I would like to discuss the current status of KDE 4.11 and to see what is still missing or what needs polishing for the openSUSE 13.1 release. My proposal would be to have the meeting on Tuesday 24 September at the usual time (18:30 UTC). The agenda for the meeting can be found here : https://en.opensuse.org/openSUSE:KDE_meeting#Next_Meeting:_2013-09-24_Time:_... Feel free to add the topics that you would like to discuss during the meeting. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sunday 15 Sep 2013 13:09:46 Raymond Wooninck wrote:
Dear Listmates,
It has already been quite some time that we had a team meeting and given the upcoming 13.1 release, I would like to discuss the current status of KDE 4.11 and to see what is still missing or what needs polishing for the openSUSE 13.1 release.
My proposal would be to have the meeting on Tuesday 24 September at the usual time (18:30 UTC).
The agenda for the meeting can be found here :
https://en.opensuse.org/openSUSE:KDE_meeting#Next_Meeting:_2013-09-24_Time:_ 1830_UTC
Feel free to add the topics that you would like to discuss during the meeting.
Regards
Raymond
Unfortunately, I won't be able to make it that week, but one thing that has been bugging me since 4.11.0 is described at the following bug report and probably needs polishing for 13.1 release (an upstream-problem though): https://bugs.kde.org/show_bug.cgi?id=324831 Nico
On Tuesday 17 September 2013 15:57:24 Nico Kruber wrote:
Unfortunately, I won't be able to make it that week, but one thing that has been bugging me since 4.11.0 is described at the following bug report and probably needs polishing for 13.1 release (an upstream-problem though): https://bugs.kde.org/show_bug.cgi?id=324831
Hi Nico, I doubt if this bug will be solved before 13.1. It is the similar to bug https://bugs.kde.org/show_bug.cgi?id=312460, where you can see the unread counter for a certain folder, but the folder itself doesn't show any new emails until you restart kmail. Upstream knows about it, but it seems very hard to trace and really to debug it. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 17 Sep 2013 19:20:12 Raymond Wooninck wrote:
On Tuesday 17 September 2013 15:57:24 Nico Kruber wrote:
Unfortunately, I won't be able to make it that week, but one thing that has been bugging me since 4.11.0 is described at the following bug report and probably needs polishing for 13.1 release (an upstream-problem though): https://bugs.kde.org/show_bug.cgi?id=324831
Hi Nico,
I doubt if this bug will be solved before 13.1. It is the similar to bug https://bugs.kde.org/show_bug.cgi?id=312460, where you can see the unread counter for a certain folder, but the folder itself doesn't show any new emails until you restart kmail.
hmm - I never experienced that bug but now subscribed just in case and to get some more details... I'm also not quite sure that it is the same thing as I'm only seeing my bug since 4.11.0 - 4.10.x has been fine but there are probably a lot of changes so it's not easy to find the culprit here, I guess I noticed one more thing though but didn't go through bugs.kde.org yet to check for a bug report: sometimes IMAP accounts get stuck on an old view and refuse to update from the server - restarting akonadi and kontact eventually helps So overall, KMail seems more responsive but has again gained some more bugs :(
Upstream knows about it, but it seems very hard to trace and really to debug it.
If I only had more time, I'd try going through the code myself... But my hopes are up that someone will eventually find and fix these annoying things. Anyway, we can deliver fixes later if not solved before 13.1, just wanted to raise the things I noticed - apart from that, I'm fine with the current state. One more topic for the meeting could be what we discussed last time, i.e. which packages (apps vs. KDE libs) go into which repo (KDF/KR411 vs. KDE:Extra). There seems to be quite a mix, e.g. digikam in KR411, skanlite not any more etc. Nico
On Tuesday 17 Sep 2013 23:56:10 you wrote:
One more topic for the meeting could be what we discussed last time, i.e. which packages (apps vs. KDE libs) go into which repo (KDF/KR411 vs. KDE:Extra). There seems to be quite a mix, e.g. digikam in KR411, skanlite not any more etc.
sorry, I meant KUA, not KDE:Extra
Onsdag den 18. september 2013 10:39:05 skrev Nico Kruber:
On Tuesday 17 Sep 2013 23:56:10 you wrote:
One more topic for the meeting could be what we discussed last time, i.e. which packages (apps vs. KDE libs) go into which repo (KDF/KR411 vs. KDE:Extra). There seems to be quite a mix, e.g. digikam in KR411, skanlite not any more etc.
sorry, I meant KUA, not KDE:Extra
KUA is for packages which *do* exist in KDF (links to KDF, not "real" packages). So a "mix" is expected, in fact if packages exist in KUA, which do not exist in KDF something is wrong. KUA should not be used with KR4XX, KUA is strictly an add-on repo for people using the stable, officially released, tested KDE packages, but who would like updated versions of non-SC apps like amarok. Shared libs should not be in KUA at all. Only if they're special libs only used by single KDE apps - e.g. libbluedevil or libkdevplatform. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 23 Sep 2013 17:56:53 Martin Schlander wrote:
Onsdag den 18. september 2013 10:39:05 skrev Nico Kruber:
On Tuesday 17 Sep 2013 23:56:10 you wrote:
One more topic for the meeting could be what we discussed last time, i.e. which packages (apps vs. KDE libs) go into which repo (KDF/KR411 vs. KDE:Extra). There seems to be quite a mix, e.g. digikam in KR411, skanlite not any more etc.
sorry, I meant KUA, not KDE:Extra
KUA is for packages which *do* exist in KDF (links to KDF, not "real" packages). So a "mix" is expected, in fact if packages exist in KUA, which do not exist in KDF something is wrong.
KUA should not be used with KR4XX, KUA is strictly an add-on repo for people using the stable, officially released, tested KDE packages, but who would like updated versions of non-SC apps like amarok.
This is how I understood it, too, which in turn means that all (stable) packages for applications in KDF should also be in KR4XX. However, there during the creation of KR411 a different policy was used which removed several of these applications, e.g. skanlite, kmymoney from KR411. Nico
Mandag den 30. september 2013 13:32:51 skrev Nico Kruber:
On Monday 23 Sep 2013 17:56:53 Martin Schlander wrote:
KUA is for packages which *do* exist in KDF (links to KDF, not "real" packages). So a "mix" is expected, in fact if packages exist in KUA, which do not exist in KDF something is wrong.
KUA should not be used with KR4XX, KUA is strictly an add-on repo for people using the stable, officially released, tested KDE packages, but who would like updated versions of non-SC apps like amarok.
This is how I understood it, too, which in turn means that all (stable) packages for applications in KDF should also be in KR4XX. However, there during the creation of KR411 a different policy was used which removed several of these applications, e.g. skanlite, kmymoney from KR411.
Possibly. But that's an issue with KR411 policies then, or possibly just a maintenance oversight for KR411. I'm sure help is welcome for maintaining the links in KR4XX. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Martin Schlander wrote:
Mandag den 30. september 2013 13:32:51 skrev Nico Kruber:
On Monday 23 Sep 2013 17:56:53 Martin Schlander wrote:
KUA is for packages which *do* exist in KDF (links to KDF, not "real" packages). So a "mix" is expected, in fact if packages exist in KUA, which do not exist in KDF something is wrong.
KUA should not be used with KR4XX, KUA is strictly an add-on repo for people using the stable, officially released, tested KDE packages, but who would like updated versions of non-SC apps like amarok.
This is how I understood it, too, which in turn means that all (stable) packages for applications in KDF should also be in KR4XX. However, there during the creation of KR411 a different policy was used which removed several of these applications, e.g. skanlite, kmymoney from KR411.
Possibly. But that's an issue with KR411 policies then, or possibly just a maintenance oversight for KR411.
I'm sure help is welcome for maintaining the links in KR4XX.
I see that this is possibly a lack of manpower. But I just realized that even the virtuoso packages are missing in KR411. Using the ones from download.opensuse.org/update seems to have problems: Nepomuk is not working correctly, especially issuing a nepomukctl restart results in the error message: nepomukstorage(5929)/nepomuk (storage service): "Failed to start Virtuoso" Regards, Stefan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 01 October 2013 12:08:22 Stefan Vater wrote:
I see that this is possibly a lack of manpower. But I just realized that even the virtuoso packages are missing in KR411. Using the ones from download.opensuse.org/update seems to have problems: Nepomuk is not working correctly, especially issuing a
Why would we include a type of system package into KR411 ? This would be same as indicating that mysql is missing from KR411. KR411 should have as target to provide a newer KDE experience to the users, not as an update repository for a big part of the system.
nepomukctl restart
results in the error message:
nepomukstorage(5929)/nepomuk (storage service): "Failed to start Virtuoso"
The 12.3 Update repo would have exactly the same version as that KR411 would provide as that virtuoso is still at version 6.1.6. So if you can reproduce this, then it should be reported as a bug. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Hi. Thanks for the quick annswer! Raymond Wooninck wrote:
On Tuesday 01 October 2013 12:08:22 Stefan Vater wrote:
I see that this is possibly a lack of manpower. But I just realized that even the virtuoso packages are missing in KR411. Using the ones from download.opensuse.org/update seems to have problems: Nepomuk is not working correctly, especially issuing a
Why would we include a type of system package into KR411 ? This would be same as indicating that mysql is missing from KR411. KR411 should have as target to provide a newer KDE experience to the users, not as an update repository for a big part of the system.
OK, that sounds reasonable. I just saw that it was part of KR410, so I thought it might be an issue...
nepomukctl restart
results in the error message:
nepomukstorage(5929)/nepomuk (storage service): "Failed to start Virtuoso"
The 12.3 Update repo would have exactly the same version as that KR411 would provide as that virtuoso is still at version 6.1.6. So if you can reproduce this, then it should be reported as a bug.
I will check if the problem persits. Is there any possibility to get more information about what's going wrong? Apart from that, what about the missing apps, like skanlite, kmymoney etc.? Where shall I take these from? Regards, Stefan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Stefan Vater wrote:
nepomukctl restart
results in the error message:
nepomukstorage(5929)/nepomuk (storage service): "Failed to start Virtuoso"
The 12.3 Update repo would have exactly the same version as that KR411 would provide as that virtuoso is still at version 6.1.6. So if you can reproduce this, then it should be reported as a bug.
I will check if the problem persits. Is there any possibility to get more information about what's going wrong?
Ok, it seems to be the bug described in https://bugs.kde.org/show_bug.cgi?id=286953. After deleting the soprano- virtuoso.trx file virtuoso is working again. Thanks, Stefan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Wednesday 02 of October 2013 10:37:44 Stefan Vater wrote:
Ok, it seems to be the bug described in https://bugs.kde.org/show_bug.cgi?id=286953. After deleting the soprano- virtuoso.trx file virtuoso is working again.
This fix has also been added to KDF/O:F/13.1, but i forgot to send it to kr411. Done now...
participants (5)
-
Martin Schlander -
Nico Kruber -
Raymond Wooninck -
Stefan Vater -
šumski