Your message dated Sun, 24 Mar 2013 03:43:55 +0100
with message-id <[email protected]>
and subject line Re: mention carddav support in description
has caused the Debian Bug report #650977,
regarding mention carddav support in description
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
650977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650977
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: davical
Version: 0.9.9.7-1
Severity: wishlist

i'd like to suggest to mention the support for CardDAV, which is present
in davical since around 0.9.9[1], in the long description of davical.

rationale: whoever wants to use carddav on his debian system is likely
to start with `apt-cache search carddav` and not find a server, although
davical is present in the repositories. (afaict it's the only server
that can do that currently; apple's calendarserver starts supporting it
in unreleased 3.0, and radicale only has a carddav branch by now.)

the new wording could be "... to trivially store CalDAV calendars and
CardDAV address books, such as ...".

[1] http://wiki.davical.org/w/CardDAV

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
fixed 650977 1.0.0-1
stop

Hi.
AFAICS this was fixed in upstream commit
23dd6285d75ebd1660ca804ae83c1d3914b59327 and therefore probably in the
1.0.0-1 version.

Therefore closing this bug now.


Cheers,
Chris.

Attachment: smime.p7s
Description: S/MIME cryptographic signature


--- End Message ---

Reply via email to