Re: [debian-kde] Re: kalarm broken by mysql upgrade?
On 2012-06-22 10:14, David Jarvie wrote: > Good, I'm glad you got it sorted out. There is always a potential problem, > in KAlarm as in other applications, if you try to use configuration or > data files when stepping back to an older version of the application. > Your experience makes me wonder whether a warning should be > displayed if this happens, together with offering the option of making the > files read-write regardless. This sounds like a very good idea to me. I was also confused because at some point there was only a "displaying.ics" and no "calendar.ics" file in the share/apps/kalarm dir. I seem to remember that I saw no alarms at all in the kalarms window - I didn't have the calendar pane open, then loaded the displaying.ics file because I thought no file was loaded at all, and thereafter the rolled back stable kalarm 4.4 crashed while starting, perhaps due to creating calendar.ics anew and now loading both files. I had also changed the version info in the displaying.ics file back to 2.4 and deleted one line that seemed to be new in the 2.9 header, but by then all was fubar... Regards, A. -- 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/4fe435b9.8060...@sandpsych.at
Re: [debian-kde] Re: kalarm broken by mysql upgrade?
On Thu, June 21, 2012 9:29 pm, Andreas v. Heydwolff wrote: > On 2012-06-21 01:10, David Jarvie wrote: > >> 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. > > > Thanks, David and Xavier, for the help and clarification, and sorry for > the confusion I created. > > It seems that the *.ics files were updated and slightly modified when I > was using a self compiled kalarm 2.9, and the Debian version 4.4.11 to > which I reverted later when the kalarm crashes were resolved could not > handle them. I finally moved all files out of the dir and started from > scratch, extraced all DESCRIPTION fields with a sed/cut script and > manually created new alarms. Problem solved. Good, I'm glad you got it sorted out. There is always a potential problem, in KAlarm as in other applications, if you try to use configuration or data files when stepping back to an older version of the application. In the case of KAlarm, if it finds that a calendar file has been written by a later version (and only if there has been a format change between the two versions) it takes the precaution of making the file read-only to ensure that data is not lost for the newer version of KAlarm which created the files. Your experience makes me wonder whether a warning should be displayed if this happens, together with offering the option of making the files read-write regardless. -- 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/fcde65224b228fde3b64fdcab2dc729b.squir...@www.sensical.net
Re: [debian-kde] Re: kalarm broken by mysql upgrade?
On 2012-06-21 01:10, David Jarvie wrote: > 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. Thanks, David and Xavier, for the help and clarification, and sorry for the confusion I created. It seems that the *.ics files were updated and slightly modified when I was using a self compiled kalarm 2.9, and the Debian version 4.4.11 to which I reverted later when the kalarm crashes were resolved could not handle them. I finally moved all files out of the dir and started from scratch, extraced all DESCRIPTION fields with a sed/cut script and manually created new alarms. Problem solved. Cheers, 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/4fe38433.4090...@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
