Package Details: python2-kivy-git 1.10.0.r8.gb36ddd52e-1

Git Clone URL: (read-only)
Package Base: python-kivy-git
Description: A software library for rapid development of hardware-accelerated multitouch applications.
Upstream URL:
Licenses: MIT
Conflicts: python2-kivy
Provides: python2-kivy
Submitter: haagch
Maintainer: None
Last Packager: NicoHood
Votes: 18
Popularity: 0.000000
First Submitted: 2015-06-16 15:50
Last Updated: 2017-05-09 11:58

Required by (6)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

cTas0099 commented on 2018-04-25 10:07

kivy: WARNING: [AudioGstplayer] b"No decoder available for type 'audio/ogg'." kivy: ERROR: [AudioGstplayer] b'Your GStreamer installation is missing a plug-in.'


FAILED (errors=10, failures=9) XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":99" after 15 requests (13 known processed) with 0 events remaining. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":99" after 10 requests (7 known processed) with 0 events remaining. ==> ERROR: A failure occurred in check(). Aborting...

Hello, why do these errors appear?

NicoHood commented on 2017-04-25 20:43

@mixedcase this should fix you problems, doesnt it? I cannot see any other difference in the package that would cause any trouble.

package_python2-kivy-git() {
depends=('sdl2_image' 'sdl2_mixer' 'sdl2_ttf' 'cython2-kivy' 'mtdev')
optdepends=('python2-twisted: networking framework integration')

mixedCase commented on 2017-04-25 20:22

Can you remove me as a co-maintainer?

mixedCase commented on 2017-04-25 20:03

I'm sorry but no, I'm done with the package.

If I were you I'd start checking wether buildozer even builds with the new package and that the final build actually contains python 2 code and interpreter rather than a mix and match or just python 3. And set-up some automated CI to warn you about the eventual cython2 breakage.

NicoHood commented on 2017-04-25 19:57

@mixedcase could you integrate the python2 specific parts into this PKGBUILD?

mixedCase commented on 2017-04-25 19:49

I'm abandoning the package. NicoHood, you made a merge without knowing the full consequences of what it breaks, despite my objections nor caring about users who don't want to build both versions (which take a *ridiculous* amount of time to build).

Additionally, you tied the package to an unsupported version of Cython for your convenience despite the breakage this has caused in the past (which is why cython2-kivy was created).

Long story short, if you are do this as a trusted user then it's your mess, and I want no part of it.

PS: The package collides with all sort of shit in my system, so there's not even a clean upgrade path.

mixedCase commented on 2016-12-22 07:37

That's not the way *we* provide PKGBUILDs; that's how the main repos do it because they distribute binaries while we distribute the PKGBUILD for end-user consumption.

Long story short, I don't think they should be merged. However, I'm completely open to sharing all common code, and it's probably better to base off the official one.

NicoHood commented on 2016-12-22 07:23

You might be right, but that is the way we provide PKGBUILDs, as it gives a simpler maintenance and a better quality PKGBUILD.

Your package still differs a lot from the official one (or my git version), so can we somehow merge them? Is the one I used okay like that?

mixedCase commented on 2016-12-21 16:35

When I pull a package I don't want to build both if I want a single one. It may work for the official repo but in the AUR it's a nuisance for end-users.

I'll add the protocol change, good one.

NicoHood commented on 2016-12-21 10:16

@mixedCase Sorry forgot to enable notifications.

My package builds the python2 and python3 version of the package the same way. However I do not understand what you mean with inconsistent? A PKGBUILD that can build 2+3 is always better than split PKGBUILDs (except if the build process differs).

Is there anything that you'd change in my PKGBUILD? Otherwise I'd upload it and merge it with your AUR package. I can add you as maintainer if you wish.

From Felix Yan:
The locale change should be needed due to some build-time assumptions
(like UTF-8 characters in path, files to open, etc) and is a common
workaround among my other python packages, too. I may not have examined
the need of it on minor bumps, though.

Please also use git+https://