Package Details: vdirsyncer-git 0.18.1.dev130+g8557c6e-1

Git Clone URL: (read-only, click to copy)
Package Base: vdirsyncer-git
Description: Synchronize CalDAV and CardDAV.
Upstream URL:
Licenses: BSD
Conflicts: vdirsyncer
Provides: vdirsyncer
Submitter: eolianoe
Maintainer: whynothugo (untitaker)
Last Packager: whynothugo
Votes: 7
Popularity: 0.009663
First Submitted: 2016-04-09 11:50 (UTC)
Last Updated: 2022-05-04 08:44 (UTC)

Latest Comments

dbermond commented on 2021-07-19 17:52 (UTC)

@whynothugo Please add python-pytest-cov to checkdepends. Package fails to pass the checks without python-pytest-cov, giving the error described by @dreieck on his comment from 2020-12-20.

serxxx commented on 2021-06-01 22:17 (UTC)

This is probably PEBCAK, but yay tries to upgrade this package every time, and has done for several months regardless of whether the project has changed. It thinks what's installed is, and that the current package version is 0.17.yyy, and so it thinks it is out of date. I suspect that the "v" in the version that gets installed is significant to the behavior. This behavior remains after uninstall/install, and clean building -- yay -Syu always rebuilds this package.

If I haven't done something wrong on my end, then aside from pinning or ignoring is there a way to fix this?

stweller commented on 2021-01-09 10:18 (UTC)

This needs to depend on python-pytest-cov. If this is installed, the check failure described by @dreieck will be resolved.

dreieck commented on 2020-12-20 13:12 (UTC)

Fails to check() for me:

==> Starting check()...
ERROR: usage: py.test [options] [file_or_dir] [file_or_dir] [...]
py.test: error: unrecognized arguments: --cov-config --cov=vdirsyncer --cov-report=term-missing --no-cov-on-fail
  inifile: [...]/aur-vdirsyncer-git/src/vdirsyncer/setup.cfg
  rootdir: [...]/aur-vdirsyncer-git/src/vdirsyncer

make: *** [Makefile:57: test] Error 4
==> ERROR: A failure occurred in check().

Thanks for maintaining!

friday13 commented on 2020-02-02 20:08 (UTC) (edited on 2020-02-02 21:02 (UTC) by friday13)

error[E0713]: borrow may still be in use when destructor runs
   --> /home/friday13/.cargo/registry/src/
