Package Details: mypaint-git 1.2.0.r33.g713d0be-1

Git Clone URL: (read-only)
Package Base: mypaint-git
Description: A fast and easy painting application for digital painters, with brush dynamics
Upstream URL:
Licenses: GPL
Conflicts: libmypaint-git, mypaint
Provides: libmypaint-git, mypaint
Submitter: jonnor
Maintainer: ShadowKyogre
Last Packager: ShadowKyogre
Votes: 21
Popularity: 0.936499
First Submitted: 2009-06-08 17:08
Last Updated: 2016-02-05 19:21

Latest Comments

ShadowKyogre commented on 2016-04-13 22:38

Found out the reason. That tag is not made on master.


I'm not going to point this at the testing cycle branch every time there's a new beta. It's too version dependent.

ShadowKyogre commented on 2016-04-13 22:13

To whoever's flagging this out of date: I just need to put it out there that the pkgver is stubborn atm. It's not reading the latest tag since it's beta flagged :|. Give me a while to wrestle with this thing.

vrav commented on 2016-01-09 05:34

This is great, thank you. Note that their website has changed to (503 error at

ShadowKyogre commented on 2016-01-07 23:41

Updated the pkgver() function to better reflect that it's being built against the beta version by also checking unannotated tags. The last annotated tag was 1.1.0, while the latest unannotated tag is 1.2.0-beta.4.

This must've been confusing for the people who thought this was out of date (even though I regularly test mypaint using this PKGBUILD).

ShadowKyogre commented on 2015-12-28 06:36

Updated the package to provide libmypaint-git

This is so gimp-git can live side-by-side with mypaint-git. Also, there's a fix for the current build (it breaks without the The issue regarding will need to be reported upstream later.

tcuc commented on 2015-07-29 08:47

just ran it right from the /usr/bin dir. since there all symlinked to there.
so if anyone else has the same problem typing:
in a terminal should fire it right up! ;)

tcuc commented on 2015-07-29 08:27

@ShadowKyogre, i tried posting this as an issue on the main git repo and i think they have found the issue. but it's a bit over my head. :P

here's the issue link:

ShadowKyogre commented on 2015-07-27 19:24

@tcuc: Why's mypaint in /usr/sbin?

Also, the during installation error, is that from the main AUR? That's due to the pkg-config files having references to $pkgdir for some reason. It's an error that definitely needs to be fixed upstream, but I can't pinpoint which part of the scons building is causing this.

tcuc commented on 2015-07-27 17:17

I cannot get Mypaint to run at all. not even the one from the main repo. all i get is this error when trying to start it:

Traceback (most recent call last):
File "/usr/sbin/mypaint", line 420, in <module>
= get_paths()
File "/usr/sbin/mypaint", line 186, in get_paths
raise RuntimeError("Unknown install type; could not determine paths")
RuntimeError: Unknown install type; could not determine paths

during installation i also get this:
==> WARNING: Package contains reference to $pkgdir

i cannot find out why.

ShadowKyogre commented on 2015-07-15 21:04

Adopted it on the AUR4 now.

All comments