Is 9.0 fully backward compatible with 7.0? Are there any schema changes, XML structure changes between the two ? I have data created with 7.0. Would the upgrade work seamlessly? Anything that needs to be taken care of? On Tue, Nov 29, 2016 at 12:32 PM, Andre LaBranche <dre@apple.com> wrote:

Hi,

Several months ago, the repo moved from macosforge to github. Please see: https://github.com/apple/ccs-calendarserver/releases

In particular, the 9.0 release: "This is the first release to support dependency bootstrapping following our move from macosforge to github."

Due to the differences between git and svn, it's not completely trivial to make a version older than 9.0 use github. Note that older versions of the code still work, but the bootstrapping won't, so you would have to manually satisfy the dependencies. It would likely be a better use of time to upgrade to 9.0.

-dre

On Nov 29, 2016, at 12:21 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

Hi,

I am using CalendarServer-7.0. I was able to install successfully so far.

But today suddenly, on a fresh install, I get the following error:

Please help me resolve this.

Obtaining twextpy from svn+http://svn.calendarserver. org/repository/calendarserver/twext/branches/release/twext- 7.0-dev@15059#egg=twextpy (from -r /opt/caldavd/CalendarServer-7.0/requirements-stable.txt (line 9))

Checking out http://svn.calendarserver.org/repository/calendarserver/ twext/branches/release/twext-7.0-dev (to revision 15059) to ./.develop/virtualenv/src/twextpy

svn: E170013: Unable to connect to a repository at URL ' http://svn.calendarserver.org/repository/calendarserver/ twext/branches/release/twext-7.0-dev'

svn: E175013: Access to '/repository/calendarserver/ twext/branches/release/twext-7.0-dev' forbidden

Complete output from command svn checkout -q -r 15059 http://svn.calendarserver.org/repository/calendarserver/ twext/branches/release/twext-7.0-dev /opt/caldavd/CalendarServer-7. 0/.develop/virtualenv/src/twextpy:

----------------------------------------

Command "svn checkout -q -r 15059 http://svn.calendarserver.org/ repository/calendarserver/twext/branches/release/twext-7.0-dev /opt/caldavd/CalendarServer-7.0/.develop/virtualenv/src/twextpy" failed with error code 1 in None

ERROR: calendarserver_config not found!? _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-users

* Unfortunately, I lost my old installation (via SVN) of CalendarServer-7.0 in development env. * However, Production env still runs CalendarServer-7.0 via SVN. To test the upgrade, can I do following: 1) Create a CalendarServer-7.0 using GitHub 2) Create data and xml files thru clients 3) Upgrade to CalendarServer-9.0 using GitHub 4) Use calendarserver_upgrade to upgrade as necessary Would this be equivalent to test upgrade of CalendarServer-7.0 installed via GitHub? On Tue, Nov 29, 2016 at 12:39 PM, Andre LaBranche <dre@apple.com> wrote:

On Nov 29, 2016, at 12:34 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

Is 9.0 fully backward compatible with 7.0?

Data created in 7 can be upgraded to 9. Data created in any version generally cannot be used with an older version.

Are there any schema changes, XML structure changes between the two ?

There are schema changes. I don't think there are any plist changes.

I have data created with 7.0. Would the upgrade work seamlessly?

It should. Attempting to start the service for the first time after upgrading should fail, with a message that upgrade is required. You can then call the calendarserver_upgrade tool to do that upgrade.

Anything that needs to be taken care of?

Just the standard testing / validation around any significant change.

-dre

On Tue, Nov 29, 2016 at 12:32 PM, Andre LaBranche <dre@apple.com> wrote:

...

Hi,

Several months ago, the repo moved from macosforge to github. Please see: https://github.com/apple/ccs-calendarserver/releases

In particular, the 9.0 release: "This is the first release to support dependency bootstrapping following our move from macosforge to github."

Due to the differences between git and svn, it's not completely trivial to make a version older than 9.0 use github. Note that older versions of the code still work, but the bootstrapping won't, so you would have to manually satisfy the dependencies. It would likely be a better use of time to upgrade to 9.0.

-dre

On Nov 29, 2016, at 12:21 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

Hi,

I am using CalendarServer-7.0. I was able to install successfully so far.

But today suddenly, on a fresh install, I get the following error:

Please help me resolve this.

