Re: [pkg-kolab] kdepim and kolab
¡Hola Torsten! El 2014-05-26 a las 14:43 +0200, Torsten Grote escribió: On Sunday 18 May 2014 02:13:48 Maximiliano Curia wrote: I'm currently packaging the new upstream release of kdepim and friends Thanks a lot for this! Your mail has just been moderated through to pkg-kolab-devel. Has there been any news since you sent it? Yes, Paul Boddie started working on libkolab, based on the debian package and the ubuntu repository, and now it's rebasing that on top of the libkolab git repository. I think he might need a hand, also libkolab build-depends on libkolabxml, so I think it would be a good thing if libkolabxml gets uploaded. I'm uploading kdepim and friends to experimental to have some testers on the nepomuk migration to baloo, built without kolab support in the meantime. Thanks, -- If a pickpocket meets a saint, he sees only his pockets. -- Kegley's Law Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Re: [pkg-kolab] kdepim and kolab
On Sunday 18 May 2014 02:13:48 Maximiliano Curia wrote: I'm currently packaging the new upstream release of kdepim and friends Thanks a lot for this! Your mail has just been moderated through to pkg-kolab-devel. Has there been any news since you sent it? Kind Regards, Torsten -- Torsten Grote, Kolab Evangelist Kolab Systems AG, Zürich, Switzerland e: gr...@kolabsys.com t: +41 43 501 66 91 w: http://kolabsys.com pgp: 0x2175A534A4F2EFA3 signature.asc Description: This is a digitally signed message part.
kdepim and kolab
Hello, I'm currently packaging the new upstream release of kdepim and friends, and in this release the support of kolab requires libkolab-dev 0.5 and libkolabxml-dev 1.0. While the ones currently available are 0.4.2 and 0.8.4 (is libkolabxml always double the libkolab version?) correspondingly. I would prefer to keep the kolab support in kdepim, would it be possible to update these libraries in Debian? Will they require a soversion bump? Updating these libraries require you to adapt some other packages as well? I don't use kolab, so even if I could nmu the n-u-r I would be able to test it. Happy hacking. -- If you think your users are idiots, only idiots will use it. -- Linus Torvalds Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Bug#732213: [kdepim-runtime] Kolab agent looses information about birthdays
Package: kdepim-runtime Version: 4:4.11.3-1 Severity: grave Why grave: user generated data is lost when using the kolab agent (and I've lost a lot of data because of this bug) Hi, I've just installed a new machine and added my IMAP server and kolab agent to akonadi. It downloaded all resources but when I've started to edit some users I've noticed that the birthday was missing. Also entering it again resulted in missing birthdays (like it was never entered) on all other machines also using the same IMAP server with kolab. Checking the imap server also seemed to verify that no dates are stored inside the KolabV3 contact xml. I've also tried to change it from KolabV3 to KolabV2 format in the Kolab-Agent settings but then other data fields cannot be parsed anymore when downloading the newly stored kolab mails/xmls (for example the pictures). Ways to reproduce: create an imap account to akonadi (using KDE systemsettings or so), add a kolab agent with the default settings (v3) using this imap server, press create folders, create a new contact in the activated contact folder in kaddressbook, add a birthday date and save it. Now open the mail on the imap server and check for the birthday information. I think this is the easiest way to check it without another machine/account to download and parse the contact information again. Interestingly the anniversary date is stored but not the birthday I don't know which component has this bug and therefore just add it to the package which seems to provide the kolab agent. --- System information. --- Architecture: amd64 Kernel: Linux 3.11-2-amd64 Debian Release: jessie/sid 500 unstablehttp.debian.net --- Package information. --- Depends (Version) | Installed =-+-= kde-runtime ( 4:4.10) | 4:4.11.3-1 kdepimlibs-kio-plugins| 4:4.11.3-2 libakonadi-calendar4(= 4:4.11.1) | 4:4.11.3-2 libakonadi-contact4 (= 4:4.11.3) | 4:4.11.3-2 libakonadi-kabc4(= 4:4.11.3) | 4:4.11.3-2 libakonadi-kcal4(= 4:4.11.3) | 4:4.11.3-2 libakonadi-kde4 (= 4:4.11.3) | 4:4.11.3-2 libakonadi-kmime4 (= 4:4.11.3) | 4:4.11.3-2 libakonadi-notes4(= 4:4.8.1) | 4:4.11.3-2 libakonadiprotocolinternals1 (= 1.5.1) | 1.10.3-1 libc6 (= 2.14) | libgcc1 (= 1:4.1.1) | libkabc4(= 4:4.11.3) | libkalarmcal2(= 4:4.8.1) | libkcal4(= 4:4.11.3) | libkcalcore4(= 4:4.11.1) | libkcalutils4 (= 4:4.5.86) | libkcmutils4 (= 4:4.11) | libkdecore5 (= 4:4.11) | libkdeui5 (= 4:4.11) | libkgapi2-2 | libkidletime4 (= 4:4.11) | libkimap4 (= 4:4.11.3) | libkio5 (= 4:4.11) | libkmbox4 (= 4:4.5.86) | libkmime4 (= 4:4.11.3) | libknewstuff3-4 (= 4:4.11) | libknotifyconfig4 (= 4:4.11) | libkolab0 (= 0.4.2-7~) | libkpimidentities4 (= 4:4.11.3) | libkpimtextedit4(= 4:4.11.3) | libkpimutils4 (= 4:4.11.3) | libkresources4 (= 4:4.11.3) | libkrosscore4 (= 4:4.11) | libmailtransport4 (= 4:4.11.3) | libmicroblog4 (= 4:4.11.3) | libnepomukcore4 (= 4:4.10.0) | libqjson0 (= 0.7.1) | libqt4-dbus (= 4:4.5.3) | libqt4-declarative (= 4:4.7.0~rc1) | libqt4-network (= 4:4.5.3) | libqt4-script(= 4:4.5.3) | libqt4-xml (= 4:4.5.3) | libqt4-xmlpatterns (= 4:4.5.3) | libqtcore4 (= 4:4.8.0) | libqtgui4(= 4:4.8.0) | libsolid4 (= 4:4.11) | libsoprano4 (= 2.9) | libstdc++6 (= 4.1.1) | libxml2(= 2.7.4) | akonadi-server (= 1.8) | Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1387130178.71596.yahoomail...@web171902.mail.ir2.yahoo.com
Bug#732231: [kdepim-runtime] Kolab agent doesnt download information about recurring task due
Package: kdepim-runtime Version: 4:4.11.3-1 Severity: normal Forwarded: https://bugs.kde.org/show_bug.cgi?id=328846 [Resending because Debian bug tracker seems to have dropped the mail] Hi, I've just installed a new machine and added my IMAP server and kolab agent to akonadi. It downloaded all resources but when I've started to edit some tasks I've noticed that the due data was missing. Also entering it again resulted in missing due dates (like it was never entered) on all other machines also using the same IMAP server with kolab. Interestingly the date was correctly stored on the server The important part here seems to be that the task was recurring. Ways to reproduce: create an imap account in akonadi (using KDE systemsettings or so), add a kolab agent with the default settings (v3) using this imap server, press create folders, create a new task in the activated task folder in korganizer, add a start date, due date, mark it as all-day and recurrance (monthly on the 1th) save it. Now open the mail on the imap server and check for the due information. It should everything be there. akonadiconsole on this machine shows following information in the raw payload view of the kolab task folder item: BEGIN:VCALENDAR PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN VERSION:2.0 X-KDE-ICAL-IMPLEMENTATION-VERSION:1.0 BEGIN:VTODO DTSTAMP:20131215T191632Z CREATED:20131215T191632Z UID:89e18570-25e1-4708-a8b5-2321bac3243a LAST-MODIFIED:20131215T191632Z SUMMARY:asd RRULE:FREQ=MONTHLY;BYMONTHDAY=1 DUE;VALUE=DATE:20131215 DTSTART;VALUE=DATE:20131201 PERCENT-COMPLETE:0 X-KDE-LIBKCAL-DTRECURRENCE;VALUE=DATE-TIME:20131201T201600 END:VTODO END:VCALENDAR Up to here everything seems to be fine. But now add the same imap server/kolab on another account/machine and download the task items there. The due information completely disappeared and it looks in the overview like there is no due: at all (not marked red). The akonadiconsole show following output in the raw payload information: BEGIN:VCALENDAR PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN VERSION:2.0 X-KDE-ICAL-IMPLEMENTATION-VERSION:1.0 BEGIN:VTODO DTSTAMP:20131215T191632Z CREATED:20131215T191632Z UID:89e18570-25e1-4708-a8b5-2321bac3243a LAST-MODIFIED:20131215T191632Z SUMMARY:asd RRULE:FREQ=MONTHLY;BYMONTHDAY=1 DTSTART:20131117T00 PERCENT-COMPLETE:0 END:VTODO END:VCALENDAR So the DUE is missing, the DTSTART is now with time (and wrong) instead of all-day and this X-KDE-LIBKCAL-DTRECURRENCE is now missing (I don't know what this is). Interestingly the DTSTART date is also stored on the server and is not what I've entered. I will create an extra bug for that later I've used the 1th of December as start date and the 15th of december as due date. I was happy that the item was marked red (because today it is the 15th) on the main machine and when I clicked on the item and marked it as complete then the Due Date/Time jumped from 01.12.2013 to 01.01.2014. This functionality is completely missing on the non-main machine which only downloaded the information over kolab. I don't know which component has this bug and therefore just add it to the package which seems to provide the kolab agent. --- System information. --- Architecture: amd64 Kernel: Linux 3.11-2-amd64 Debian Release: jessie/sid 500 unstable http.debian.net --- Package information. --- Depends (Version) | Installed =-+-= kde-runtime ( 4:4.10) | 4:4.11.3-1 kdepimlibs-kio-plugins | 4:4.11.3-2 libakonadi-calendar4 (= 4:4.11.1) | 4:4.11.3-2 libakonadi-contact4 (= 4:4.11.3) | 4:4.11.3-2 libakonadi-kabc4 (= 4:4.11.3) | 4:4.11.3-2 libakonadi-kcal4 (= 4:4.11.3) | 4:4.11.3-2 libakonadi-kde4 (= 4:4.11.3) | 4:4.11.3-2 libakonadi-kmime4 (= 4:4.11.3) | 4:4.11.3-2 libakonadi-notes4 (= 4:4.8.1) | 4:4.11.3-2 libakonadiprotocolinternals1 (= 1.5.1) | 1.10.3-1 libc6 (= 2.14) | libgcc1 (= 1:4.1.1) | libkabc4 (= 4:4.11.3) | libkalarmcal2 (= 4:4.8.1) | libkcal4 (= 4:4.11.3) | libkcalcore4 (= 4:4.11.1) | libkcalutils4 (= 4:4.5.86) | libkcmutils4 (= 4:4.11) | libkdecore5 (= 4:4.11) | libkdeui5 (= 4:4.11) | libkgapi2-2 | libkidletime4 (= 4:4.11) | libkimap4 (= 4:4.11.3) | libkio5 (= 4:4.11) | libkmbox4 (= 4:4.5.86) | libkmime4 (= 4:4.11.3) | libknewstuff3-4 (=