259 | impl<'a> Target for ::UrlQuery<'a> {
    |      -- lifetime `'a` defined here
260 |     fn as_mut_string(&mut self) -> &mut String { &mut self.url.serialization }
261 |     fn finish(self) -> &'a mut ::Url { self.url }
    |                                        ^^^^^^^^ - here, drop of `self` needs exclusive access to `*self.url`, because the type `UrlQuery<'_>` implements the `Drop` trait
    |                                        |
    |                                        returning this value requires that `*self.url` is borrowed for `'a`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0713`.
error: could not compile `url`.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
Error making: vdirsyncer-git

untitaker commented on 2018-06-13 16:12 (UTC)

I pushed something to the vdirsyncer repository, please try again.

mehalter commented on 2018-06-13 15:23 (UTC)

I am getting pkg_resources.DistributionNotFound: The 'click-log<0.3.0,>=0.2.0' distribution was not found and is required by vdirsyncer. Seems that click-log is at version 0.3.2 as installed from the community repo and vdirsyncer requires < 0.3.0

untitaker commented on 2018-06-13 13:52 (UTC)

@Rhinoceros: thanks, I think I fixed it

Rhinoceros commented on 2018-06-13 01:33 (UTC)

vdirsyncer sync is failing for me with pkg_resources.DistributionNotFound: The 'shippai>=0.2.3' distribution was not found and is required by vdirsyncer. I can't seem to find this in any package.

untitaker commented on 2018-01-14 12:25 (UTC)

It is definetly not a runtime dependency. If you experience the same issue as @hnicke, make sure you have the latest versions of setuptools, pip and Python.

Rhinoceros commented on 2018-01-10 03:15 (UTC)

@hnicke Odd, vdirsyncer discover works fine for me without milksnake.

hnicke commented on 2018-01-09 23:57 (UTC)

python-milksnake must be a dependency, not a build-dependency. After installation i stripped unneeded packages with 'yaourt -Qtd', executed 'vdirsyncer discover' and got:

pkg_resources.DistributionNotFound: The 'milksnake' distribution was not found and is required by vdirsyncer

whynothugo commented on 2018-01-03 16:54 (UTC)

python-milksnake is a build dependency only, AFAIK (makedepends).

Rhinoceros commented on 2018-01-01 22:36 (UTC)

@stitran this package works fine for me without python-milksnake installed.

stitran commented on 2018-01-01 17:28 (UTC)

Missing dependency: python-milksnake

whynothugo commented on 2017-10-23 14:07 (UTC)

Also note: now packages are architecture-specific.

whynothugo commented on 2017-10-23 14:05 (UTC)

Yup, they're new dependencies (both provided by the `rust` package). Updated.

stevenroose commented on 2017-10-23 10:06 (UTC)

Fails to build with following message /bin/sh: cargo: command not found It seems to need rust and cargo in order to build...

whynothugo commented on 2017-09-02 22:59 (UTC)

Updated. Note that you're a maintainer too though.

whynothugo commented on 2017-09-02 22:59 (UTC)

Updated. Note that you're a maintainer too though.

untitaker commented on 2017-09-02 20:57 (UTC)

Vdirsyncer is licensed under the 3-clause BSD, please change that.

Rhinoceros commented on 2017-04-28 03:54 (UTC)

As per vdirsyncer, building with python-urllib3-1.21-1 fails, and downgrading to python-urllib3-1.20-1 fixes it. Issue filed here:

eolianoe commented on 2016-11-25 09:47 (UTC)

@swalladge: I cannot reproduce your error on a clean chroot. Do you have any special configurations? Could you send me or paste somewhere your full build log?

swalladge commented on 2016-11-25 09:23 (UTC)

I'm getting the following error trying to build the package now: --- Running Sphinx v1.4.8 Error during import: No module named 'urlparse' If you have installed vdirsyncer from a distro package, please file a bug against that package, not vdirsyncer. Consult on how to work around this.

eolianoe commented on 2015-04-14 12:18 (UTC)

Updated by renaming the binary and the man page. I didn't have time to investigate the check function without all the check dependencies.

whynothugo commented on 2015-04-14 08:04 (UTC)

Please either install /usr/bin/vdirsyncer as /usr/bin/vdirsyncer2, or add conflicts=vdirsyncer. (I'd prefer the former).

eolianoe commented on 2015-02-22 22:03 (UTC)


untitaker commented on 2015-02-22 22:01 (UTC)

E.g. it's convention to name the changelog either CHANGES, CHANGELOG or NEWS. Is there a similar thing for packaging-related instructions?

eolianoe commented on 2015-02-22 21:57 (UTC)

Ok, I will try to have a look at virtualenv and pip to manage to install the packages needed for tests locally somewhere in ${srcdir}. Sorry, but I did not understand well your question. What are you looking for?

untitaker commented on 2015-02-22 17:43 (UTC)

BTW is there some sort of convention where to store information for package maintainers? Like, a particular filename in the repo root?

untitaker commented on 2015-02-22 17:39 (UTC)

See I wouldn't recommend running the stylechecker though, the errors it reports are not the kind of stuff that should prevent the user from using vdirsyncer.

eolianoe commented on 2015-02-22 17:36 (UTC)

@untitaker: that sounds like a good idea, but how pratically implement this solution? For now it seems that `make test` runs only the test and does not install the package needed for the tests.

untitaker commented on 2015-02-22 10:52 (UTC)

Late to the party, but regarding ``check``, wouldn't it be easier if you create a virtualenv and let pip install the dependencies?

eolianoe commented on 2014-09-23 19:38 (UTC)

@hobarrera: I'm trying to follow as much as possible the GitHub repo, and rebuild regularly the package. I'm ok the add a check function, but I think it's some superfluous dependencies (especially in this case because there is more checkdepends than dependencies ^^). (the same thing apply for your comment at

whynothugo commented on 2014-09-23 15:01 (UTC)

You should check the package in your PKGBUILD, especially since -git packages have higher chances of breaking:

whynothugo commented on 2014-09-23 15:00 (UTC)

You should check the package in your PKGBUILD, especially since -git packages have higher chances of breaking: