Arch Linux User Repository

@milouse yaourt works fine with AUR4 if you add this option: '--aur-url https://aur4.archlinux.org/'

@milouse
I haven't pushed it to AUR3, nope. I actually already uninstalled the tools I used for that already, and it'll get dropped completely in a few days, so there's really no big fuzz.

Sure, I can co-maintain this if you like. I follow upstream very closely, so it won't be an issue.

Warning, this package now build-depends on python-setuptools_scm, which is only available on aur4. If you manage your package with yaourt, you won't find it for now, resulting on a crash during install. Either install it manually from here https://aur4.archlinux.org/packages/python-setuptools_scm/ or wait for yaourt to support aur4.

Or maybe hobarrera you should put it on old-aur too ? Anyway, thank you very much for your help maintening this package :) In fact, do you want to take the management of this package ? As you already maintain vdirsyncer and now python-setuptools_scm, it could make sense. As you wish.

Also, because of the version number used upstream, this package comes back to a 0.5.x number, which is normal.

Also, because of the version number used upstream, this package comes back to a 0.5.x number, which is normal.

Warning, this package now build-depends on python-setuptools_scm, which is only available on aur4. If you manage your package with yaourt, you won't find it for now, resulting on a crash during install. Either install it manually from here https://aur4.archlinux.org/packages/python-setuptools_scm/ or wait for yaourt to support aur4.

Or maybe hobarrera you should put it on old-aur too ?

Problem there... python-setuptools_scm does not seems to have been ported on aur4, thus the build crash. One of you have a copy of its old pkgbuild to quickly re-push it on aur4 ?

Here's a fully working PKGBUILD:

https://git.barrera.io/snippets/11

Also FYI vdirsyncer probably has the same problems.

Then build in pkgver() and don't in `build`?

I'm not sure which feature to request from setuptools-scm though. I think this works and is easy enough, but it should be documented better:

python -c 'import setuptools_scm; print(setuptools_scm.get_version())`

@untitaker Yeah, the thing is that pkgver is run *before* building, so that would require double-building. :(

I agree with the feature request for setuptools-scm. :)

I've noticed that make man is failing for me now too, but I'll get back to you when I find out what the cause is.