Notice: Undefined variable: name in /srv/http/vhosts/ on line 248

Package Details: krita-git

Git Clone URL: (read-only)
Package Base: krita-git
Description: A free digital painting application. Digital Painting, Creative Freedom! (GIT Version)
Upstream URL:
Licenses: GPL2
Conflicts: calligra-krita, krita
Provides: calligra-krita, krita
Submitter: sl1pkn07
Maintainer: haawda
Last Packager: haawda
Votes: 12
Popularity: 0.468261
First Submitted: 2015-10-11 13:38
Last Updated: 2017-02-03 20:01

Latest Comments

1 2 3 4 5 6 Next › Last »

haawda commented on 2017-01-30 22:39

An unclean build directory is very unlikely. Krita launches fine her, but I am on nouveau.

electricprism commented on 2017-01-30 09:37

Compiling created a binary that wasn't able to launch. #krita suggests this may be linked to a unclean build directory or something else, I'm on MESA with Intel HD, can anyone else confirm it's broken?

ArchangeGabriel commented on 2016-12-16 22:33

Well, I’ve switched to stable krita anyway, so will just unsuscribe from here. However, you might want to check your bot commit messages, they’re quite lenghty currently…

haawda commented on 2016-12-16 11:26

The bot builds the package before it pushes a new AUR commit. And if I do no push the changes next time it will fail because the local commit is ahead of the one in AUR.

Enought said.

ArchangeGabriel commented on 2016-12-15 21:47

@haawda: It’s been explicitely stated on the aur-general ML that there is no point in updating VCS packages just for the sake of updating. Also, you’ve never adressed my concerned regarding whether the bot actually tries to package it before pushing.

haawda commented on 2016-09-09 10:40

Bad advice, goldpaw. Simply rebuild krita.

haawda commented on 2016-08-27 20:36

The bot may be useless to you but not for me as a maintainer. But I stop maintaining this.

ArchangeGabriel commented on 2016-08-26 20:40

@haawda: This AUR bot is definitively useless. The only changes that need to be tracked and that matters are packaging ones (dependencies, build process), and that do require human intervention. I don’t know if the bot even try to package it, else it could even push a non-building version…

In the event it does actually try to build and report failure, then this is the only time when the package should be upgraded, not when the build succeed. The rest of time, we know we should rebuild krita daily if we want always the latest commit, but also have a choice to rebuild it only once per week if that’s what we want.

codl commented on 2016-08-25 13:38

goldpaw, you're missing the point. makepkg knows how to fetch the latest version and update the version number every time you build a -git package, there is no need for the PKGBUILD to be manually updated every time. I've been making nightly builds of krita-git from a months-old PKGBUILD for a while and it's been working out fine

I'll just disable notifications, upstream changes happen almost every day, several times a day on Krita so I don't see the point of getting notified

ArchangeGabriel commented on 2016-08-13 10:32

I think what codl means, and what -git should do IMO, is only update the package when there is a significant change, e.g. new or removed (make/opt)dependency or changed build process (i.e. changes that affecte something else that the pkgver).