May 2011 - calendarserver-dev - lists.macosforge.org

[Calendar and Contacts Server] #412: [PATCH] add german localization
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#412: [PATCH] add german localization ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- Hi, I just created a german localization. As I think .po is the most widely used format I have chosen to use that. see #410. regards -- Ticket URL: <http://trac.calendarserver.org/ticket/412> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #409: Exception: Characterset does not work for french Translation
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#409: Exception: Characterset does not work for french Translation ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- I set Language to "fr" to test the localization. {{{ 2011-02-06 19:46:36+0100 [-] [mailgateway] 2011-02-06 19:46:36+0100 [-] [twext.web2.server#error] [Failure instance: Traceback: <type 'exceptions.UnicodeEncodeError'>: 'ascii' codec can't encode character u'\xe0' in position 5: ordinal not in range(128) 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/internet/defer.py:345:errback 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/internet/defer.py:424:_startRunCallbacks 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/internet/defer.py:441:_runCallbacks 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/internet/defer.py:949:gotResult 2011-02-06 19:46:36+0100 [-] [mailgateway] --- <exception caught here> --- 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/internet/defer.py:891:_inlineCallbacks 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/python/failure.py:338:throwExceptionIntoGenerator 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twistedcaldav/resource.py:309:renderHTTP 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/internet/defer.py:891:_inlineCallbacks 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/python/failure.py:338:throwExceptionIntoGenerator 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twext/web2/static.py:127:renderHTTP 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/internet/defer.py:891:_inlineCallbacks 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/python/failure.py:338:throwExceptionIntoGenerator 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twext/web2/resource.py:109:renderHTTP 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twisted/internet/defer.py:893:_inlineCallbacks 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twistedcaldav/mail.py:334:http_POST 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twistedcaldav/mail.py:940:outbound 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/site- packages/twistedcaldav/mail.py:1029:generateEmail 2011-02-06 19:46:36+0100 [-] [mailgateway] /usr/lib/python2.6/encodings/utf_8.py:16:decode 2011-02-06 19:46:36+0100 [-] [mailgateway] ] }}} This can be reproduced by {{{ >>> u"à".decode("utf-8") Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode return codecs.utf_8_decode(input, errors, True) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe0' in position 0: ordinal not in range(128) }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/409> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 6

