Package Details: bugwarrior 1.8.0-1

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

Required by (0)

Sources (1)

Latest Comments

Arvedui commented on 2020-04-13 08:54 (UTC)

Yes, of course. Thank your for bringing this to my attention!

I added other optdepends as well, some are still missing because they are not packaged at all for arch right now. I made a todo item to fix that.

tjaart commented on 2020-04-13 01:13 (UTC)

I think this package should optionally depend on python-jira for jira support

rvasilev commented on 2017-12-10 08:47 (UTC)

wrong sha256sum.

should be ab03c3872e8f27f954b60bb6ff4f0646a2b7e2a7fb9c12116a90cdc297b4b34f

Foxboron commented on 2017-12-09 23:31 (UTC) (edited on 2017-12-09 23:32 (UTC) by Foxboron)

Yes, I saw it now :p Missed that one.

Pushed and should be without errors. Please feel free to yell if you spot anything.

rvasilev commented on 2017-12-09 16:43 (UTC) (edited on 2017-12-09 17:02 (UTC) by rvasilev)

The second package() should be install()?

... My bad. The 1st package() should be build()

Foxboron commented on 2017-12-09 15:01 (UTC)

Something strange with the when utilizing python3, the egg-info is inserted but the module is missing.

Don't have time to investigate this today, so incase anyone else wants to take a look:

pkgdesc="pull issues from issue trackers into taskwarrior (GitHub, GitLab, Bitbucket, etc.)"
depends=('python' 'python-setuptools'
         'python-requests' 'python-taskw'
         'python-dateutil' 'python-pytz'
         'python-six' 'python-jinja'
         'python-dogpile.cache' 'python-lockfile'
         'python-click' 'python-future')

  cd "$srcdir/$pkgname-$pkgver"
  sed -i -e 's/!=0.16.0//g'

package() {
  cd "$srcdir/$pkgname-$pkgver"
  python build

package() {
  cd "$srcdir/$pkgname-$pkgver"
  python install --root="$pkgdir/" --optimize=1 --skip-build
λ fox@theia pkg » λ git master* → tree
└── bugwarrior
    └── usr
        ├── bin
        │   ├── bugwarrior-pull
        │   ├── bugwarrior-uda
        │   └── bugwarrior-vault
        └── lib
            └── python3.6
                └── site-packages
                    └── bugwarrior-1.5.1-py3.6.egg-info
                        ├── dependency_links.txt
                        ├── entry_points.txt
                        ├── not-zip-safe
                        ├── PKG-INFO
                        ├── requires.txt
                        ├── SOURCES.txt
                        └── top_level.txt

7 directories, 10 files
λ fox@theia pkg » λ git master* → bugwarrior-pull 
Traceback (most recent call last):
  File "/usr/bin/bugwarrior-pull", line 11, in <module>
    load_entry_point('bugwarrior==1.5.1', 'console_scripts', 'bugwarrior-pull')()
  File "/usr/lib/python3.6/site-packages/pkg_resources/", line 572, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3.6/site-packages/pkg_resources/", line 2752, in load_entry_point
    return ep.load()
  File "/usr/lib/python3.6/site-packages/pkg_resources/", line 2405, in load
    return self.resolve()
  File "/usr/lib/python3.6/site-packages/pkg_resources/", line 2411, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
ModuleNotFoundError: No module named 'bugwarrior'

rvasilev commented on 2017-12-08 12:40 (UTC)

omitting dependency check is also a workaround with potential to brake the build.

even python3 install --optimize=1 is installing future-0.15. is it a bug or a feature?

so, you as maintainer can do both - make it up to date and working, or leave it broken and wait until all upstreams/AUR dependencies will be fixed

just for reference

pkgdesc="pull issues from issue trackers into taskwarrior (GitHub, GitLab, Bitbucket, etc.)"
#depends=('python2-bugzilla' 'python2-click' 'python2-dateutil' 'python2-dogpile.cache' 'python2-future' 'python2-keyring' 'python2-lockfile' 'python2-offtrac' 'python2-pytz' 'python2-requests' 'python2-twiggy' 'python2-xdg' 'python2-configparser' 'python2-jinja')
depends=('python3' 'python-virtualenv')


#        "setup.patch")

#prepare() {
# cd ${srcdir}/${pkgname}-${pkgver}

# patch ${srcdir}/setup.patch  

package() {
    cd ${srcdir}/${pkgname}-${pkgver}

    virtualenv ${pkgdir}/opt/${pkgname}
    ${pkgdir}/opt/${pkgname}/bin/python install --optimize=1
    sed -i "s|${pkgdir}/opt/$pkgname|/opt/${pkgname}|g" ${pkgdir}/opt/${pkgname}/bin/*

    python install --root="${pkgdir}" --optimize=1

#    install -d ${pkgdir}/usr/bin/
    ln -f -s /opt/${pkgname}/bin/${pkgname}-pull ${pkgdir}/usr/bin/${pkgname}-pull
    ln -f -s /opt/${pkgname}/bin/${pkgname}-vault ${pkgdir}/usr/bin/${pkgname}-vault
    ln -f -s /opt/${pkgname}/bin/${pkgname}-uda ${pkgdir}/usr/bin/${pkgname}-uda

#         'eab141c2d22f46b5cf242fd7c5046ac9')

Foxboron commented on 2017-12-08 11:38 (UTC)

If you read what i wrote you'd realize that dependency check can be omitted. The bug that happens with future is a python2 regression.

taskw will be fixed whenever I accept the orphan request.

rvasilev commented on 2017-12-08 11:34 (UTC) (edited on 2017-12-08 11:39 (UTC) by rvasilev)

not everything is solved with python3

even if upstream will be fixed, it will not 'just build' with AUR dependencies as of now.

i see number of options, choose one of them:

1 Ideal linux-way with python3:

2 Ideal linux-way with python2:

3 My linux-way with python2:

  • patch to unpin version from python2-future
  • fix python2-taskw

4 My python2-3 way:

  • build upstream with no system/AUR dependencies and patching

the last one is the fastest and more future proof until all the fixes will be accepted to upstream/AUR. and it will just work.

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

Looking at this, it's only a python2 problem. Everything is solved by migrating to python3.

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

Instead of patching, we can tell 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 that comes with source and remove version pin for python2-future. check this out

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 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

commented on 2017-12-08 08:08 (UTC)

Besides waiting for 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)

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)


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.