[email protected] (Remi Locherer), 2017.03.06 (Mon) 08:34 (CET):
> On Sun, Mar 05, 2017 at 10:42:33PM +0000, Stuart Henderson wrote:
> > On 2017/03/05 23:21, Remi Locherer wrote:
> > > attached a port of vdirsyncer plus it's dependencies.
> >
> > I've just had a quick read through; in a few of the ports you have hardcoded
> > ,python3 in deps, this should be ${MODPY_FLAVOR}. It's a noop for vdirsyncer
> > itself though we are generally doing this anyway and it saves trouble if
> > we change things in ports later, but for some of the other ports it's
> > wrong as-is i.e. py-requests-toolbelt depends on www/py-requests,python3
> > even for the py27 one. Similarly should use sphinx-build${MODPY_BIN_SUFFIX}
> > rather than hardcoded sphinx-build-3.
> >
> > One other nit, please use "Yes" instead of "YES" for PERMIT_PACKAGE_CDROM.
> >
> > Other than that, looks good to me.
>
> Thank you for reviewing my ports!
>
> Attached updated tarballs.
Happy tester here: works.
Thanks for bringing that software to my doorstep!
For py-click-log I had to change the distinfo to:
SHA256 (click-log-0.1.8.tar.gz) =
57271008c12e2dc16d413373bedd7fd3ff17c57434e168650dc27dfb9c743392
SIZE (click-log-0.1.8.tar.gz) = 9277
vdirsyncer Makefile had to be adjusted:
-BUILD_DEPENDS = textproc/py-sphinx,python3
+BUILD_DEPENDS = textproc/py3-sphinx,python3
(at least that's what was starting to build when I did 'make' in
mystuff/productivity/vdirsyncer. I had pkg_add-ed py-sphinx already.)
Upon first run:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
vdirsyncer --help
Traceback (most recent call last):
File "/usr/local/bin/vdirsyncer", line 11, in <module>
load_entry_point('vdirsyncer==0.15.0', 'console_scripts', 'vdirsyncer')()
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 716, in
__call__
return self.main(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 675, in main
_verify_python3_env()
File "/usr/local/lib/python3.6/site-packages/click/_unicodefun.py", line 119,
in _verify_python3_env
'mitigation steps.' + extra)
RuntimeError: Click will abort further execution because Python 3 was
configured to use ASCII as encoding for the environment. Either run this under
Python 2 or consult http://click.pocoo.org/python3/ for mitigation steps.
This system supports the C.UTF-8 locale which is recommended.
You might be able to resolve your issue by exporting the
following environment variables:
export LC_ALL=C.UTF-8
export LANG=C.UTF-8
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
With these it works (LC_ALL=C.UTF-8 alone is actually enough for me):
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
vdirsyncer --help
Usage: vdirsyncer [OPTIONS] COMMAND [ARGS]...
Synchronize calendars and contacts
Options:
-v, --verbosity LVL Either CRITICAL, ERROR, WARNING, INFO or DEBUG
--version Show the version and exit.
-c, --config FILE Config file to use.
--help Show this message and exit.
Commands:
discover Refresh collection cache for the given pairs.
metasync Synchronize metadata of the given collections...
repair Repair a given collection.
sync Synchronize the given collections or pairs.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Getting https to work was only possible via "verify_fingerprint = " and
verify = false. This is although it's a letsenkrypt cert... (cadaver
complains, too.)
To make my SOGo caldav/carddav server working with vdirsync I had to add
the following to the front end webserver:
RedirectMatch ^/principals/users/(.*)$ https://dav.domain.foo/SOGo/dav/$1
RedirectMatch ^/principals/$ https://dav.domain.foo/SOGo/dav/
RedirectMatch ^/.well-known/(caldav|carddav)$ https://dav.domain.foo/SOGo/dav/
Even if the url in .vcardsync/config already points to
https://dav.domain.foo/SOGo/dav/username.
vdirsync just wants https://dav.domain.foo/.well-known/(caldav|carddav)
Thanks, Marcus
> !DSPAM:58bd110f119611904443423!