Package Details: todoman 3.0.1-1

Git Clone URL: https://aur.archlinux.org/todoman.git (read-only)
Package Base: todoman
Description: A simple CalDav-based todo manager.
Upstream URL: https://github.com/pimutils/todoman
Keywords: calendar icalendar tasks todo
Licenses: MIT
Submitter: hobarrera
Maintainer: hobarrera
Last Packager: hobarrera
Votes: 5
Popularity: 0.365911
First Submitted: 2015-03-30 17:28
Last Updated: 2017-03-27 12:50

Latest Comments

hobarrera commented on 2017-04-19 04:39

Package hasn't been updated to v3.1.0 because there's an installation error with it (already being worked on upstream).

dvzrv commented on 2017-04-02 17:05

@hobarrera: could you disable the tests in the meantime (they fail anyways)?
It's not too far off, that someone might have pyicu installed, when trying to build todoman

another commented on 2017-03-27 13:57

Test failed! Are you sure you want a 23 hour delta?

> assert todos['ccc'].due == todos['bbb'].due - datetime.timedelta(hours=23)
E AssertionError: assert FakeDatetime(2017, 3, 27, 17, 48, 14, tzinfo=tzlocal()) == (FakeDatetime(2017, 3, 28, 17, 48, 14, tzinfo=tzlocal()) - datetime.timedelta(0, 82800))
E + where FakeDatetime(2017, 3, 27, 17, 48, 14, tzinfo=tzlocal()) = <todoman.model.Todo object at 0x7fad45024a20>.due
E + and FakeDatetime(2017, 3, 28, 17, 48, 14, tzinfo=tzlocal()) = <todoman.model.Todo object at 0x7fad45024940>.due
E + and datetime.timedelta(0, 82800) = <class 'datetime.timedelta'>(hours=23)
E + where <class 'datetime.timedelta'> = datetime.timedelta

tests/test_cli.py:277: AssertionError

hobarrera commented on 2017-02-25 13:57

Having pyicu installed causes some failures in the test suite. This is a bug in a dependency used only for testing though, and should not affect real-life usage. We're already working on it.

dvzrv commented on 2017-02-25 03:52

The current build fails in check() for me, and I'm unable to guess what the problem is:
https://paste.sleepmap.de/view/ca911095#hpiMWHqeRRka49Go7SQmkWgia5jVOhQC

hobarrera commented on 2017-01-30 02:05

Updated, thanks!

milouse commented on 2017-01-27 19:31

Hi!

python-pytest-runner is also a checkdependancy.

hobarrera commented on 2016-11-07 17:20

check() should only take a few seconds anyway, and yes, you assume correctly, especially since I'm an upstream dev AND the packager.

I just confirmed that after uninstalling python-pytest, removing checkdepends and check() worked fine. Maybe you forgot to remove checkdepends?

Note that you can use `makepkg --nocheck` and avoid editig the PKGFILE after every update. ;)

milouse commented on 2016-11-07 08:37

@hobarrera it's very weird. I'm used to comment the check part. I'm (maybe wrongly) confident with upstream developper and packager and assume they've do their job, thus I comment the check part and its dependancies.

On one of my machines I then encounter a crash during the build phase, telling me my system lacks of python-pytest and python-pytest-runner (hence my previous message). But today, with the same PKGBUILD on another machine it build without problem.

Therefor you may ignore my messages for now, unless someone else encounter such a problem.

Cheers.

hobarrera commented on 2016-11-04 22:13

@milouse They should not be required when skipping checks, what made you think otherwise?

All comments