On Sun, Nov 12, 2017 at 11:30:48AM +0000, Edd Barrett wrote: > To accompany the new neovim, here's an update to the Python bindings. > Please test (:CheckHealth is your friend).
I've just realised a problem with this port. The distfile filename clashes with the old version of neovim (both called neovim-0.2.0.tar.gz). Then pypi seems broken: ---8<--- >> Fetch https://pypi.io/packages/source/n/neovim/neovim-0.2.0.tar.gz ftp: SSL write error: ocsp verify failed: ocsp response not current >> Fetch https://ftp.openbsd.org/pub/OpenBSD/distfiles//neovim-0.2.0.tar.gz ftp: SSL write error: ocsp verify failed: ocsp response not current --->8--- This is probably my crappy DSL router hosing SSL -- wouldn't be the first time. But anyway, if the fetch from pypi falls, it falls back to our mirrors and fetches the wrong distfile (the older version of neovim itself): ---8<--- >> Fetch https://ftp.usa.openbsd.org/pub/OpenBSD/distfiles//neovim-0.2.0.tar.gz ... >> Size does not match for neovim-0.2.0.tar.gz >> Fetch https://ftp.fr.openbsd.org/pub/OpenBSD/distfiles//neovim-0.2.0.tar.gz ... >> Size does not match for neovim-0.2.0.tar.gz --->8--- Should we do something (host out own tarball?) to ensure both files can be mirrored concurrently? -- Best Regards Edd Barrett http://www.theunixzoo.co.uk
