Your message dated Tue, 8 Aug 2017 20:42:58 +0530
with message-id <18d84bc6-3846-0b9c-28b9-1a3adf5ef...@amaram.name>
and subject line Re: Bug#870926: calendarserver: should calendarserver be 
removed from unstable?
has caused the Debian Bug report #870926,
regarding calendarserver: should calendarserver be removed from unstable?
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 ow...@bugs.debian.org
immediately.)


-- 
870926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: calendarserver
User: debian...@lists.debian.org
Usertags: qa-removals-post-stretch

Hi,

Following a discussion[1] on the debian-qa@ mailing list on packages that
missed both jessie and stretch, I am proposing the removal of this package from
unstable, because:

  it was in unstable at the time of the stretch freeze
    but wasn't part of stretch
AND
  it was in unstable at the time of the jessie freeze
    but it wasn't part of jessie
AND
  it is still not in testing
AND
  it was not uploaded since the beginning of 2017.

If you disagree and think that this package should remain in unstable, feel
free to just close this bug.

If this bug is still open one month from now (on 2017-09-06), it will be turned
into a removal request, using:

  reassign -1 ftp.debian.org
  retitle -1 RM: calendarserver -- RoQA; missed both jessie and stretch
  thanks

- Lucas, for the QA team.


[1] https://lists.debian.org/debian-qa/2017/07/msg00021.html

--- End Message ---
--- Begin Message ---
Hi,
I am currently the maintainer for Debian calendarserver. I do intend on maintaining it. Actually for both jessie and stretch, I had prepared the releases, but right before the freeze, something came-up and it got pushed out of testing. However, it always was in the right shape with no blockers during Ubuntu LTS releases and hence has always managed to get into Ubuntu LTS.

The reason why it is currently not in testing is because calendarserver depends on sqlparse library, which had been updated to 0.2.x series and the then released calendarserver version (9.0) was not compatible with it. I see that a newer version of calendarserver (9.1) has been released which is compatible with the latest sqlparse library.

I will work on updating the package this month.

Thanks,
Rahul.

On Sunday 06 August 2017 07:20 PM, Lucas Nussbaum wrote:
Source: calendarserver
User: debian...@lists.debian.org
Usertags: qa-removals-post-stretch

Hi,

Following a discussion[1] on the debian-qa@ mailing list on packages that
missed both jessie and stretch, I am proposing the removal of this package from
unstable, because:

   it was in unstable at the time of the stretch freeze
     but wasn't part of stretch
AND
   it was in unstable at the time of the jessie freeze
     but it wasn't part of jessie
AND
   it is still not in testing
AND
   it was not uploaded since the beginning of 2017.

If you disagree and think that this package should remain in unstable, feel
free to just close this bug.

If this bug is still open one month from now (on 2017-09-06), it will be turned
into a removal request, using:

   reassign -1 ftp.debian.org
   retitle -1 RM: calendarserver -- RoQA; missed both jessie and stretch
   thanks

- Lucas, for the QA team.


[1] https://lists.debian.org/debian-qa/2017/07/msg00021.html


--
http://rahul.amaram.name

--- End Message ---

Reply via email to