Obtaining twextpy from svn+http://svn.calendarserver. org/repository/calendarserver/twext/branches/release/twext-7 .0-dev@15059#egg=twextpy (from -r /opt/caldavd/CalendarServer-7.0/requirements-stable.txt (line 9))

Checking out http://svn.calendarserver.org/ repository/calendarserver/twext/branches/release/twext-7.0-dev (to revision 15059) to ./.develop/virtualenv/src/twextpy

svn: E170013: Unable to connect to a repository at URL ' http://svn.calendarserver.org/repository/calendarserver/twe xt/branches/release/twext-7.0-dev'

svn: E175013: Access to '/repository/calendarserver/tw ext/branches/release/twext-7.0-dev' forbidden

Complete output from command svn checkout -q -r 15059 http://svn.calendarserver.org/repository/calendarserver/twex t/branches/release/twext-7.0-dev /opt/caldavd/CalendarServer-7. 0/.develop/virtualenv/src/twextpy:

----------------------------------------

Command "svn checkout -q -r 15059 http://svn.calendarserver.org/ repository/calendarserver/twext/branches/release/twext-7.0-dev /opt/caldavd/CalendarServer-7.0/.develop/virtualenv/src/twextpy" failed with error code 1 in None

ERROR: calendarserver_config not found!? _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-users

Ok. I see ccs-CalendarServer-7.0 in GitHub also uses SVN On Tue, Nov 29, 2016 at 12:49 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

Typo in last line / questions

Would this be equivalent to test upgrade of CalendarServer-7.0 installed via SVN?

On Tue, Nov 29, 2016 at 12:47 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

...

* Unfortunately, I lost my old installation (via SVN) of CalendarServer-7.0 in development env. * However, Production env still runs CalendarServer-7.0 via SVN.

To test the upgrade, can I do following:

1) Create a CalendarServer-7.0 using GitHub 2) Create data and xml files thru clients 3) Upgrade to CalendarServer-9.0 using GitHub 4) Use calendarserver_upgrade to upgrade as necessary

Would this be equivalent to test upgrade of CalendarServer-7.0 installed via GitHub?

On Tue, Nov 29, 2016 at 12:39 PM, Andre LaBranche <dre@apple.com> wrote:

...

On Nov 29, 2016, at 12:34 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

Is 9.0 fully backward compatible with 7.0?

Data created in 7 can be upgraded to 9. Data created in any version generally cannot be used with an older version.

Are there any schema changes, XML structure changes between the two ?

There are schema changes. I don't think there are any plist changes.

I have data created with 7.0. Would the upgrade work seamlessly?

It should. Attempting to start the service for the first time after upgrading should fail, with a message that upgrade is required. You can then call the calendarserver_upgrade tool to do that upgrade.

Anything that needs to be taken care of?

Just the standard testing / validation around any significant change.

-dre

On Tue, Nov 29, 2016 at 12:32 PM, Andre LaBranche <dre@apple.com> wrote:

...

Hi,

Several months ago, the repo moved from macosforge to github. Please see: https://github.com/apple/ccs-calendarserver/releases

In particular, the 9.0 release: "This is the first release to support dependency bootstrapping following our move from macosforge to github."

Due to the differences between git and svn, it's not completely trivial to make a version older than 9.0 use github. Note that older versions of the code still work, but the bootstrapping won't, so you would have to manually satisfy the dependencies. It would likely be a better use of time to upgrade to 9.0.

-dre

On Nov 29, 2016, at 12:21 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

Hi,

I am using CalendarServer-7.0. I was able to install successfully so far.

But today suddenly, on a fresh install, I get the following error:

Please help me resolve this.

Obtaining twextpy from svn+http://svn.calendarserver. org/repository/calendarserver/twext/branches/release/twext-7 .0-dev@15059#egg=twextpy (from -r /opt/caldavd/CalendarServer-7.0/requirements-stable.txt (line 9))

Checking out http://svn.calendarserver.org/ repository/calendarserver/twext/branches/release/twext-7.0-dev (to revision 15059) to ./.develop/virtualenv/src/twextpy

svn: E170013: Unable to connect to a repository at URL ' http://svn.calendarserver.org/repository/calendarserver/twe xt/branches/release/twext-7.0-dev'

svn: E175013: Access to '/repository/calendarserver/tw ext/branches/release/twext-7.0-dev' forbidden

Complete output from command svn checkout -q -r 15059 http://svn.calendarserver.org/repository/calendarserver/twex t/branches/release/twext-7.0-dev /opt/caldavd/CalendarServer-7. 0/.develop/virtualenv/src/twextpy:

