Package Details: krita-git 5.3.0.prealpha.2258.g83bdc0dc5f-1

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: GPL-3.0-only
Conflicts: calligra-krita, krita, krita-il10n
Provides: krita
Submitter: sl1pkn07
Maintainer: AlfredoRamos
Last Packager: AlfredoRamos
Votes: 17
Popularity: 0.47
First Submitted: 2015-10-11 13:38 (UTC)
Last Updated: 2025-01-05 20:31 (UTC)

Dependencies (65)

Required by (4)

Sources (1)

Latest Comments

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

AlfredoRamos commented on 2022-06-16 15:13 (UTC)

@zlfn: Nightly builds and builds from source are two different things.

In my opinion krita-next-git should be deleted, since it's the same as this package (krita-git), does not differ from this build in any way (different features, patches, etc.), and this one follows the naming convention guidelines.

https://wiki.archlinux.org/title/VCS_package_guidelines#Guidelines

However that's a decision a TU should make.

zlfn commented on 2022-06-16 00:49 (UTC) (edited on 2022-06-16 00:49 (UTC) by zlfn)

I have something to discuss.
Krita's pre alpha build is split into two branches.
Krita-Plus with only new bug fixes and
Krita-Next with new features.

Krita-Plus is based on the krita/5.1 branch of the krita repository.
Krita-Next is based on the master branch.
These are built daily by Jenkins and distributed in .appimage format.

I uploaded two VCS packages based on two different branches to use them in Arch. (krita-plus-git, krita-next-git)

And I just noticed that the content provided by krita-git and the content provided by krita-next-git are exactly the same.

I think these two should be merged. Can one package have two names? Or is there a naming convention to use in this case?
I would like to keep the krita-next naming if possible.

zlfn commented on 2022-06-16 00:06 (UTC)

@AlfredoRamos: Sorry, I didn't know.

AlfredoRamos commented on 2022-06-15 22:36 (UTC)

@zlfn: The package is not outdated as it always builds the latest available version from source.

So unless the package is missing a dependency or the build fails, please refrain to marking the package as out-of-date.

Read the note about VCS packages in the wiki:

https://wiki.archlinux.org/title/Arch_User_Repository#Flagging_packages_out-of-date

I've unflagged it as out-of-date as it builds the latest version perfectly fine as of today.

vladafirefly commented on 2021-12-23 11:26 (UTC)

Starting from version 5, developers have included their own gmic plugin build with Krita itself. I am no sure what's the reason, but I guess it has something to do with the fact that macOS can't share so much memory between different processes. Anyhow, the problem I'm seeing is - there is no gmic in this version.

Thanks for your support and time.

AlfredoRamos commented on 2021-10-25 21:13 (UTC)

@carlosnewmusic I cannot reproduce that issue.

I built it in a clean chroot and I discovered that some dependencies were missing, but nothing related to openexr (your issue) in any way.

Make sure your mirrors are up to date, and upgrade your system first.

carlosnewmusic commented on 2021-10-25 13:21 (UTC)

build error https://pastebin.com/rVVjNgGT

arojas commented on 2021-10-23 17:56 (UTC)

krita supports opencolorio 2 now in master, please switch the dependency

AlfredoRamos commented on 2021-06-25 21:37 (UTC)

Thanks for the report.

I've fixed the package and now it must build without problems.

sodaplayer commented on 2021-06-22 18:16 (UTC) (edited on 2021-06-22 18:17 (UTC) by sodaplayer)

If you've been having trouble building this lately, it's because OpenColorIO is now on version 2 and has had API changes. There's now an explicit package for OpenColorIO version 1.

The main Krita package has a patch to handle this change in the CMake files which you can apply.

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