Package Details: krita-git 5.3.0.prealpha.279.g8697e4bffc-2

Git Clone URL: https://aur.archlinux.org/krita-git.git (read-only, click to copy)
Package Base: krita-git
Description: A full-featured free digital painting studio. Git version.
Upstream URL: https://krita.org
Keywords: qt5
Licenses: GPL3
Conflicts: calligra-krita, krita, krita-il10n
Provides: krita
Submitter: sl1pkn07
Maintainer: AlfredoRamos
Last Packager: AlfredoRamos
Votes: 16
Popularity: 0.000001
First Submitted: 2015-10-11 13:38 (UTC)
Last Updated: 2023-12-30 06:07 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

Archange commented on 2016-12-16 22:33 (UTC)

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 (UTC)

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.

Archange commented on 2016-12-15 21:47 (UTC)

@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 (UTC)

Bad advice, goldpaw. Simply rebuild krita.

haawda commented on 2016-08-27 20:36 (UTC)

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

Archange commented on 2016-08-26 20:40 (UTC)

@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 (UTC)

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

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »