Given the fact that 3 years passed prior to this change, that the KDE community had to create a fork of libkolab, and that openSUSE dropped the package due to lack of upstream maintenance, there is no point in keeping this task open.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 2 2020
Jul 6 2019
Jul 5 2019
Dec 16 2018
Because jsTimezoneDetect is not very active project I decided to add a workaround on PHP side. Fixed in https://github.com/roundcube/roundcubemail/commit/36485dfc345ad724f08eaa7ea30c3cc88e48a00d.
Aug 21 2018
Copenhagen is, in principle, available. The reason for the parent ticket to exist has largely been obsoleted. This sub-ticket, and its sub-tickets, can therefore be closed.
Oct 19 2017
I have filed now a bug at the jstz library, because I guess that would be the cleanest solution.
If that ignores Etc timezones coming from the internationalization API from the browser, then it calculates a proper Olson timezone.
It does not depend on Windows Server version.
It does not depend on Firefox version either.
I got more details: the client is Firefox 56 running on Windows Server 2012 R2. The timezone setting for the user in Roundcube is "auto".
Oct 18 2017
Sep 9 2016
Done.
Sep 6 2016
Jul 27 2016
Jun 28 2016
Jun 7 2016
Jun 6 2016
The attach property is indeed optional, but libkolabxml doesn't treat it as optional property.
Apr 29 2016
Apr 28 2016
Apr 25 2016
Apr 22 2016
This will need to be packaged and tested in a setup where this actually happens.
A patch has been added to libkolab 0.6.3 and libkolab 0.7 (which has never been released apparently).
I was not able to catch this debug information in PHP, I'm not sure it's possible/simple in python. So, my preferred solution would be to fix libkolab/libcalendaring. In my opinion it would be reasonable to get rid of it on packaging level.
Apr 14 2016
Apr 8 2016
D127 together with D123 are fixing unit tests. Now the output is:
[root@kolab pykolab]# nosetests ./tests/unit ...............................Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/objectvalidation.cpp 94: event.start() is not set Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/xcalconversions.h 1500: Start date is missing, but is mandatory for events Debug: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/kolabformat.cpp 94: Error occurred while writing. .......................unnamed app(16962) KCalCore::ICalFormatImpl::populate: No PRODID property found unnamed app(16962) KSystemTimeZonesPrivate::readConfig: readConfig(): local zone= "UTC" unnamed app(16962) KSystemTimeZonesPrivate::readZoneTab: readZoneTab( "/usr/share/zoneinfo/zone.tab" ) .....unnamed app(16962) KCalCore::ICalFormatImpl::populate: No PRODID property found .....(20:39:09) timezoneconverter.cpp(51): Guessed timezone and found: "" (20:39:09) commonconversion.cpp(44): invalid timezone: "None" , assuming floating time .unnamed app(16962) KCalCore::ICalFormatImpl::populate: No PRODID property found .Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/utils.h 114: bad numeric conversion: negative overflow Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/utils.h 114: bad numeric conversion: negative overflow schema exception :25:25 error: value '' does not match regular expression facet '(\-|\+)?\d{4}\-\d{2}\-\d{2}T\d{2}:\d{2}:\d{2}(\.\d*)?Z?' Critical: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/xcalconversions.h 1940: Failed to parse calendar! Debug: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/kolabformat.cpp 94: Error occurred while writing. ........................................................................S. ---------------------------------------------------------------------- Ran 140 tests in 2.898s
Dec 30 2015
Aug 25 2015
Aug 19 2015
Aug 11 2015
Aug 7 2015
Hmm... I'm not so sure. According to RFC5545 it is not valid.
Aug 3 2015
Oops. It looks that "P" is valid. I'll look for the issue in other places.
Jun 24 2015
Jun 22 2015
May 22 2015
May 12 2015
May 10 2015
A DateTime class needs to be introduced to replace the date-only functionality provided by KDateTime that is no longer available in QDateTime
May 6 2015
Apr 29 2015
Apr 28 2015
The following usecases are currently covered by libkolab:
- Interpretation and expansion of recurrences
- Detection of conflicts in event-sets
- Retrieval of current system-time
- Attendee/Delegation-helpers for events
- iTip/iMip reading/writing
- iCalendar reading/writing
- Conversion between kolab and KDE Containers
- Generating/aggregating and serializing freebusy
- Definitions such as types, used in the kolab MIME-message format and IMAP annotations.
- Reading/writing of kolab objects to/from V3 MIME-messages
- Reading/writing of kolab objects to/from V3 XML
- Reading/writing of kolab objects to/from V2 MIME-messages
- Reading/writing of kolab objects to/from V2 XML
Everything's medium until product owners say different.
Everything's medium until product owners say different.
Everything's medium until product owners say different.
Everything's medium until product owners say different.
Everything's medium until product owners say different.
Everything's medium until product owners say different.
Everything's medium until product owners say different.
Everything's medium until product owners say different.
Everything's medium until product owners say different.
Apr 27 2015
Apr 26 2015
Apr 24 2015
Apr 21 2015
Dropping QT from libkolab would be a complete rewrite of it, and also mean we no longer use any KDE libraries.