On 12/11/18 12:38 PM, Storm Dragon via aur-general wrote:
Howdy,
On Mon, Dec 10, 2018 at 12:21:19PM -0500, AUR General wrote:
Is taholafs not in the AUR? There are no AUR packages which depend on magic-wormhole, and I cannot find anything when searching for "taholafs".
I guess it would be helpful if I had spelled the package name correctly. :) It is tahoe-lafs-git.
Ouch. There's an AUR package for that but it hasn't been updated since 2015 and the most glaring issue is that it currently depends on "twisted" which was deprecated for "python2-twisted" a long time ago. Also yeah, it imports wormhole in the python code, and uses python2, so it should be updated to new versions of tahoe-lafs and in the process updated to depend on python2-magic-wormhole. If you're interested in this package, please request it to be orphaned, then fix it up.
I've written up an untested PKGBUILD that expresses what I believe you want. Note how I've fixed up the url and the two package names it provides, and installed the LICENSE file which you *must* install for MIT-licensed software.
Also note the addition of the testsuite, and the reliance on a dummy array _deps=() to track the twelve module dependencies, which are super annoying to enter four times over.
Thanks so much for this, I have learned a lot from it. It seems to work, but now I'm having trouble with another package, python2-humanize which, in part, says this:
make: Entering directory '/home/storm/.cache/yay/python2-humanize/src/humanize-0.5.1/docs' sphinx-build -b html -d _build/doctrees . _build/html make: sphinx-build: Command not found make: *** [Makefile:34: html] Error 127
This does not happen with the python3 version.
The python3 version is in the official repos. The Makefile that is being run over there unconditionally uses the command "sphinx-build" which is provided by python-sphinx, and the package needs to be updated to depend on that instead... or to stop using the Makefile, and invoke sphinx-build2 instead. *glares at foxlike maintainer*
I have heard that python2 is going to be completely deprecated after january. If that is true, will these packages have to be changed back to py3 only after then?
Python2 is not going away IMHO. There is too much code which still uses it. The Python Software Foundation may drop support for it, but I suspect other interest groups will pick up the torch... Either way, it is up to the maintainer whether to support python2 split builds. You might decide it is simply not worth it. -- Eli Schwartz Bug Wrangler and Trusted User