[Calendar and Contacts Server] #407: better error handling in case mail address is not working
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#407: better error handling in case mail address is not working ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- Hi, I played have a day just to find out that the calendar server did not handle my smtp server. The relevant source is in @source:CalendarServer/trunk/twistedcaldav/mail.py The ESMTPSenderFactory does not return for me. This leeds the calendar server into a locking issue which is finally shown in iCal as a "409 CONFLICT". The server in question is: smtprelaypool.ispgateway.de on port 465. I can create an account for testing if wanted. -- Ticket URL: <http://trac.calendarserver.org/ticket/407> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #404: support for heimdal
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#404: support for heimdal ------------------------------------+--------------------------------------- Reporter: Martin.vGagern@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: PyKerberos | Severity: Other Keywords: | Radar: ------------------------------------+--------------------------------------- PyKerberos won't compile against Heimdal 1.3.3 on my Gentoo Linux system. 1. Heimdal doesn't provide a `gssapi/gssapi_generic.h` header file 2. The `krb5_context` type is declared in `krb5.h` 3. `krb5_kt_cursor` isn't a pointer, so you can't assign NULL 4. `gss_krb5_nt_service_name` is undefined, `GSS_KRB5_NT_PRINCIPAL_NAME` seems to be the heimdal replacement Some of these, like the missing `gss_krb5_nt_service_name`, have been mentioned in ticket #37 already, but it seems they never made it into the tree. I'll attach a patch addressing the errors, but I assume it will break compatibility with MIT Kerberos. Don't know the best approach to cater for both. Maybe we should check some preprocessor macro. Or we could check the presence of certain header files in setup.py, and supply our own preprocessor macro from this information. Or we could investigate the list of libraries that krb5-config generates, as I believe e.g. `libroken` to be specific to Heimdal. Not sure, though. Some functions used by the code are deprecated according to the Heimdal header file: 1. Use `krb5_xfree` instead of `krb5_free_unparsed_name` 2. Use `krb5_get_init_creds_opt_alloc` instead of `krb5_get_init_creds_opt_init` 3. Use `krb5_set_password` instead of `krb5_change_password` I haven't addressed these in my patch, as they are only warnings, but perhaps you should note them for future reference. And if MIT Kerberos provides the newer functions as well, you should switch as soon as possible. -- Ticket URL: <http://trac.calendarserver.org/ticket/404> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #396: More setup needed for CalDAV/implicitauto6.xml
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#396: More setup needed for CalDAV/implicitauto6.xml ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- This {{{ <request user="$useradmin:" pswd="$pswdadmin:"> <method>DELETEALL</method> <ruri>$calendarpath1:/</ruri> </request> }}} needs adding to the startup for CalDAV/implicitauto6.xml Previous tests can leave stuff lying around in the calendar -- Ticket URL: <http://trac.calendarserver.org/ticket/396> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #391: 'run' script installs Twisted plugins to wrong location on x86_64 systems
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#391: 'run' script installs Twisted plugins to wrong location on x86_64 systems ---------------------------------+------------------------------------------ Reporter: s.adam@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | ---------------------------------+------------------------------------------ I may have made a beginner's mistake as this is the first time I deal with Twisted, but I believe that CalendarServer installs the Twisted plugins to the wrong location on x86_64 systems. CalendarServer will create a both '/usr/lib/python2.X/site-packages' (sitelib) and '/usr/lib64/python2.X/site-packages' (sitearch) directory and places the Twisted files in sitearch directory and the Twisted plugins in the sitelib. Attempting to start the server will have Twisted search only the sitearch directory and produce an error since the caldav plugin isn't known. I am using Fedora 13 x86_64 which has Python 2.6. -- Ticket URL: <http://trac.calendarserver.org/ticket/391> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #389: Allow 400 (Bad Request) for bad requests
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#389: Allow 400 (Bad Request) for bad requests ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Task | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- Validator prepostcondition only allows 403, 409, 507 as a status even though 400 seems valid and sometimes more appropriate (e..g non-UTC datetime in time-range): DAV says {{{ Servers MAY reject questionable requests (even though they consist of well-formed XML), for instance, with a 400 (Bad Request) status code and an optional response body explaining the problem. }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/389> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #387: Content-type could use its own verifier
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#387: Content-type could use its own verifier ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- Tests fail because the content-type header value doesn't match but is actually valid, e.g. g test for {{{ text/calendar;charset=utf-8 }}} and receive {{{ text/calendar; charset=UTF-8 }}} The space(s) after the semi-colon are valid as is the UC "UTF-8" This might be complicated enough to justify its own verifier -- Ticket URL: <http://trac.calendarserver.org/ticket/387> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #386: DTSTAMP should be (partially) filtered in calendarDataMatch
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#386: DTSTAMP should be (partially) filtered in calendarDataMatch ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- DTSTAMP is equivalent to LAST-MODIFIED for entities without a METHOD so should be filtered for those tests. For example, tests in put.xml fail because the DTSTAMP value changes, DTSTAMP from rfc5545: {{{ Purpose: In the case of an iCalendar object that specifies a "METHOD" property, this property specifies the date and time that the instance of the iCalendar object was created. In the case of an iCalendar object that doesn't specify a "METHOD" property, this property specifies the date and time that the information associated with the calendar component was last revised in the calendar store. ... In the case of an iCalendar object that specifies a "METHOD" property, this property differs from the "CREATED" and "LAST- MODIFIED" properties. These two properties are used to specify when the particular calendar data in the calendar store was created and last modified. This is different than when the iCalendar object representation of the calendar service information was created or last modified. In the case of an iCalendar object that doesn't specify a "METHOD" property, this property is equivalent to the "LAST-MODIFIED" property. }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/386> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #385: This is not working properly
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#385: This is not working properly --------------------------------+------------------------------------------- Reporter: jpr.guru@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 4: Nice to have | Milestone: Later Component: Calendar Server | Severity: Performance Keywords: performance | --------------------------------+------------------------------------------- This application is not working properly on my browser IE 8 -- Ticket URL: <http://trac.calendarserver.org/ticket/385> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2