Hi Adam,
Thanks for the response. I missed out the submitters email id. I am working on a fix and should be submitting tomorrow.

I do understand that it is very unlikely that this fix can get into squeeze initial release taking into consideration that it is likely to be released on Feb 6.

I am a new (sponsored) maintainer and really not aware on how to handle this. I really don't think this bug is grave as it affects only a part of the calendarserver and most of the important features seem to be running fine. Anyway, I was wondering how do I get this fix into squeeze? Should it be done via security updates?

Thanks,
Rahul.

On Sunday 30 January 2011 09:40 PM, Adam D. Barratt wrote:
On Sat, 2011-01-29 at 07:40 +0530, Rahul Amaram wrote:
I am able to reproduce this problem. The reason for this issue is because data
in /var/run/caldavd was persistent in lenny unlike in squeeze.

Anyway, in spite of the error, I was able to access the calendar and create and
delete events and tasks properly. So I have two queries:
Did you intentionally not include the submitter on that mail?

1. For what are these files used i.e. what exactly is stored in these files?

2. When are these files used i.e. is it possible to give a scenario using
Thunderbird(+Lightning) as to when these files are used?
I don't know much at all about the package, but the files are generated
by twistedcaldav/directory/{calendaruserproxy,resourceinfo}.py.  The
brief docstrings in each of those files read:

Implements a calendar user proxy principal.

Database for storing extra resource information, such as auto-schedule
A database to maintain resource (and location) information

Each file is created in config.DataRoot, which appears to be explicitly
set to /var/run/caldavd by debian/patches/paths.diff.

I will try to get out a fix soon.
Given the closeness of the scheduled release, possible values of "soon"
are quite small right now.

Regards,

Adam



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to