Your message dated Sat, 02 Nov 2013 01:55:51 +0530
with message-id <[email protected]>
and subject line Unable to reproduce the bug
has caused the Debian Bug report #724683,
regarding calendarserver: Actions need to be performed twice
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.)


-- 
724683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724683
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: calendarserver
Version: 3.2+dfsg-4
Severity: grave
Justification: renders package unusable

Actions performed on a calendar need to be performed twice to succeed.

Steps to reproduce:
 1. Start iCal with the calendar already configured, and a fresh install of
calendarserver with default settings.
 2. Create an event; its description is "New Event" by default.
 3. Change the name of the event to "Test"; after a few seconds, the name goes
back to "New Event"
 4. Change the name of the avant to "Test again"; now the change sticks

Changing the time of an event, its location, its note, or any other property
gives the same result.

I have captured the traffic between the client and the server (see attached
file). It can be seen that the client is sending conditional PUT requests. Half
of those requests fail, because after every successful request, the server does
not provide the client with the new ETag. So the next request fails. The client
needs to send a GET request to get the new ETag and be able to place a new PUT
request that will succeed.

-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-0.bpo.2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages calendarserver depends on:
ii  adduser                3.113+nmu3
ii  libc6                  2.13-38
ii  lsb-base               4.1+Debian8+deb7u1
ii  memcached              1.4.13-0.2
ii  python                 2.7.3-4
ii  python-dateutil        1.5+dfsg-0.1
ii  python-kerberos        1.1+svn4895-1+b2
ii  python-openssl         0.13-2+deb7u1
ii  python-plist           1.8-1
ii  python-pycalendar      2.0~svn188-1
ii  python-pygresql        1:4.0-3
ii  python-pysqlite2       2.6.3-3
ii  python-sqlparse        0.1.4-1
ii  python-twisted-conch   1:12.0.0-1
ii  python-twisted-core    12.0.0-1
ii  python-twisted-mail    12.0.0-1
ii  python-twisted-web     12.0.0-1
ii  python-twisted-words   12.0.0-1
ii  python-xattr           0.6.4-2
ii  python-zope.interface  3.6.1-3
ii  ssl-cert               1.0.32

Versions of packages calendarserver recommends:
ii  python-ldap  2.4.10-1
ii  python-pam   0.4.2-13

calendarserver suggests no packages.

-- Configuration Files:
/etc/default/calendarserver changed:
start_calendarserver=yes



-- no debconf information

Attachment: calendarserver-bug.pcapng.gz
Description: GNU Zip compressed data


--- End Message ---
--- Begin Message ---
Package: calendarserver

--- Please enter the report below this line. ---
I have been unable to reproduce this bug from my end. Also, calendarserver 5.0 will be pushed to unstable soon. You can test it with the new release. Also, kindly don't set the severity of this bug to grave, as the package is fully functional currently.
--- End Message ---

Reply via email to