Package Details: bugwarrior 1.8.0-1

Git Clone URL: https://aur.archlinux.org/bugwarrior.git (read-only, click to copy)
Package Base: bugwarrior
Description: pull issues from issue trackers into taskwarrior (GitHub, GitLab, Bitbucket, etc.)
Upstream URL: https://bugwarrior.readthedocs.io
Licenses: GPL3
Conflicts: bugwarrior-git
Submitter: wookietreiber
Maintainer: Arvedui
Last Packager: Arvedui
Votes: 9
Popularity: 0.000008
First Submitted: 2017-02-21 14:26 (UTC)
Last Updated: 2020-12-13 20:31 (UTC)

Dependencies (21)

Required by (1)

Sources (1)

Latest Comments

« First ‹ Previous 1 2

Foxboron commented on 2017-12-08 10:32 (UTC)

Instead of patching setup.py, we can tell setup.py to ignore any dependency checks.

  1. Not a problem
  2. Lets fix upstream
  3. That's what i always do

We are also not going to do horrible workarounds when it helps everyone if we just submit patches to upstream to solve the problem.

rvasilev commented on 2017-12-08 09:46 (UTC) (edited on 2017-12-08 09:50 (UTC) by rvasilev)

for upstream 1.5.1

the easiest way to do it is patching setup.py that comes with source and remove version pin for python2-future. check this out https://gist.github.com/rvasilev/d90e20c76e39821b9dd3a924d4703227

that's possible and package is even building, but it's not the best choice because

  1. part of dependencies in AUR is outdated, not maintained or not building out of the box (python2-taskw, python2-twiggy)
  2. author of bugwarrior is tracking dependencies on it's own, so some future change will brake the package because of AUR is more up- or outdated than bugwarrior requires
  3. maintainer of this AUR package should check and track upstream setup.py requirements every time upstream bump new version

so, we could go with less linux, but more pythonic way and step off of dependancy tracking and build self-contained python module in virtualenv. to do so, you may look https://gist.github.com/rvasilev/c86d9f4522d5375f12f22dd8718c9729

<deleted-account> commented on 2017-12-08 08:08 (UTC)

Besides waiting for https://github.com/ralphbean/bugwarrior/issues/427 to be solved, I think the more pragmatic way for us to workaround this issue on our side is to create a separate package named python2-future-0.15 (or whatever the version bugwarrior needs) and this package should conflict with the normal python2-future meanwhile, until the issue noted above is solved.

rvasilev commented on 2017-12-07 20:29 (UTC) (edited on 2017-12-07 20:30 (UTC) by rvasilev)

https://gist.github.com/rvasilev/c86d9f4522d5375f12f22dd8718c9729

PKGBUILD builds latest tagged 1.5.1 bugwarrior within isolated virtualenv. Bugwarrior will be self-contained with all non-system dependencies. That's the only way that not bothers about outdated arch-python packages.

wookietreiber commented on 2017-12-07 08:33 (UTC)

the real (and only) problem is getting in the old version of python2-future. see my older comment on how it works with virtualenv. I suppose you could depend on everything BUT python2-future and do the remaining python2-future/bugwarrior installation via virtualenv to /opt or something.

Foxboron commented on 2017-12-07 00:30 (UTC)

Helluw.

I just adopted this package. I'll get to work fixing it during the weekend!

thelinuxguy commented on 2017-12-06 23:34 (UTC)

Do you intend to continue maintaining this package? I am interested in using it myself, so I could take over.

wookietreiber commented on 2017-07-31 12:46 (UTC)

Can't update properly because bugwarrior wants an older python-future version than Arch currently ships. I recommend to install via virtualenv: pacman -S python2-virtualenv virtualenv2 ~/.apps/bugwarrior source ~/.apps/bugwarrior/bin/activate pip install bugwarrior Then you can use (without needing to activate the virtualenv) ~/.apps/bugwarrior/bin/bugwarrior-pull in your crontab or systemd-timers.

« First ‹ Previous 1 2