FFe: Sync calendarserver 5.1+dfsg-1 (universe) from Debian unstable (main)

Bug #1290218 reported by Rahul Amaram
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
calendarserver (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Please sync calendarserver 5.1+dfsg-1 (universe) from Debian unstable (main)

Explanation of FeatureFreeze exception:
I am the Debian maintainer for Apple calendaserver. I have uploaded the latest release for calendarserver (version 5.1). It would be great to get 5.1 into trusty. The current version 3.2 in trusty is sort of outdated. I can help with fixing important bugs on a priority basis to expedite the process of having 5.1 running smoothly in Ubuntu Trusty.

Changelog entries since current trusty version 3.2+dfsg-5:

calendarserver (5.1+dfsg-1) unstable; urgency=low

  * New upstream release (Closes: #709607)
  * Updated NSS Configuration documentation (Closes: #696334)
  * Added documentation for PostgreSQL Peer authentication. Also debianized
    bootstrapdatabase.py (Thanks to Georges Racinet and Fredrik Unger)
    (Closes: #696931)
  * Removed fields Vcs-Svn and Vcs-Browser as they were pointing to upstream
    sources rather than that where the debian package is maintained (Closes:
    #709608)
  * IPv6 support added upstream (Closes: #719649)
  * Removed patch py-ssize-t-fix.patch as it has been included upstream in
    r9700 (See http://trac.calendarserver.org/ticket/448)
  * Removed upgrade-nss-data-directories.py script and related changes. This
    was being used to address an issue when upgrading from 1.2 to 2.4 (See
    Debian Bug#610124). As we have had two major versions released since then,
    we believe it to be safe to remove this fix.
  * Removed zoneinfo.patch

 -- Rahul Amaram <email address hidden> Sun, 23 Feb 2014 10:51:58 +0530

Revision history for this message
Rahul Amaram (amaramrahul) wrote :

Any update on this?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in calendarserver (Ubuntu):
status: New → Confirmed
Revision history for this message
Rahul Amaram (amaramrahul) wrote :

Just curious as the trusty release is almost on the corner. Is there any idea to still have calendarserver 5.1 into Trusty?

Revision history for this message
Rahul Amaram (amaramrahul) wrote :

As suggested by Andrew, I am attaching the build log for calendarserver and python-pycalendar for Ubuntu Trusty. Also, I did some basic testing with NSS directory backend and adding / removing / modifying events work fine. There were a couple of non-Ubuntu specific bugs which I encountered which I will get fixed on a priority if this package is likely to be accepted into Trusty (even otherwise I need to fix them but maybe not on a priority basis).

Revision history for this message
Rahul Amaram (amaramrahul) wrote :
Revision history for this message
Stefano Rivera (stefanor) wrote :

This is a leaf, unseeded package, so very low risk.

The bugs that you mentioned. Are they regressions in 5.1? I wouldn't want to upgrade to a known-buggy release.

Revision history for this message
Rahul Amaram (amaramrahul) wrote :

Hi Stefano, There were two issues faced:

1. Migrated data from earlier versions would not be visible. The fix for this is to use the same guid that was being auto-generated earlier. I have written a script for getting this auto-generated guid.

2. The second issue was that tasks were not visible from Thunderbird. This could be changed using a configuration option, which is currently not set in 5.1.

I have addressed both these issues in version 5.2 which I have just pushed into debian unstable. It would be great if you could sync calendarserver 5.2 and pycalendar 2.0~svn13177-1 from debian unstable.

Alternatively, I could backport the script and config changes to 5.1.

Let me know what works.

Revision history for this message
Rahul Amaram (amaramrahul) wrote :

calendarserver 5.2 is already into unstable :).

Revision history for this message
Stefano Rivera (stefanor) wrote :

Sure, let's do it. I'll grant the FFe and sponsor the upload for you.

Changed in calendarserver (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Stefano Rivera (stefanor) wrote :

This bug was fixed in the package calendarserver - 5.2+dfsg-1
Sponsored for Rahul Amaram (amaramrahul)

---------------
calendarserver (5.2+dfsg-1) unstable; urgency=high

  * New upstream release
  * Provided instructions on how to ensure data migration with XML Directory
    Backend while upgrading (Closes: #744889)

 -- Rahul Amaram <email address hidden> Mon, 14 Apr 2014 06:02:38 +0530

calendarserver (5.1+dfsg-1) unstable; urgency=low

  * New upstream release (Closes: #709607)
  * Updated NSS Configuration documentation (Closes: #696334)
  * Added documentation for PostgreSQL Peer authentication. Also debianized
    bootstrapdatabase.py (Thanks to Georges Racinet and Fredrik Unger)
    (Closes: #696931)
  * Removed fields Vcs-Svn and Vcs-Browser as they were pointing to upstream
    sources rather than that where the debian package is maintained (Closes:
    #709608)
  * IPv6 support added upstream (Closes: #719649)
  * Removed patch py-ssize-t-fix.patch as it has been included upstream in
    r9700 (See http://trac.calendarserver.org/ticket/448)
  * Removed upgrade-nss-data-directories.py script and related changes. This
    was being used to address an issue when upgrading from 1.2 to 2.4 (See
    Debian Bug#610124). As we have had two major versions released since then,
    we believe it to be safe to remove this fix.
  * Removed zoneinfo.patch

 -- Rahul Amaram <email address hidden> Sun, 23 Feb 2014 10:51:58 +0530

Changed in calendarserver (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Rahul Amaram (amaramrahul) wrote :

We will also need to migrate pycalendar 2.0~svn13177-1.

Revision history for this message
Rahul Amaram (amaramrahul) wrote :

Raised a sync request for pycalendar as well - https://bugs.launchpad.net/bugs/1308587

Revision history for this message
Stefano Rivera (stefanor) wrote :

Ah, I missed your mentions of pycalendar here. Next time, open a task in the same bug.

I also guess your dependencies between the two are too loose, if calendarserver requires a newer pycalendar.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.