#406: calendarserver_export uses CalDAVFile ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- Comment(by mail@…): The error message one gets for google to index: {{{ Traceback (most recent call last): File "/usr/bin/calendarserver_export", line 43, in <module> from calendarserver.tools.export import main File "/usr/lib/python2.7/site-packages/calendarserver/tools/export.py", line 44, in <module> from twistedcaldav.static import CalDAVFile ImportError: No module named static }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/406#comment:1> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

#406: calendarserver_export uses CalDAVFile ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- Comment(by mail@…): My fix does not really solve the problem which requires way more work: {{{ <fmms> glyph, just patched that have a look at the ticket <glyph> fmms: it's not quite that simple <fmms> at least then i can read the help ;) <glyph> fmms: the data-store API is completely different now, CalDAVResource isn't backed by files on disk. Even if you use the (unsupported) filesystem backend, it has a different API. <glyph> yeah that tool just hasn't been updated yet <glyph> it's not a matter of a single import, it needs to be rewritten :) <fmms> glyph, i am just using the filesystem backend, why is it not supported? <fmms> what does that mean, will you remove it any day, or will bugs be fixed slower? <glyph> fmms: It means that you should use the database backend because that's the one that's supposed to work :). }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/406#comment:3> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

#406: calendarserver_export uses CalDAVFile ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: sagen@… Type: Defect | Status: new Priority: 1: Blocker | Milestone: CalendarServer-3.0 Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- Comment(by mail@…): I think this issue has been fixed at least partly by commit r7486 ?? One question why does this use {{{/etc/cardavd/caldavd.plist}}} instead of {{{/etc/caldavd/caldavd.plist}}}? -- Ticket URL: <http://trac.calendarserver.org/ticket/406#comment:5> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

#406: calendarserver_export uses CalDAVFile -----------------------------------+---------------------------------------- Reporter: mail@… | Owner: sagen@… Type: Defect | Status: closed Priority: 1: Blocker | Milestone: CalendarServer-3.0 Component: Calendar Server | Severity: Other Resolution: Software changed | Keywords: Radar: | -----------------------------------+---------------------------------------- Changes (by glyph@…): * status: new => closed * resolution: => Software changed Comment: The wrong-default-config-file issue fixed in http://trac.calendarserver.org/changeset/7489. Thanks for reporting the bug! -- Ticket URL: <http://trac.calendarserver.org/ticket/406#comment:7> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server