----------------------------------------

Command "svn checkout -q -r 15059 http://svn.calendarserver.org/ repository/calendarserver/twext/branches/release/twext-7.0-dev /opt/caldavd/CalendarServer-7.0/.develop/virtualenv/src/twextpy" failed with error code 1 in None

ERROR: calendarserver_config not found!? _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-users

Would it possible for you to please provide Git mapping for: --editable svn+ http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... --editable svn+ http://svn.calendarserver.org/repository/calendarserver/PyKerberos/trunk@134... --editable svn+ http://svn.calendarserver.org/repository/calendarserver/PyCalendar/trunk@150... Best Regards, On Tue, Nov 29, 2016 at 1:00 PM, Andre LaBranche <dre@apple.com> wrote:

On Nov 29, 2016, at 12:47 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

* Unfortunately, I lost my old installation (via SVN) of CalendarServer-7.0 in development env. * However, Production env still runs CalendarServer-7.0 via SVN.

To test the upgrade, can I do following:

1) Create a CalendarServer-7.0 using GitHub 2) Create data and xml files thru clients 3) Upgrade to CalendarServer-9.0 using GitHub 4) Use calendarserver_upgrade to upgrade as necessary

Would this be equivalent to test upgrade of CalendarServer-7.0 installed via GitHub?

Yes, you will just have to do what Cyrus suggested to get 7.0 working from github. Once the service is operational, it doesn't really matter how the service was bootstrapped, and it doesn't influence the upgrade process.

I would suggest taking this opportunity to learn how to migrate / copy data and config from one instance to another, with the goal of being able to test the upgrade to v9 with a copy of your real data, but without taking the v7 instance out of service until you are comfortable that everything is working in v9. For the most part this just involves making a 'staging' copy of the PG DB, copying the configs / other data files over to a fresh CS instance, and tweaking stuff as needed for the specifics of the test environment (i.e. possibly different hostnames, different DB, etc). Then you can do the upgrade of the real data in the test instance, which is a better test than if you only use data created in a fresh v7 instance.

-dre

On Tue, Nov 29, 2016 at 12:39 PM, Andre LaBranche <dre@apple.com> wrote:

...

On Nov 29, 2016, at 12:34 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

Is 9.0 fully backward compatible with 7.0?

Data created in 7 can be upgraded to 9. Data created in any version generally cannot be used with an older version.

Are there any schema changes, XML structure changes between the two ?

There are schema changes. I don't think there are any plist changes.

I have data created with 7.0. Would the upgrade work seamlessly?

It should. Attempting to start the service for the first time after upgrading should fail, with a message that upgrade is required. You can then call the calendarserver_upgrade tool to do that upgrade.

Anything that needs to be taken care of?

Just the standard testing / validation around any significant change.

-dre

On Tue, Nov 29, 2016 at 12:32 PM, Andre LaBranche <dre@apple.com> wrote:

...

Hi,

Several months ago, the repo moved from macosforge to github. Please see: https://github.com/apple/ccs-calendarserver/releases

In particular, the 9.0 release: "This is the first release to support dependency bootstrapping following our move from macosforge to github."

Due to the differences between git and svn, it's not completely trivial to make a version older than 9.0 use github. Note that older versions of the code still work, but the bootstrapping won't, so you would have to manually satisfy the dependencies. It would likely be a better use of time to upgrade to 9.0.

-dre

On Nov 29, 2016, at 12:21 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

Hi,

I am using CalendarServer-7.0. I was able to install successfully so far.

But today suddenly, on a fresh install, I get the following error:

Please help me resolve this.

Obtaining twextpy from svn+http://svn.calendarserver. org/repository/calendarserver/twext/branches/release/twext-7 .0-dev@15059#egg=twextpy (from -r /opt/caldavd/CalendarServer-7.0/requirements-stable.txt (line 9))

Checking out http://svn.calendarserver.org/ repository/calendarserver/twext/branches/release/twext-7.0-dev (to revision 15059) to ./.develop/virtualenv/src/twextpy

svn: E170013: Unable to connect to a repository at URL ' http://svn.calendarserver.org/repository/calendarserver/twe xt/branches/release/twext-7.0-dev'

svn: E175013: Access to '/repository/calendarserver/tw ext/branches/release/twext-7.0-dev' forbidden

