On 20/01/16 19:07, Rahul Amaram wrote: > > > On Wednesday 20 January 2016 11:31 PM, Ximin Luo wrote: >> On 20/01/16 18:48, Rahul Amaram wrote: >>> I had removed the calenarserver_upgrade instructions from README.Debian >>> because it was not working and I was assuming that when I start >>> calendarserver the upgrade will happen automatically. I will take care of >>> all the points that you have mentioned and also mostly write a script for >>> xml file upgrade while installing calendarserver 7.0. But this is odd. I >>> feel, upstream should take care of all these upgrades automatically :). >>> >> Yes, they ought to have better documentation to help admins during upgrades. >> :( Even doc/Admin/DirectoryService-XML.rst describes the old format... I had >> to guess and also by looking at the output of >> http://$server:8008/addressbooks/ >:( >> >>> Thanks for all the help. I just can't tell you how awesome you have been. I >>> do have one final request. I need the packages twextypy and pg8000 to be >>> uploaded to Debian. I have reached out to my mentor but have not yet heard. >>> He gets busy at times. In case I do not hear from him, would you be willing >>> to upload these two packages? I have already raised ITP for them. >>> >> Sure, just let me know when you are ready. :) You can either send me a link >> to a git commit, or a link to a .dsc that you upload to mentors.debian.net. > Should I tag the commit so that you can easily build from it? If you would be > reviewing it, it might be better to do it before I tag it. I will anyway, > implement all your suggestions in the earlier mails. If you have anything > apart from that, let me know.
No, just a commit reference will do, I can find it. I usually only tag things after I get the "ACCEPTED" email from ftp-master, and then I run "gbp buildpackage --git-tag-only" and push it. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
