[opensuse-factory] Upcoming changes for KDE users in Tumbleweed
Some history As you may know, up to now the default PIM suite for Plasma 5 in openSUSE Tumbleweed was the KDE PIM 4.14, based on kdelibs 4.x. While upstream KDE has offered a KF5-based version since Applications 15.08, it has been originally marked as a technology preview, so we (the openSUSE community KDE team) thought it would be more prudent to stick with the 4.14 version (but offer the KF5 based PIM as an option for the daring). Fast forward to today: KDE Applications 15.12.1 have been released, and we’ve been testing and using the KF5 based PIM suite for all these months with no issues. In addition, PIM developers have been adding interesting new features and impressive speed optimization (see the blog post by PIM developer Dan Vratil), and at the same time dropped support for the the 4.14 PIM suite. What does it mean for openSUSE? This means that from the next openSUSE Tumbleweed snapshot, the old PIM 4.14.x packages will be replaced by their KF5 counterparts. Most settings should be migrated automatically, and the mail store is set in a DE-independent location, so you should not lose any data. You have two options for upgrading: 1) Start from scratch Simply recreate all your accounts in the new interface and redownload all your mail. This works best with IMAP (with setups and if you have enough bandwidth. 2) Use the PIM settings exporter You can export all your mail from KMail: under the Tools menu, there is the option Import/Export KMail Data, which you can use to create an archive with all your mails and account configurations. You need to do this before upgrading, then use the same option in KMail after upgrading to the KF5 based version to have all your accounts, calendars and mail set up. Caveats The 4.14.x and KF5 versions of the PIM stack are incompatible with each other. Therefore if you do not fully upgrade the system you will get strange issues. Ensure you update with zypper dup or with the equivalent option in YaST to ensure that all packages will be picked up. Bugs Bugs? What bugs? Software is perfect! ;) Jokes aside, if you find a bug in the PIM stack, please report it to the upstream bug tracker. If instead it’s a bug in the openSUSE packages (missing dependencies, etc.), report it to openSUSE’s Bugzilla Thanks Thanks go to the KDE PIM developers for their awesome work despite their small numbers (Laurent Montel and Dan Vratil deserve several beers each ;). See also Some history As you may know, up to now the default PIM suite for Plasma 5 in openSUSE Tumbleweed was the KDE PIM 4.14, based on kdelibs 4.x. While upstream KDE has offered a KF5-based version since Applications 15.08, it has been originally marked as a technology preview, so we (the openSUSE community KDE team) thought it would be more prudent to stick with the 4.14 version (but offer the KF5 based PIM as an option for the daring). Fast forward to today: KDE Applications 15.12.1 have been released, and we’ve been testing and using the KF5 based PIM suite for all these months with no issues. In addition, PIM developers have been adding interesting new features and impressive speed optimization (see the blog post by PIM developer Dan Vratil), and at the same time dropped support for the the 4.14 PIM suite. What does it mean for openSUSE? This means that from the next openSUSE Tumbleweed snapshot, the old PIM 4.14.x packages will be replaced by their KF5 counterparts. Most settings should be migrated automatically, and the mail store is set in a DE-independent location, so you should not lose any data. You have two options for upgrading: Start from scratch Simply recreate all your accounts in the new interface and redownload all your mail. This works best with IMAP (with setups and if you have enough bandwidth. Use the PIM settings exporter You can export all your mail from KMail: under the Tools menu, there is the option Import/Export KMail Data, which you can use to create an archive with all your mails and account configurations. You need to do this before upgrading, then use the same option in KMail after upgrading to the KF5 based version to have all your accounts, calendars and mail set up. Caveats The 4.14.x and KF5 versions of the PIM stack are incompatible with each other. Therefore if you do not fully upgrade the system you will get strange issues. Ensure you update with zypper dup or with the equivalent option in YaST to ensure that all packages will be picked up. Bugs Bugs? What bugs? Software is perfect! ;) Jokes aside, if you find a bug in the PIM stack, please report it to the upstream bug tracker. If instead it’s a bug in the openSUSE packages (missing dependencies, etc.), report it to openSUSE’s Bugzilla Thanks Thanks go to the KDE PIM developers for their awesome work despite their small numbers (Laurent Montel and Dan Vratil deserve several beers each ;) See also Luca's post here: https://www.dennogumi.org/2016/01/kdepim-changes-in-opensuse-tumbleweed/ Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op zondag 17 januari 2016 11:38:01 schreef Raymond Wooninck:
Some history As you may know, up to now the default PIM suite for Plasma 5 in openSUSE Tumbleweed was the KDE PIM 4.14, based on kdelibs 4.x. While upstream KDE has offered a KF5-based version since Applications 15.08, it has been originally marked as a technology preview, so we (the openSUSE community KDE team) thought it would be more prudent to stick with the 4.14 version (but offer the KF5 based PIM as an option for the daring).
Fast forward to today: KDE Applications 15.12.1 have been released, and we’ve been testing and using the KF5 based PIM suite for all these months with no issues. In addition, PIM developers have been adding interesting new features and impressive speed optimization (see the blog post by PIM developer Dan Vratil), and at the same time dropped support for the the 4.14 PIM suite.
What does it mean for openSUSE? This means that from the next openSUSE Tumbleweed snapshot, the old PIM 4.14.x packages will be replaced by their KF5 counterparts. Most settings should be migrated automatically, and the mail store is set in a DE-independent location, so you should not lose any data.
You have two options for upgrading:
1) Start from scratch Simply recreate all your accounts in the new interface and redownload all your mail. This works best with IMAP (with setups and if you have enough bandwidth.
2) Use the PIM settings exporter You can export all your mail from KMail: under the Tools menu, there is the option Import/Export KMail Data, which you can use to create an archive with all your mails and account configurations. You need to do this before upgrading, then use the same option in KMail after upgrading to the KF5 based version to have all your accounts, calendars and mail set up.
Caveats The 4.14.x and KF5 versions of the PIM stack are incompatible with each other. Therefore if you do not fully upgrade the system you will get strange issues. Ensure you update with zypper dup or with the equivalent option in YaST to ensure that all packages will be picked up.
Bugs Bugs? What bugs? Software is perfect! ;)
Jokes aside, if you find a bug in the PIM stack, please report it to the upstream bug tracker. If instead it’s a bug in the openSUSE packages (missing dependencies, etc.), report it to openSUSE’s Bugzilla
Thanks Thanks go to the KDE PIM developers for their awesome work despite their small numbers (Laurent Montel and Dan Vratil deserve several beers each ;).
See also Some history As you may know, up to now the default PIM suite for Plasma 5 in openSUSE Tumbleweed was the KDE PIM 4.14, based on kdelibs 4.x. While upstream KDE has offered a KF5-based version since Applications 15.08, it has been originally marked as a technology preview, so we (the openSUSE community KDE team) thought it would be more prudent to stick with the 4.14 version (but offer the KF5 based PIM as an option for the daring).
Fast forward to today: KDE Applications 15.12.1 have been released, and we’ve been testing and using the KF5 based PIM suite for all these months with no issues. In addition, PIM developers have been adding interesting new features and impressive speed optimization (see the blog post by PIM developer Dan Vratil), and at the same time dropped support for the the 4.14 PIM suite.
What does it mean for openSUSE? This means that from the next openSUSE Tumbleweed snapshot, the old PIM 4.14.x packages will be replaced by their KF5 counterparts. Most settings should be migrated automatically, and the mail store is set in a DE-independent location, so you should not lose any data.
You have two options for upgrading:
Start from scratch Simply recreate all your accounts in the new interface and redownload all your mail. This works best with IMAP (with setups and if you have enough bandwidth.
Use the PIM settings exporter You can export all your mail from KMail: under the Tools menu, there is the option Import/Export KMail Data, which you can use to create an archive with all your mails and account configurations. You need to do this before upgrading, then use the same option in KMail after upgrading to the KF5 based version to have all your accounts, calendars and mail set up.
Caveats The 4.14.x and KF5 versions of the PIM stack are incompatible with each other. Therefore if you do not fully upgrade the system you will get strange issues. Ensure you update with zypper dup or with the equivalent option in YaST to ensure that all packages will be picked up.
Bugs Bugs? What bugs? Software is perfect! ;)
Jokes aside, if you find a bug in the PIM stack, please report it to the upstream bug tracker. If instead it’s a bug in the openSUSE packages (missing dependencies, etc.), report it to openSUSE’s Bugzilla
Thanks Thanks go to the KDE PIM developers for their awesome work despite their small numbers (Laurent Montel and Dan Vratil deserve several beers each ;)
See also Luca's post here: https://www.dennogumi.org/2016/01/kdepim-changes-in-opensuse-tumbleweed/
Regards
Raymond
Not quite clear to me: simply updating/upgrading ( assuming that package install is OK ) is not enough? Everyone SHOULD either start clean OR export/import ? -- Gertjan Lettink, a.k.a. Knurpht Official openSUSE Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il Sun, 17 Jan 2016 15:27:36 +0100, Knurpht - Gertjan Lettink ha scritto:
Not quite clear to me: simply updating/upgrading ( assuming that package install is OK ) is not enough? Everyone SHOULD either start clean OR export/import ?
I have talked with the KDE PIM developers and the options are actually 3: 1. Fully automatic upgrade: just use the the new programs. 2. Start clean 3. Import / Export What's far more important is that Akonadi *should not be running* during the upgrade. To stop Akonadi, close all PIM applications, open a terminal and issue akonadictl stop. Alternatively, open the akonadiconsole program, and select *Stop Server* from the *Server* menu. Lastly, you can do the upgrade from a different user account. I have updated the blog post with the suggested course of action. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: A29D259B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op zondag 17 januari 2016 16:37:24 schreef Luca Beltrame:
Il Sun, 17 Jan 2016 15:27:36 +0100, Knurpht - Gertjan Lettink ha scritto:
Not quite clear to me: simply updating/upgrading ( assuming that package install is OK ) is not enough? Everyone SHOULD either start clean OR export/import ?
I have talked with the KDE PIM developers and the options are actually 3:
1. Fully automatic upgrade: just use the the new programs. 2. Start clean 3. Import / Export
What's far more important is that Akonadi *should not be running* during the upgrade.
To stop Akonadi, close all PIM applications, open a terminal and issue akonadictl stop. Alternatively, open the akonadiconsole program, and select *Stop Server* from the *Server* menu. Lastly, you can do the upgrade from a different user account.
I have updated the blog post with the suggested course of action. Thanks for the update. I couldn't believe option 1 would not be there. -- Gertjan Lettink, a.k.a. Knurpht
Official openSUSE Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il Sun, 17 Jan 2016 17:51:58 +0100, Knurpht - Gertjan Lettink ha scritto:
Thanks for the update. I couldn't believe option 1 would not be there.
My fault, actually - I've been using KF5 PIM since their first release, and at the time upgrades weren't available. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: A29D259B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op zondag 17 januari 2016 17:15:53 schreef Luca Beltrame:
Il Sun, 17 Jan 2016 17:51:58 +0100, Knurpht - Gertjan Lettink ha scritto:
Thanks for the update. I couldn't believe option 1 would not be there.
My fault, actually - I've been using KF5 PIM since their first release, and at the time upgrades weren't available.
Maybe spread a corrected post? Before a lot of noise arises? -- Gertjan Lettink, a.k.a. Knurpht Official openSUSE Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il Mon, 18 Jan 2016 10:33:35 +0100, Knurpht - Gertjan Lettink ha scritto:
Maybe spread a corrected post? Before a lot of noise arises?
I have amended my blog post yesterday including the new information. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: A29D259B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Sonntag, 17. Januar 2016, 16:37:24 schrieb Luca Beltrame:
What's far more important is that Akonadi *should not be running* during the upgrade.
To stop Akonadi, close all PIM applications, open a terminal and issue akonadictl stop. Alternatively, open the akonadiconsole program, and select *Stop Server* from the *Server* menu. Lastly, you can do the upgrade from a different user account.
The problem with that is: How do you know before running "zypper up" that the PIM upgrade is coming now and you need to stop akonadi before ? Couldn't this be done by a smart upgrade procedure automagically ? That would be a much better user experience -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Jan 17, 2016 at 06:15:51PM +0100, Markus Koßmann wrote:
Am Sonntag, 17. Januar 2016, 16:37:24 schrieb Luca Beltrame:
What's far more important is that Akonadi *should not be running* during the upgrade.
To stop Akonadi, close all PIM applications, open a terminal and issue akonadictl stop. Alternatively, open the akonadiconsole program, and select *Stop Server* from the *Server* menu. Lastly, you can do the upgrade from a different user account.
The problem with that is: How do you know before running "zypper up" that the PIM upgrade is coming now and you need to stop akonadi before ?
Now that we have been warned, I guess we can simply run "zypper update" and if it shows tons of KDE related packages to update, log out from KDE and run "zypper dup" from a text console. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Michal Kubecek <mkubecek@suse.cz> [01-17-16 16:40]:
On Sun, Jan 17, 2016 at 06:15:51PM +0100, Markus Koßmann wrote:
Am Sonntag, 17. Januar 2016, 16:37:24 schrieb Luca Beltrame:
What's far more important is that Akonadi *should not be running* during the upgrade.
To stop Akonadi, close all PIM applications, open a terminal and issue akonadictl stop. Alternatively, open the akonadiconsole program, and select *Stop Server* from the *Server* menu. Lastly, you can do the upgrade from a different user account.
The problem with that is: How do you know before running "zypper up" that the PIM upgrade is coming now and you need to stop akonadi before ?
Now that we have been warned, I guess we can simply run "zypper update" and if it shows tons of KDE related packages to update, log out from KDE and run "zypper dup" from a text console.
Or just run "zypper dup" normally as was advised early in tw's history. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le 17/01/2016 22:59, Patrick Shanahan a écrit :
Or just run "zypper dup" normally as was advised early in tw's history.
but seems really deprecated nowadays jdd -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
18.01.2016 00:59, Patrick Shanahan пишет:
* Michal Kubecek <mkubecek@suse.cz> [01-17-16 16:40]:
On Sun, Jan 17, 2016 at 06:15:51PM +0100, Markus Koßmann wrote:
Am Sonntag, 17. Januar 2016, 16:37:24 schrieb Luca Beltrame:
What's far more important is that Akonadi *should not be running* during the upgrade.
To stop Akonadi, close all PIM applications, open a terminal and issue akonadictl stop. Alternatively, open the akonadiconsole program, and select *Stop Server* from the *Server* menu. Lastly, you can do the upgrade from a different user account.
The problem with that is: How do you know before running "zypper up" that the PIM upgrade is coming now and you need to stop akonadi before ?
Now that we have been warned, I guess we can simply run "zypper update" and if it shows tons of KDE related packages to update, log out from KDE and run "zypper dup" from a text console.
Or just run "zypper dup" normally as was advised early in tw's history.
And how exactly does it help in this case? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Andrei Borzenkov -
jdd -
Knurpht - Gertjan Lettink -
Luca Beltrame -
Markus Koßmann -
Michal Kubecek -
Patrick Shanahan -
Raymond Wooninck