Complete output from command svn checkout -q -r 15059 http://svn.calendarserver.org/repository/calendarserver/twex t/branches/release/twext-7.0-dev /opt/caldavd/CalendarServer-7. 0/.develop/virtualenv/src/twextpy:

----------------------------------------

Command "svn checkout -q -r 15059 http://svn.calendarserver.org/ repository/calendarserver/twext/branches/release/twext-7.0-dev /opt/caldavd/CalendarServer-7.0/.develop/virtualenv/src/twextpy" failed with error code 1 in None

ERROR: calendarserver_config not found!? _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-users

Hi, There is a fancy redirect service that was deployed to help support our migration to github, which should do the mapping if you just open those links in a browser. I guess the pip stuff doesn't follow redirects, or you wouldn't have to do anything at all. ... and I guess another option is to use git cli tools to search the properties Cyrus just mentioned in his reply. -dre

On Nov 29, 2016, at 1:06 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

Would it possible for you to please provide Git mapping for:

--editable svn+http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev@15059#egg=twextpy>

--editable svn+http://svn.calendarserver.org/repository/calendarserver/PyKerberos/trunk@134... <http://svn.calendarserver.org/repository/calendarserver/PyKerberos/trunk@13420#egg=kerberos>

--editable svn+http://svn.calendarserver.org/repository/calendarserver/PyCalendar/trunk@150... <http://svn.calendarserver.org/repository/calendarserver/PyCalendar/trunk@15020#egg=pycalendar>

Best Regards,

On Tue, Nov 29, 2016 at 1:00 PM, Andre LaBranche <dre@apple.com <mailto:dre@apple.com>> wrote:

...

On Nov 29, 2016, at 12:47 PM, Gaurav Jain <monkeyfdude@gmail.com <mailto:monkeyfdude@gmail.com>> wrote:

* Unfortunately, I lost my old installation (via SVN) of CalendarServer-7.0 in development env. * However, Production env still runs CalendarServer-7.0 via SVN.

To test the upgrade, can I do following:

1) Create a CalendarServer-7.0 using GitHub 2) Create data and xml files thru clients 3) Upgrade to CalendarServer-9.0 using GitHub 4) Use calendarserver_upgrade to upgrade as necessary

Would this be equivalent to test upgrade of CalendarServer-7.0 installed via GitHub?

Yes, you will just have to do what Cyrus suggested to get 7.0 working from github. Once the service is operational, it doesn't really matter how the service was bootstrapped, and it doesn't influence the upgrade process.

I would suggest taking this opportunity to learn how to migrate / copy data and config from one instance to another, with the goal of being able to test the upgrade to v9 with a copy of your real data, but without taking the v7 instance out of service until you are comfortable that everything is working in v9. For the most part this just involves making a 'staging' copy of the PG DB, copying the configs / other data files over to a fresh CS instance, and tweaking stuff as needed for the specifics of the test environment (i.e. possibly different hostnames, different DB, etc). Then you can do the upgrade of the real data in the test instance, which is a better test than if you only use data created in a fresh v7 instance.

-dre

...

On Tue, Nov 29, 2016 at 12:39 PM, Andre LaBranche <dre@apple.com <mailto:dre@apple.com>> wrote:

...

On Nov 29, 2016, at 12:34 PM, Gaurav Jain <monkeyfdude@gmail.com <mailto:monkeyfdude@gmail.com>> wrote:

Is 9.0 fully backward compatible with 7.0?

Data created in 7 can be upgraded to 9. Data created in any version generally cannot be used with an older version.

...

Are there any schema changes, XML structure changes between the two ?

There are schema changes. I don't think there are any plist changes.

...

I have data created with 7.0. Would the upgrade work seamlessly?

It should. Attempting to start the service for the first time after upgrading should fail, with a message that upgrade is required. You can then call the calendarserver_upgrade tool to do that upgrade.

...

Anything that needs to be taken care of?

Just the standard testing / validation around any significant change.

-dre

...

On Tue, Nov 29, 2016 at 12:32 PM, Andre LaBranche <dre@apple.com <mailto:dre@apple.com>> wrote: Hi,

Several months ago, the repo moved from macosforge to github. Please see: https://github.com/apple/ccs-calendarserver/releases <https://github.com/apple/ccs-calendarserver/releases>

In particular, the 9.0 release: "This is the first release to support dependency bootstrapping following our move from macosforge to github."

