Package Details: python-gogs-client 1.0.6-3

Git Clone URL: https://aur.archlinux.org/python-gogs-client.git (read-only, click to copy)
Package Base: python-gogs-client
Description: Python client for Gogs server
Upstream URL: https://github.com/unfoldingWord-dev/python-gogs-client
Licenses: MIT
Conflicts: python-gogs-client
Provides: python-gogs-client
Submitter: mracos
Maintainer: mracos
Last Packager: mracos
Votes: 0
Popularity: 0.000000
First Submitted: 2017-05-06 23:10 (UTC)
Last Updated: 2019-03-19 13:27 (UTC)

Latest Comments

1 2 Next › Last »

mracos commented on 2025-01-13 13:03 (UTC)

Hey @dreick, been out of the archway for a while but feel free to send a patch fixing it and I'll gladly apply!

dreieck commented on 2025-01-11 16:01 (UTC)

If possible, please remove the dependency on python-furure/ make the package working without python-future:

WARNING: python-future package is not compatible with Python 3.13

The python-future project was created in 2013 to attempt to save Python from the schism of version incompatibility that was threatening to tear apart the language (as Perl 6 contributed to the death of Perl).

That time is now past. Thanks to a huge porting effort across the Python community, Python 3 eventually thrived. Python 2 reached its end of life in 2020 and the python-future package should no longer be necessary. Use it to help with porting legacy code to Python 3 but don’t depend on it for new code.

If you use packages that depend on it, please contact maintainers and/or upstream of these packages and try to work out whether this dependency is really needed.

Regards and thanks for this package!

mracos commented on 2019-03-19 13:35 (UTC)

@SpotlightKid your solution worked! I already updated the PKGBUILD.

Thanks @sirl1on and @SpotlightKid <3

SpotlightKid commented on 2019-03-10 20:21 (UTC)

Ran into the error mentioned by @sirl1on as well. Fixed it by changing the last line in the package function to these two: 

local pyver=$(python -c 'import sys; print("{0}.{1}".format(*sys.version_info))')
rm -f "${pkgdir}/usr/lib/python${pyver}/site-packages/tests/__init__.py"

sirl1on commented on 2019-01-16 14:13 (UTC)

supposedly due to a new python version, the last package action (deleting the test) fails.

Quick fix is to change the python version in the PKGBUILD from 3.6 to 3.7 (or whatever is current).

Proper fix surely would be to dynamically infer the correct python version or use a wildcard shell expression.

mracos commented on 2018-05-28 01:19 (UTC)

done!

whynothugo commented on 2018-05-27 06:47 (UTC)

The easiest way would probably be to simply delete $pkgdir/usr/lib/python3.6/site-packages/tests/__init__.py as the last step in package().

That would result in the end package not including the file.

This has been reported upstream, FWIW.

mracos commented on 2018-05-27 06:23 (UTC)

And again, how do i do that? There is and option in the PKGBUILD manifest?

whynothugo commented on 2018-05-23 19:31 (UTC)

That file should simply not be installed. It's that simple :)

mracos commented on 2018-05-23 19:20 (UTC)

You know how to solve it? If not I'll look into it later :)

1 2 Next › Last »