Package Details: python-gitpython 2.1.3-9

Git Clone URL: https://aur.archlinux.org/python-gitpython.git (read-only)
Package Base: python-gitpython
Description: Python Git Library
Upstream URL: https://pypi.python.org/pypi/GitPython
Licenses: BSD
Provides: python-gitpython
Submitter: sanerb
Maintainer: sanerb
Last Packager: sanerb
Votes: 29
Popularity: 0.193736
First Submitted: 2017-02-13 14:50
Last Updated: 2017-03-20 18:40

Latest Comments

sanerb commented on 2017-06-13 18:20

@nicohood -

<3<3<3 i was literally just about to push 2.1.4. i guess that'd be pointless now, wouldn't it? (as a heads-up, no change to build process necessary.)

thanks so much! i love it when my packages get promoted!

NicoHood commented on 2017-06-13 18:09

gitdb, smmap and gitpython is now in [community]. Please test and report back bugs/issues. I will delete this AUR package within the next two weeks if no issues are reported. Thanks :)

tidux commented on 2017-05-08 19:05

GitPython-2.1.3.tar.gz ... FAILED (unknown public key 8C004C2F93481F6B)

terminalmage commented on 2017-03-20 20:13

Yeah. The reasoning makes sense when you think about it though. The main usage of multiple packages outside of PY2/PY3 split packages is for single projects that create multiple packages, in which the build process happens once and then the package_pkgname() funcs put the files in their proper places for the subpackages defined in "pkgname". So since the build process happens once, there is no call for multiple makedepends.

It just wasn't really documented properly. But the documentation has been improved now, so at least something positive came out of all the confusion, if you're looking for a silver lining here. :)

sanerb commented on 2017-03-20 18:41

@terminalmage (sigh) thanks. that's so stupid. this is why i prefer to create standalone python vs. python2 packages- split packaging is just so fucking broken, but someone requested i create a split package for this.

anyways, fixed.

terminalmage commented on 2017-03-20 18:17

@sanerb Confirmed, makedepends are global. I've updated the Arch Wiki.

terminalmage commented on 2017-03-20 17:44

@sanerb I've opened https://bugs.archlinux.org/task/53387 to inquire about the makedepends issue.

terminalmage commented on 2017-03-20 17:30

@sanerb still failing, it appears that the makedepends aren't processed when specified inside the "package-pkgname" functions, I had to specify them globally to get it to build. Perhaps this should be considered a bug in makepkg? I don't see any clarifying information saying that they must be specified globally in the wiki: https://wiki.archlinux.org/index.php/PKGBUILD#makedepends

sanerb commented on 2017-03-16 16:06

@terminalmage fixed

terminalmage commented on 2017-03-16 15:50

This won't build for me using makechrootpkg without adding a makedepends:

makedepends=('python' 'python2' 'python-setuptools' 'python2-setuptools')

All comments