Due to the differences between git and svn, it's not completely trivial to make a version older than 9.0 use github. Note that older versions of the code still work, but the bootstrapping won't, so you would have to manually satisfy the dependencies. It would likely be a better use of time to upgrade to 9.0.

-dre

...

On Nov 29, 2016, at 12:21 PM, Gaurav Jain <monkeyfdude@gmail.com <mailto:monkeyfdude@gmail.com>> wrote:

Hi,

I am using CalendarServer-7.0. I was able to install successfully so far.

But today suddenly, on a fresh install, I get the following error:

Please help me resolve this.

Obtaining twextpy from svn+http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev@15059#egg=twextpy> (from -r /opt/caldavd/CalendarServer-7.0/requirements-stable.txt (line 9))

Checking out http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev> (to revision 15059) to ./.develop/virtualenv/src/twextpy

svn: E170013: Unable to connect to a repository at URL 'http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev>'

svn: E175013: Access to '/repository/calendarserver/twext/branches/release/twext-7.0-dev' forbidden

Complete output from command svn checkout -q -r 15059 http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev> /opt/caldavd/CalendarServer-7.0/.develop/virtualenv/src/twextpy:

----------------------------------------

Command "svn checkout -q -r 15059 http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev> /opt/caldavd/CalendarServer-7.0/.develop/virtualenv/src/twextpy" failed with error code 1 in None

ERROR: calendarserver_config not found!?

_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org <mailto:calendarserver-users@lists.macosforge.org> https://lists.macosforge.org/mailman/listinfo/calendarserver-users <https://lists.macosforge.org/mailman/listinfo/calendarserver-users>

Hi Andre, Gaurav, --On November 29, 2016 at 4:23:34 PM -0500 Cyrus Daboo <cdaboo@apple.com> wrote:

Actually I don't think those URLs are working properly as they redirect to a completely different repo than the expected one!

Let me clarify: the SVN revisions in the requirements are sometimes not the svn revision of the last commit to a particular project, but rather the last commit to CalendarServer. So the URIs actually end up pointing to the wrong place in git. What I had to do was look at each ccs-* project in git and look through the commit history to find the svn revision less than or equal to the one in the SVN uri. -- Cyrus Daboo

Now, it failed on --editable svn+ http://svn.calendarserver.org/repository/calendarserver/CalDAVClientLibrary/... --editable svn+ http://svn.calendarserver.org/repository/calendarserver/CalDAVTester/branche... On Tue, Nov 29, 2016 at 1:32 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

I am trying. I will update with the results.

On Tue, Nov 29, 2016 at 1:31 PM, Cyrus Daboo <cdaboo@apple.com> wrote:

...

Hi Andre, Gaurav,

--On November 29, 2016 at 4:23:34 PM -0500 Cyrus Daboo <cdaboo@apple.com> wrote:

Actually I don't think those URLs are working properly as they redirect

...

to a completely different repo than the expected one!

Let me clarify: the SVN revisions in the requirements are sometimes not the svn revision of the last commit to a particular project, but rather the last commit to CalendarServer. So the URIs actually end up pointing to the wrong place in git.

What I had to do was look at each ccs-* project in git and look through the commit history to find the svn revision less than or equal to the one in the SVN uri.

-- Cyrus Daboo

Thank you so much. All the bootstrapping issues are resolved. Now, I hit following error: Can't roll back cryptography; was not uninstalled Command "/opt/caldavd/CalendarServer-7.0/.develop/virtualenv/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-M1eqq0/cryptography/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-bXjSbl-record/install-record.txt --single-version-externally-managed --compile --install-headers /opt/caldavd/CalendarServer-7.0/.develop/virtualenv/include/site/python2.7/cryptography" failed with error code 1 in /tmp/pip-build-M1eqq0/cryptography On Tue, Nov 29, 2016 at 1:54 PM, Cyrus Daboo <cdaboo@apple.com> wrote:

Hi Gaurav,

--On November 29, 2016 at 1:48:23 PM -0800 Gaurav Jain < monkeyfdude@gmail.com> wrote:

--editable svn+

...

http://svn.calendarserver.org/repository/calendarserver/CalDAVClientLibra ry/trunk@14856#egg=CalDAVClientLibrary

git-svn-id: https://svn.calendarserver.org/repository/calendarserver/Cal DAVClientLibrary/trunk@14856 commit 80b22707ae2b056a860449bbbe4bb7614cb70866

--editable svn+

...

http://svn.calendarserver.org/repository/calendarserver/CalDAVTester/bran ches/release/CalDAVTester-7.0-dev@15059#egg=CalDAVTester

git-svn-id: https://svn.calendarserver.org/repository/calendarserver/Cal DAVTester/trunk@15021 commit 0d27e502deb38a9336f0141cf4326d21fca3e60f

-- Cyrus Daboo

Preceding was this: x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -I/opt/caldavd/CalendarServer-7.0/.develop/roots/PostgreSQL/include -I/opt/caldavd/CalendarServer-7.0/.develop/roots/memcached/include -I/opt/caldavd/CalendarServer-7.0/.develop/roots/libevent/include -I/opt/caldavd/CalendarServer-7.0/.develop/roots/libffi/include -fPIC -I/usr/include/python2.7 -c src/cryptography/hazmat/bindings/__pycache__/_Cryptography_cffi_e7d09016xc302a38b.c -o build/temp.linux-x86_64-2.7/src/cryptography/hazmat/bindings/__pycache__/_Cryptography_cffi_e7d09016xc302a38b.o src/cryptography/hazmat/bindings/__pycache__/_Cryptography_cffi_e7d09016xc302a38b.c:505:6: error: conflicting types for ‘BIO_new_mem_buf’ BIO *BIO_new_mem_buf(void *, int); ^ In file included from /usr/include/openssl/asn1.h:65:0, from src/cryptography/hazmat/bindings/__pycache__/_Cryptography_cffi_e7d09016xc302a38b.c:220: /usr/include/openssl/bio.h:692:6: note: previous declaration of ‘BIO_new_mem_buf’ was here BIO *BIO_new_mem_buf(const void *buf, int len); ^ error: command 'x86_64-linux-gnu-gcc' failed with exit status 1 On Tue, Nov 29, 2016 at 2:03 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

I am on Ubuntu 16.06 AWS EC2 instance.

On Tue, Nov 29, 2016 at 2:00 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

...

Thank you so much. All the bootstrapping issues are resolved. Now, I hit following error:

Can't roll back cryptography; was not uninstalled

Command "/opt/caldavd/CalendarServer-7.0/.develop/virtualenv/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-bu ild-M1eqq0/cryptography/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-bXjSbl-record/install-record.txt --single-version-externally-managed --compile --install-headers /opt/caldavd/CalendarServer-7.0/.develop/virtualenv/include/site/python2.7/cryptography" failed with error code 1 in /tmp/pip-build-M1eqq0/cryptography

On Tue, Nov 29, 2016 at 1:54 PM, Cyrus Daboo <cdaboo@apple.com> wrote:

...

Hi Gaurav,

--On November 29, 2016 at 1:48:23 PM -0800 Gaurav Jain < monkeyfdude@gmail.com> wrote:

--editable svn+

...

http://svn.calendarserver.org/repository/calendarserver/CalD AVClientLibra ry/trunk@14856#egg=CalDAVClientLibrary

git-svn-id: https://svn.calendarserver.org/repository/calendarserver/Cal DAVClientLibrary/trunk@14856 commit 80b22707ae2b056a860449bbbe4bb7614cb70866

--editable svn+

...

http://svn.calendarserver.org/repository/calendarserver/CalD AVTester/bran ches/release/CalDAVTester-7.0-dev@15059#egg=CalDAVTester

git-svn-id: https://svn.calendarserver.org/repository/calendarserver/Cal DAVTester/trunk@15021 commit 0d27e502deb38a9336f0141cf4326d21fca3e60f

-- Cyrus Daboo

On Nov 29, 2016, at 1:00 PM, Andre LaBranche <dre@apple.com> wrote:

...

On Nov 29, 2016, at 12:47 PM, Gaurav Jain <monkeyfdude@gmail.com <mailto:monkeyfdude@gmail.com>> wrote:

* Unfortunately, I lost my old installation (via SVN) of CalendarServer-7.0 in development env. * However, Production env still runs CalendarServer-7.0 via SVN.

To test the upgrade, can I do following:

1) Create a CalendarServer-7.0 using GitHub 2) Create data and xml files thru clients 3) Upgrade to CalendarServer-9.0 using GitHub 4) Use calendarserver_upgrade to upgrade as necessary

Would this be equivalent to test upgrade of CalendarServer-7.0 installed via GitHub?

Yes, you will just have to do what Cyrus suggested to get 7.0 working from github. Once the service is operational, it doesn't really matter how the service was bootstrapped, and it doesn't influence the upgrade process.

I would suggest taking this opportunity to learn how to migrate / copy data and config from one instance to another, with the goal of being able to test the upgrade to v9 with a copy of your real data, but without taking the v7 instance out of service until you are comfortable that everything is working in v9. For the most part this just involves making a 'staging' copy of the PG DB, copying the configs / other data files over to a fresh CS instance, and tweaking stuff as needed for the specifics of the test environment (i.e. possibly different hostnames, different DB, etc).

... to expand on that a bit, be absolutely sure that nothing (writable) is shared between the test v9 instance and the prod v7 instance. This means discrete memcache service, and different filesystem paths for everything. This should be easy-ish if you're close to a default config, by simply using a different server root - most of the paths by default are children of server root, and are expressed as relative paths in the configs. It is ok to share the same directory service, whether it is xml or LDAP. Make fresh backups before you do anything :) -dre

Then you can do the upgrade of the real data in the test instance, which is a better test than if you only use data created in a fresh v7 instance.

-dre

...

On Tue, Nov 29, 2016 at 12:39 PM, Andre LaBranche <dre@apple.com <mailto:dre@apple.com>> wrote:

...

On Nov 29, 2016, at 12:34 PM, Gaurav Jain <monkeyfdude@gmail.com <mailto:monkeyfdude@gmail.com>> wrote:

Is 9.0 fully backward compatible with 7.0?

Data created in 7 can be upgraded to 9. Data created in any version generally cannot be used with an older version.

...

Are there any schema changes, XML structure changes between the two ?

There are schema changes. I don't think there are any plist changes.

...

I have data created with 7.0. Would the upgrade work seamlessly?

It should. Attempting to start the service for the first time after upgrading should fail, with a message that upgrade is required. You can then call the calendarserver_upgrade tool to do that upgrade.

...

Anything that needs to be taken care of?

Just the standard testing / validation around any significant change.

-dre

...

On Tue, Nov 29, 2016 at 12:32 PM, Andre LaBranche <dre@apple.com <mailto:dre@apple.com>> wrote: Hi,

Several months ago, the repo moved from macosforge to github. Please see: https://github.com/apple/ccs-calendarserver/releases <https://github.com/apple/ccs-calendarserver/releases>

In particular, the 9.0 release: "This is the first release to support dependency bootstrapping following our move from macosforge to github."

Due to the differences between git and svn, it's not completely trivial to make a version older than 9.0 use github. Note that older versions of the code still work, but the bootstrapping won't, so you would have to manually satisfy the dependencies. It would likely be a better use of time to upgrade to 9.0.

-dre

...

On Nov 29, 2016, at 12:21 PM, Gaurav Jain <monkeyfdude@gmail.com <mailto:monkeyfdude@gmail.com>> wrote:

Hi,

I am using CalendarServer-7.0. I was able to install successfully so far.

But today suddenly, on a fresh install, I get the following error:

Please help me resolve this.

Obtaining twextpy from svn+http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev@15059#egg=twextpy> (from -r /opt/caldavd/CalendarServer-7.0/requirements-stable.txt (line 9))

Checking out http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev> (to revision 15059) to ./.develop/virtualenv/src/twextpy

svn: E170013: Unable to connect to a repository at URL 'http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev>'

svn: E175013: Access to '/repository/calendarserver/twext/branches/release/twext-7.0-dev' forbidden

Complete output from command svn checkout -q -r 15059 http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev> /opt/caldavd/CalendarServer-7.0/.develop/virtualenv/src/twextpy:

----------------------------------------

Command "svn checkout -q -r 15059 http://svn.calendarserver.org/repository/calendarserver/twext/branches/relea... <http://svn.calendarserver.org/repository/calendarserver/twext/branches/release/twext-7.0-dev> /opt/caldavd/CalendarServer-7.0/.develop/virtualenv/src/twextpy" failed with error code 1 in None

ERROR: calendarserver_config not found!?

_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org <mailto:calendarserver-users@lists.macosforge.org> https://lists.macosforge.org/mailman/listinfo/calendarserver-users <https://lists.macosforge.org/mailman/listinfo/calendarserver-users>

_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org <mailto:calendarserver-users@lists.macosforge.org> https://lists.macosforge.org/mailman/listinfo/calendarserver-users <https://lists.macosforge.org/mailman/listinfo/calendarserver-users>