Re: KDE PIM packaging
Am Dienstag, 19. Juni 2012 schrieb Torsten Grote: > > As martin correctly said, Kdepim 2 lacks migration and that is one > > reason it will not be included in wheezy. > > I'm sitting with several PIM hackers in the same office and they said > that using 4.4.11 programs with recent akonadi is quite > "adventurous". Also, I'm not sure whether the migration will improve > in the near future. Hmmm, why? I think its an important feature for the regular user. > As for me, I'm ready to set up my KDE PIM accounts freshly to take > advantage of a more recent and stable platform. This might be difficult for not so advanced users or people who have a "big" setup like me. I have to recreate about 100 filter rules and re-integrate CRM114 spam filtering. I understand that a 100% complete migration might be difficult to implement cause there is a wide variety of setups, but at least some help for the basic stuff like filter rules would be really nice. Well anyway, thats probably better a discussion on kdepim mailinglist. -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201206200934.03031.mar...@lichtvoll.de
Re: KDE PIM packaging
Am Montag, 18. Juni 2012 schrieb Eshat Cakar: > Hi Torsten, > hi Martin, > > On Mon 18 June 2012 11:29:22 Martin Steigerwald wrote: > > Am Samstag, 16. Juni 2012 schrieb Torsten Grote: > > > I'd love to have some information, why the KDE PIM applications are > > > at version 4.4.11. > > > > The switch to Akonadi for KMail is a big one. And I think even right > > now there is no way of automatic migration thats working out okay in > > most cases. > Thus the recommended procedure as far as I am aware of > > is to recreate mail accounts and reimport mail from IMAP server or > > POP3 mail directory. As far as I read its usually also necessary to > > recreate all filter rules. > > > > I´d love to test KDEPIM 2, > > As martin correctly said, Kdepim 2 lacks migration and that is one > reason it will not be included in wheezy. > But we will provide packages for the curious testers like you, just > after the team finishes the rest of the 4.8.4 transition, which has > higher priority due to the wheezy freeze. Thanks, that great to hear. I think that helps us to get a handle on the current situation with KDEPIM 2. I always wanted to compile it myself, but didn´t come to it. When its just an apt-get install away thats easier to handle for me. Would it be sufficient for Debian when there is a step by step migration guide that describes how to copy everything over manuelly by recreating it? I am willing to help to document such migration steps once I migrate to KDEPIM 2 myself. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201206200945.40611.mar...@lichtvoll.de
Re: KDE PIM packaging
Am Dienstag, 19. Juni 2012 schrieb Modestas Vainius: > Hello, > > On antradienis 19 Birželis 2012 19:43:12 Valerio Passini wrote: > > martedì 19 giugno 2012 > > > > I could understand this point of view if: > > 1 - a tool to ease the migration it's going to be on the way any time > > soon (in the next 2-3 years) before the release of what will be the > > next stable after Wheezy, but if such tool is not in anybody's mind > > I can only complain this decision. > > 2 - this hypothetical migration tool will still hold a meaning, > > considering the major changes that will come in the next future like > > the entire KDE moving from 4.x to 5.x, with likely a lot of new > > stuff. This will doom Debian to be always lagging in respect to KDE > > releases, to miss new technology and to support mixed KDE > > environment with piece of "old" KDE inside. This should scare the > > developers more than users having troubles migrating emails, IMO. > > There is nothing wrong with having "old KDE inside" if it works. That > said, I don't claim that pim 2 does not work. We simply don't know it > and it's too late in the game to find out (IMHO). Inexistance of a > good migration tool helps to make the decision though. > > FWIW, I'm pretty sure that migration won't ever be fixed. However, > users will have more time to adjust at the start of the next release > cycle. What is more, I think somebody will be kind enough and upload > kdepim 4.8.4 to backports and wheezy users will have the best of two > worlds (a choice) in the end. I agree. Better let us likely a bit more experienced Debian KDE users here on the list test KDEPIM 2 for a while before letting it loose on all Debian KDE users. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201206200948.51042.mar...@lichtvoll.de
Re: KDE PIM packaging
Am Dienstag, 19. Juni 2012 schrieb Dietz Pröpper: > Martin Steigerwald: > > The switch to Akonadi for KMail is a big one. > > And a quite questionable, too. Everything is questionable. But I believe that the fundamental decision to use a database for metadata is sound. > > And I think even right now > > there is no way of automatic migration thats working out okay in most > > cases. > > Wow. What do they smoke over at KDE Central? Not a very helpful comment in my oppinion. And nothing for me to follow up on. > > Thus the recommended procedure as far as I am aware of is to > > recreate mail accounts and reimport mail from IMAP server or POP3 > > mail directory. As far as I read its usually also necessary to > > recreate all filter rules. > > Fine. I have a ~/Mail around 1G in size and a forest of filter rules. > This "recommended procedure" is simply not feasible for me. > > Add to this the quite braindama^W questionable idea to move not only > metadata stuff but the complete maildir to akonadi, and *I* will be out > of the game, for sure. Even if repeated even more times it will not become true. Akonadi is a metadata cache. Not the mail store. So once again also here on this list: Please read Akonadi misconception #1: where is my data? http://blogs.kde.org/node/4503 Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201206200952.49094.mar...@lichtvoll.de
Re: KDE PIM packaging
On Tuesday, 2012-06-19, Modestas Vainius wrote: > There is nothing wrong with having "old KDE inside" if it works. That said, > I don't claim that pim 2 does not work. We simply don't know it and it's > too late in the game to find out (IMHO). Inexistance of a good migration > tool helps to make the decision though. > > FWIW, I'm pretty sure that migration won't ever be fixed. However, users > will have more time to adjust at the start of the next release cycle. What > is more, I think somebody will be kind enough and upload kdepim 4.8.4 to > backports and wheezy users will have the best of two worlds (a choice) in > the end. The main problem with the migration tool is that the complexity of the mail setup just does not fit into the constraints of the migrator framework used for other data types. I.e. for other data types it is sufficient to create one new backend connectors for each old backend connector and transfer the respective config. Mail setup has folder specific config, folder and mail item specific meta data, etc. which requires the migrator to do a lot of mail structure and data processing. This also takes way longer than what is acceptable for a migrator that runs automatically on first application start. The correct solution is to make KMail2 start immediately but empty and detect and offer import choices. Cheers, Kevin signature.asc Description: This is a digitally signed message part.
Re: kalarm broken by mysql upgrade?
On Wed, June 20, 2012 12:54 am, Xavier Brochard wrote: > Andreas v. Heydwolff wrote: > >>> You are missing Kalarm akonadi resources. >> >> Indeed they are not installed. I am not sure which package they belong to. > > Kalarm > see http://packages.debian.org/sid/i386/kalarm/filelist Actually, the KAlarm Akonadi resources are in the kdepim-runtime package. -- David Jarvie. KDE developer. KAlarm author - http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/01abf2717f09aa6fad30578edc87d2e1.squir...@www.sensical.net
Re: kalarm broken by mysql upgrade?
On 2012-06-20 17:47, David Jarvie wrote: > On Wed, June 20, 2012 12:54 am, Xavier Brochard wrote: >> Andreas v. Heydwolff wrote: >> You are missing Kalarm akonadi resources. >>> >>> Indeed they are not installed. I am not sure which package they belong to. >> >> Kalarm >> see http://packages.debian.org/sid/i386/kalarm/filelist > > Actually, the KAlarm Akonadi resources are in the kdepim-runtime package. But which one in the list would show up as the kalarm resource in Akonadi (please follow link)? http://packages.debian.org/sid/amd64/kdepim-runtime/filelist Andreas -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fe202c0.8020...@sandpsych.at
Re: [debian-kde] Re: kalarm broken by mysql upgrade?
On Wednesday 20 June 2012 18:05:04 Andreas v. Heydwolff wrote: > On 2012-06-20 17:47, David Jarvie wrote: > > On Wed, June 20, 2012 12:54 am, Xavier Brochard wrote: > >> Andreas v. Heydwolff wrote: > >> > You are missing Kalarm akonadi resources. > >>> > >>> Indeed they are not installed. I am not sure which package they belong to. > >> > >> Kalarm > >> see http://packages.debian.org/sid/i386/kalarm/filelist > > > > Actually, the KAlarm Akonadi resources are in the kdepim-runtime package. > > > But which one in the list would show up as the kalarm resource in > Akonadi (please follow link)? > > http://packages.debian.org/sid/amd64/kdepim-runtime/filelist That package is for use with kdepim 4.4. I'm confused as to which package versions you are using, since KAlarm 4.4 is not able to use Akonadi - Akonadi resources for KAlarm were only implemented in kdepim 4.8. Earlier versions of KAlarm do not use Akonadi at all. -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201206210010.31885.djar...@kde.org
