Package Details: krita-git 4.3.0.prealpha.7876.g8e7ccd3cd7-2

Git Clone URL: (read-only, click to copy)
Package Base: krita-git
Description: A full-featured free digital painting studio. Git version.
Upstream URL:
Keywords: qt5
Licenses: GPL3
Conflicts: calligra-krita, krita, krita-il10n
Provides: krita=4.3.0.prealpha.7876.g8e7ccd3cd7
Submitter: sl1pkn07
Maintainer: AlfredoRamos
Last Packager: AlfredoRamos
Votes: 16
Popularity: 0.090645
First Submitted: 2015-10-11 13:38
Last Updated: 2021-10-23 19:11

Dependencies (38)

Required by (1)

Sources (1)

Latest Comments

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

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.

Archange 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

Archange 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).

haawda commented on 2016-08-02 16:14

So take the mails as opportunity to rebuild the package because of upstream changes. Because, that's what the bot does: updating whenever upstream changes something.

codl commented on 2016-08-02 08:06

> Unsubscribe, if you do not want mails.

I do want emails, but only about meaningful updates to the package, updates that will require me to re-download the PKGBUILD

haawda commented on 2016-08-02 05:54

No, this would destroy my workflow. Unsubscribe, if you do not want mails.

codl commented on 2016-07-31 12:07

haawda, could you disable your version update bot? I subscribed to package notifications to know when there is a significant change, but now I get an email every day for this package, and the only change is the version number. It's quite noisy ;)

Archange commented on 2016-05-22 12:51

Oh, I see. flag, not frag.

AppImage files are not to be packaged. It’s not something you install on your system. And there is no advantage versus a distro package if that one exists and is maintained. ;)

sl1pkn07 commented on 2016-05-22 12:42

I removing the frag outdate of date just now

Your package krita-git [1] has been flagged out-of-date by Myrik [2]:

now krita use .appimage file

Nothing to do