[opensuse-kde] 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-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Raymond Wooninck writes:
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.
Do I really need to export all the mails in the local maildirs? I have several GiB of them and the ZIP used for the backup is bad at compressing them. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 17. Januar 2016, 14:07:34 schrieb Achim Gratz:
Do I really need to export all the mails in the local maildirs?
No, you don't *need* to do that. Akonadi5 should migrate the current config on first start. And even if the migration would fail for some reason, you should still be able to reconfigure it and point it to the existing maildirs. (the mails are not *stored* inside akonadi, but in the same standard locations as ever) Although, if your mails are really important to you, it's always good to have a backup... ;-) IMHO, it shouldn't even be necessary to stop Akonadi before the update as has been recommended. But the KDEPIM5 applications won't work with a running Akonadi4 server. And Akonadi4 itself will probably stop working as well if its files are being replaced underneath by the update, and it maybe won't even be possible to stop/shutdown it properly afterwards, which in itself might cause some (database) corruption or an inconsistent state. So better be safe than sorry, I'd say. And I think that's the main purpose of that "heads up" announcement. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Wolfgang Bauer writes:
No, you don't *need* to do that. Akonadi5 should migrate the current config on first start.
Thanks.
And even if the migration would fail for some reason, you should still be able to reconfigure it and point it to the existing maildirs. (the mails are not *stored* inside akonadi, but in the same standard locations as ever)
The last time a KMail migration was necessary (from mbox to maildir because the mbox didn't work and might not to this day) it took a really long time and several restarts from scratch before the whole lot was reindexed and I've lost the attachment marks for old mails that (still) have attachments. I hope to get those back… :-)
Although, if your mails are really important to you, it's always good to have a backup... ;-)
Yes, but I can at least compress them better so they don't take up so much space. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Achim Gratz writes:
The last time a KMail migration was necessary (from mbox to maildir because the mbox didn't work and might not to this day) it took a really long time and several restarts from scratch before the whole lot was reindexed and I've lost the attachment marks for old mails that (still) have attachments. I hope to get those back… :-)
I've updated my old machine to check this out and it seems that this is my lucky day and the new KMail does show me the attachment marks correctly again. The old KMail settings were not auto-converted, but it was easy enough to attach my local KMail folder (even in read-only mode, which is a nice touch). Indexing was a lot faster than before, although I'm sure it is not finished yet. But I can search for the subject lines and actually get results back. For the first time in years, I can then actually run a second search for a different topic and get results for the new search term back (that was hit-and-miss with KMail 4.x and I never figured out why it happened). Plus, the last two Plasma releases don't seem to run amok with 100% CPU after about an hour any more and in general the idle CPU consumption is back to where it was with KDE4 and so is the CPU temperature. I'm starting to think that maybe I could finally make the switch from KDE 4.x to Plasma 5 on my main machine. Still missing, though: there's no widget for the various system temperatures anymore and the system monitor widget that bundled all the various monitors doesn't appear to have been ported as well. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sunday 17 Jan 2016 11:38:01 Raymond Wooninck wrote: Great news, thanks.
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:
If we miss the announcement of the next snapshot and blindly install it, what will the result be if we have not yet used the PIM settings exporter? Will the install process give us the option to run the exporter? Can we run this exporter now and if we make some changes, can we run the exporter again with no issues?
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.
What about the "Software Updater" widget? will that not process the install?
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-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data domenica 17 gennaio 2016 16:35:26 CET, ianseeks ha scritto:
Will the install process give us the option to run the exporter?
No. And actually there shouldn't be any need for update: I checked with the PIM developers and the upgrade path should be automatic. However you must make sure Akonadi isn't running when the update is done. Check my blog post, which I updated, for more details. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: A29D259B
On Sunday 17 Jan 2016 18:12:29 Luca Beltrame wrote:
In data domenica 17 gennaio 2016 16:35:26 CET, ianseeks ha scritto:
Will the install process give us the option to run the exporter?
No. And actually there shouldn't be any need for update: I checked with the PIM developers and the upgrade path should be automatic. However you must make sure Akonadi isn't running when the update is done. Check my blog post, which I updated, for more details.
thanks Shouldn't the install process also automatically stop akonadi for you? You might install by mistake. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 17. Januar 2016, 18:31:03 schrieb ianseeks:
Shouldn't the install process also automatically stop akonadi for you?
No, that's impossible. The update/install process is running as root, it cannot stop the users' akonadi(s) that might be running. Well, it could kill them of course, but that would cause the same possible problems that not stopping Akonadi before the update manually would be able to cause I think. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 18 Jan 2016 12:46:34 Wolfgang Bauer wrote:
Am Sonntag, 17. Januar 2016, 18:31:03 schrieb ianseeks:
Shouldn't the install process also automatically stop akonadi for you?
No, that's impossible.
The update/install process is running as root, it cannot stop the users' akonadi(s) that might be running.
Well, it could kill them of course, but that would cause the same possible problems that not stopping Akonadi before the update manually would be able to cause I think.
Could it not pop up a warning that says, "please stop akonadi (with the example command)...... and press Y when done?" I think doing this type of user friendly action makes the process more professional and will hopefully stop a few bug reports
Kind Regards, Wolfgang
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Montag, 18. Januar 2016, 13:05:07 schrieb ianseeks:
On Monday 18 Jan 2016 12:46:34 Wolfgang Bauer wrote:
Am Sonntag, 17. Januar 2016, 18:31:03 schrieb ianseeks:
Shouldn't the install process also automatically stop akonadi for you?
No, that's impossible.
The update/install process is running as root, it cannot stop the users' akonadi(s) that might be running.
Well, it could kill them of course, but that would cause the same possible problems that not stopping Akonadi before the update manually would be able to cause I think.
Could it not pop up a warning that says, "please stop akonadi (with the example command)...... and press Y when done?" I think doing this type of user friendly action makes the process more professional and will hopefully stop a few bug reports
No. You have the same problem again. The installation process running as root cannot connect to the users' X or DBUS session. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Montag, 18. Januar 2016, 15:38:26 schrieb Wolfgang Bauer:
Am Montag, 18. Januar 2016, 13:05:07 schrieb ianseeks:
On Monday 18 Jan 2016 12:46:34 Wolfgang Bauer wrote:
Am Sonntag, 17. Januar 2016, 18:31:03 schrieb ianseeks:
Shouldn't the install process also automatically stop akonadi for you?
No, that's impossible.
The update/install process is running as root, it cannot stop the users' akonadi(s) that might be running.
Well, it could kill them of course, but that would cause the same possible problems that not stopping Akonadi before the update manually would be able to cause I think.
Could it not pop up a warning that says, "please stop akonadi (with the example command)...... and press Y when done?" I think doing this type of user friendly action makes the process more professional and will hopefully stop a few bug reports
No. You have the same problem again. The installation process running as root cannot connect to the users' X or DBUS session.
PS: Sending a message via "wall" would be possible I think. AFAIK, KDE's "Wall service" is still enabled by default in Plasma5, which would show it as popup to the user. But, you cannot wait for a user response this way (leading to the original problem of akonadi not being stopped when the update is being installed), and you would probably also "annoy" users that are not running KDE or Akonadi at all. So not a "solution" either. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 18 Jan 2016 15:38:26 Wolfgang Bauer wrote:
Am Montag, 18. Januar 2016, 13:05:07 schrieb ianseeks:
On Monday 18 Jan 2016 12:46:34 Wolfgang Bauer wrote:
Am Sonntag, 17. Januar 2016, 18:31:03 schrieb ianseeks:
Shouldn't the install process also automatically stop akonadi for you?
No, that's impossible.
The update/install process is running as root, it cannot stop the users' akonadi(s) that might be running.
Well, it could kill them of course, but that would cause the same possible problems that not stopping Akonadi before the update manually would be able to cause I think.
Could it not pop up a warning that says, "please stop akonadi (with the example command)...... and press Y when done?" I think doing this type of user friendly action makes the process more professional and will hopefully stop a few bug reports
No. You have the same problem again. The installation process running as root cannot connect to the users' X or DBUS session.
its a shame that there is no way round it, it makes parts of installation process difficult to fully automate
Kind Regards, Wolfgang
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Dne Po 18. ledna 2016 12:46:34, Wolfgang Bauer napsal(a):
Am Sonntag, 17. Januar 2016, 18:31:03 schrieb ianseeks:
Shouldn't the install process also automatically stop akonadi for you?
No, that's impossible.
The update/install process is running as root, it cannot stop the users' akonadi(s) that might be running.
Why not? Why couldn't it detect user process running, peacefully terminate it, perform the update and launch user process again? Sorry, I really do not see why this is impossible... -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On Monday, 18 January 2016 14:13:43 CET Vojtěch Zeisek wrote:
The update/install process is running as root, it cannot stop the users' akonadi(s) that might be running.
Why not? Why couldn't it detect user process running, peacefully terminate it, perform the update and launch user process again? Sorry, I really do not see why this is impossible...
If you would have copied also the other part of Wolfgang's message, then you would know why. As indicated the update process runs under the root user, while the akonadi process is running under an users account. The only way for root to terminate the process, is to kill it. I wouldn't really call this peacefully :) But if you have another way that we can do this, then please let us know and we will incorporate it into the package. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Dne Po 18. ledna 2016 14:33:34, Raymond Wooninck napsal(a):
On Monday, 18 January 2016 14:13:43 CET Vojtěch Zeisek wrote:
The update/install process is running as root, it cannot stop the users' akonadi(s) that might be running.
Why not? Why couldn't it detect user process running, peacefully terminate it, perform the update and launch user process again? Sorry, I really do not see why this is impossible...
If you would have copied also the other part of Wolfgang's message, then you would know why. As indicated the update process runs under the root user, while the akonadi process is running under an users account. The only way for root to terminate the process, is to kill it. I wouldn't really call this peacefully :)
Yes, killing is not peaceful. :-) I thought root can send something like su CURRENTUSER -c 'akonadictl stop' and similarly start it again after upgrade.
But if you have another way that we can do this, then please let us know and we will incorporate it into the package.
Sorry, I may be missing something, but it seems doable with su... Sincerely, -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On Monday, 18 January 2016 14:40:16 CET Vojtěch Zeisek wrote:
Yes, killing is not peaceful. :-) I thought root can send something like su CURRENTUSER -c 'akonadictl stop' and similarly start it again after upgrade.
Well, the question is also if the program akonadictl is still present when the command is issues. The package akonadi-server is the new KF5 based Akonadi and the KDE4 one is in akonadi-runtime. Given the obsoletes and/or Conflicts in akonadi-server, it will force yast/zypper to first uninstall the akonadi- runtime package (removing all binaries) and then to install the new akonadi- server package. If we now want to insert a command to stop the akonadi- server, we are faced with the fact that the akonadi-runtime package has already been removed, so akonadictl is most likely no longer available on the system. This means that killing the process would be the only way to stop the akonadiserver itself. This one will of course continue to run as that the binaries/libraries are already loaded in memory. As you can see it is not that easy to find the right way and that it is not just a simple su command that could help out. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Dne Po 18. ledna 2016 14:49:23, Raymond Wooninck napsal(a):
On Monday, 18 January 2016 14:40:16 CET Vojtěch Zeisek wrote:
Yes, killing is not peaceful. :-) I thought root can send something like su CURRENTUSER -c 'akonadictl stop' and similarly start it again after upgrade.
Well, the question is also if the program akonadictl is still present when the command is issues. The package akonadi-server is the new KF5 based Akonadi and the KDE4 one is in akonadi-runtime. Given the obsoletes and/or Conflicts in akonadi-server, it will force yast/zypper to first uninstall the akonadi- runtime package (removing all binaries) and then to install the new akonadi- server package. If we now want to insert a command to stop the akonadi- server, we are faced with the fact that the akonadi-runtime package has already been removed, so akonadictl is most likely no longer available on the system. This means that killing the process would be the only way to stop the akonadiserver itself. This one will of course continue to run as that the binaries/libraries are already loaded in memory.
As you can see it is not that easy to find the right way and that it is not just a simple su command that could help out.
Ah, OK, thank You for explanation. So the only place for this insertion would be before removal of KDE4 version. Sincerely, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
Am Montag, 18. Januar 2016, 15:05:01 schrieb Vojtěch Zeisek:
Ah, OK, thank You for explanation. So the only place for this insertion would be before removal of KDE4 version.
You'd probably have to change the existing KDE4 packages to do that though. And even then, the order of installation/removal is not guaranteed (by rpm), so if you run something in the KDE4 packages' uninstallation scripts, the old files probably won't be there any more either. Also consider that Linux is a *multi* user system, you'd have to do that for every logged in user. Another problem: if you run a command by root as user (via su), it won't find the logged in users' DBUS session (this is exported via environment variables in the running user's environment), which would be required to properly stop the users' akonadi servers... But, as Raymond wrote already, if you can come up with a solution, feel free to submit it. I cannot think of any general one that would work in all circumstances... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Op zondag 17 januari 2016 11:38:01 schreef Raymond Wooninck:
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.
There is nothing automatic for the replacement. Installing kmail5 removes a lot and installs a lot, but not kontact5. Installing kontact5 does not install kmail5 and other pim5 modules. Although kaddressbook5 is installed kontact5 does not show the addressbook as a plugin. Same for knotes5. All my accounts have been automatically migrated, however Appearance needed to be reconfigured from the defaults. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Dear Freek,
Based on your indications you just installed kmail5. The update to KDE
Apps 15.12.1 (with the automatic replacement) has not been published
yet. At least I didn't see any announcement in openSUSE-factory. I
might be wrong here as that I am not running Tumbleweed. But if you
had kontact4 installed, then it should be replaced by kontact5.
Raymond
On Sat, Jan 23, 2016 at 10:56 PM, Freek de Kruijf
Op zondag 17 januari 2016 11:38:01 schreef Raymond Wooninck:
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.
There is nothing automatic for the replacement. Installing kmail5 removes a lot and installs a lot, but not kontact5. Installing kontact5 does not install kmail5 and other pim5 modules. Although kaddressbook5 is installed kontact5 does not show the addressbook as a plugin. Same for knotes5. All my accounts have been automatically migrated, however Appearance needed to be reconfigured from the defaults.
-- fr.gr.
member openSUSE Freek de Kruijf
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (7)
-
Achim Gratz -
Freek de Kruijf -
ianseeks -
Luca Beltrame -
Raymond Wooninck -
Vojtěch Zeisek -
Wolfgang Bauer