Package Details: khal-git 0.9.6.dev2+g119d44c-1

Git Clone URL: (read-only)
Package Base: khal-git
Description: Command line CalDav client
Upstream URL:
Licenses: MIT
Conflicts: khal
Provides: khal
Submitter: milouse
Maintainer: WhyNotHugo
Last Packager: WhyNotHugo
Votes: 28
Popularity: 0.000047
First Submitted: 2013-12-11 19:24
Last Updated: 2017-05-04 23:20

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

WhyNotHugo commented on 2015-03-13 13:39

Also, python2-setproctitle should be an optdepends.

> It was a dependancy of python2-vdirsyncer but they drop it. I re-introduce it here. I don't have seen it as python2-icalendar was already installed for me.

Uninstalling unused dependencies would have revealed that eventually. You do clean up orphans, right?

milouse commented on 2015-03-13 13:31

It was a dependancy of python2-vdirsyncer but they drop it. I re-introduce it here. I don't have seen it as python2-icalendar was already installed for me.


WhyNotHugo commented on 2015-03-13 12:54

Depends python2-icalendar is missing:

$ khal
Traceback (most recent call last):
File "/usr/bin/khal", line 5, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/site-packages/pkg_resources/", line 3020, in <module>
working_set = WorkingSet._build_master()
File "/usr/lib/python2.7/site-packages/pkg_resources/", line 614, in _build_master
File "/usr/lib/python2.7/site-packages/pkg_resources/", line 920, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python2.7/site-packages/pkg_resources/", line 807, in resolve
raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: icalendar

eolianoe commented on 2014-10-23 07:03

python2-requests is still include in the dependency with python-vdirsyncer -> python2-requests-toolbelt -> python2-requests.
I'm not sure it's needed for khal, but vdirsyncer need it.

Runiq commented on 2014-10-23 07:02

Ah, right, I forgot that vdirsyncer provides some things as well. I'm doing it differently with my own packages, but I can see why one would do it like that.

Carry on, then! :)

milouse commented on 2014-10-22 20:19

Ok, I've cleanup a bit dependanies: I now follow the order of the file. It is easier to know where we are as this.

For information, I do not include python2-click and python2-icalendar as dependancies as they come with python2-vdirsyncer, nor I include python2-pytz, as it comes with python2-icalendar.

Finally, be careful that I've drop dependancies on python2-requests and python2-certifi too, as they don't seem to be mandatory any more. If you experience some crash, do not hesitate to notify me. Thanks.

Runiq commented on 2014-10-22 19:09

Just as an FYI, 0.4.0 (and therefore this package as well) will no longer depend on python2-docopt, but it will depend on python2-click:

eolianoe commented on 2014-10-14 19:00

@milouse: IHMO optional dependencies provide only some additional informations. It's certainly true that someone that doesn't know zsh will install it, but for zsh users they can see that there is auto-completion for this app.

In all cases you are the maintainer, and it's just optional stuff :)

milouse commented on 2014-10-14 10:00

I'm not sure it's really an optional dependancies. As pointed by @david.runge, if you don't use zsh, you don't really care about it. And if you use it, you already have it. At no point having zsh or not will break things.

On the other hand, just this package cannot be viewed as a starting point to install zsh. IMHO optionnal dependancies must be viewed as tips like « Hey! you really must try this other stuff, it's great. »

But I'd be happy to listen your arguments about it :)

eolianoe commented on 2014-10-14 07:01

@milouse: with those changes could you re-add the line optdepends=('zsh') ?