Package Details: krita-git 4.3.0.prealpha.7877.g6e8aab8fd8-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.81
First Submitted: 2015-10-11 13:38 (UTC)
Last Updated: 2021-10-25 21:07 (UTC)

Latest Comments

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.

AlfredoRamos commented on 2020-10-17 14:09 (UTC)

@pkr It will use the number of cores (simultaneous jobs) you have specified in MAKEFLAGS.

See Makepkg: Improving compile times.

pkr commented on 2020-10-17 11:38 (UTC)

Is this build running on one core? Because it takes ages to build. Any chance to crank up the cores used for building?

AlfredoRamos commented on 2020-07-27 15:06 (UTC)

@vladafirefly Thanks for the report.

The patch for PyQt5 with SIP5 is no longer needed since it was fixed upstream KDE/krita@c3cba34.

vladafirefly commented on 2020-07-27 12:02 (UTC)

The package stopped building for me. Here's the output:

==> Starting prepare()... patching file cmake/modules/FindPyQt5.py Hunk #1 succeeded at 2 with fuzz 2. Hunk #2 FAILED at 41. 1 out of 2 hunks FAILED -- saving rejects to file cmake/modules/FindPyQt5.py.rej ==> ERROR: A failure occurred in prepare(). Aborting... error making: krita-git

AlfredoRamos commented on 2020-05-03 21:49 (UTC)

Package adopted.

It uses the same patch from the package of krita [Extra] to fix the build for PyQt5 and SIP 5.

Werzi2001 commented on 2019-05-18 17:10 (UTC)

Does this build not support the python scripter? I can't find the option in the settings to enable it.

C0rn3j commented on 2018-12-12 10:13 (UTC)

Why is this tagged out of date? "4.0.0.prealpha.891.g1cfb64ab4b-1 is the current git version" makes no sense, as this package builds current 4.2.0 just fine.

Teteros commented on 2017-04-18 01:59 (UTC) (edited on 2017-04-18 02:03 (UTC) by Teteros)

You need to add python-pyqt5 to makedepends, as well as: -DPYQT_SIP_DIR_OVERRIDE=/usr/share/sip/PyQt5 to cmake options. eg: CXXFLAGS=' -std=c++11' cmake ../krita \ [...] -DBUILD_TESTING=OFF \ -DPYQT_SIP_DIR_OVERRIDE=/usr/share/sip/PyQt5 Needed since commit https://github.com/KDE/krita/commit/71631f90dc3b7636d29fd607c85c13cfe1987208 Autodetection of the path seems to not work so the cmake env var is needed for now, which is weird because the tests in src/krita/cmake/modules/FindPyQt5.py (and FindSIP.py) output the right path.

laichiaheng commented on 2017-04-11 07:23 (UTC)

[ 55%] Generating krita/sipkritapart0.cpp sip: Unable to find file "QtCore/QtCoremod.sip" make[2]: *** [plugins/extensions/pykrita/sip/CMakeFiles/python_module_PyKrita_krita.dir/build.make:64: plugins/extensions/pykrita/sip/krita/sipkritapart0.cpp] Error 1 make[2]: *** Deleting file 'plugins/extensions/pykrita/sip/krita/sipkritapart0.cpp' make[1]: *** [CMakeFiles/Makefile2:25820: plugins/extensions/pykrita/sip/CMakeFiles/python_module_PyKrita_krita.dir/all] Error 2 make: *** [Makefile:139: all] Error 2 ==> 錯誤: build() 遭遇失敗。 正在中止...

haawda commented on 2017-03-07 20:46 (UTC)

Ask upstream.

commented on 2017-03-06 18:58 (UTC)

I am on Gnome with Wayland, and my graphical tablet Wacom doesn't work with Krita. Where is the support of libinput with Kwin-Wayland ? Now i must use mypaint, but i prefer Krita.

haawda commented on 2017-01-30 22:39 (UTC)

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

electricprism commented on 2017-01-30 09:37 (UTC) (edited on 2017-01-30 09:37 (UTC) by electricprism)

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?

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

Archange commented on 2016-08-13 10:32 (UTC)

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

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

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

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

codl commented on 2016-07-31 12:07 (UTC)

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

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

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 https://krita.org/download/krita-desktop/ Nothing to do Greetings

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

@sl1pkn07: I think you’re not on the right package. ;)

sl1pkn07 commented on 2016-05-22 11:58 (UTC)

@Myrik you can elaborate you frag outdate? Greetings

gravymond commented on 2016-05-19 14:47 (UTC)

it seems that git://anongit.kde.org/krita.git has 404'd. what should i do?

Archange commented on 2016-05-03 08:58 (UTC)

Given that hooks have landed, you should remove the install file. ;)

sl1pkn07 commented on 2016-04-23 12:21 (UTC)

@codl done

codl commented on 2016-04-23 08:36 (UTC)

As of apr 22 (commit 080dd9bf) the version variables in CMakeLists.txt have been renamed from CALLIGRA_... to KRITA_... As a result, pkgver needs to be updated, here's a patch: https://gist.github.com/codl/88e406c8f51d7b708fd739b67a951e7a

UnintelGen commented on 2016-03-21 03:17 (UTC) (edited on 2016-04-09 19:09 (UTC) by UnintelGen)

Never mind as of 4/9... Must've been some weird issue with my system. It works now after I compiled.

codl commented on 2016-03-11 19:21 (UTC)

@StormEngineer Hooray! \o/

StormEngineer commented on 2016-03-11 18:16 (UTC) (edited on 2016-03-11 18:27 (UTC) by StormEngineer)

@codl It was fixed in Krita 3.0 Pre-Alpha upstream this morning. I am building manually form source and I had to use this same hack, but I just built fresh without it and it succeeded.

codl commented on 2016-03-03 21:14 (UTC)

A recent glibc update causes the build to fail with an error about isnan not being declared. I've reported this upstream, but until it's fixed a quick way to get it to build is to add this line to the prepare() function of the PKGBUILD: sed -i 's/if (!isnan(value))/if (!std::isnan(value))/' krita/libs/widgets/KoUnitDoubleSpinBox.cpp

Archange commented on 2016-02-17 10:14 (UTC)

Since kimageformats 5.19, for files are provided by this one that are also in krita-git: krita-git : /usr/lib/qt/plugins/imageformats/kimg_kra.so krita-git : /usr/lib/qt/plugins/imageformats/kimg_ora.so krita-git : /usr/share/kservices5/qimageioplugins/kra.desktop krita-git : /usr/share/kservices5/qimageioplugins/ora.desktop Maybe the PKGBUILD should remove those while waiting for upstream to do so.

codl commented on 2016-02-12 11:21 (UTC)

There is no longer a package called 'krita' in the repos, this should provide/conflict with 'calligra-krita' instead

neubauten84 commented on 2016-01-20 20:04 (UTC)

Ok!!!Now style is working!!!Breeze!!!

neubauten84 commented on 2015-12-17 22:03 (UTC)

Ok perfect..so we have to wait!! Thanks!!

sl1pkn07 commented on 2015-12-15 14:53 (UTC)

form IRC on #Krita channel [15:50:13] <sL1pKn07> Hi [15:50:26] <Wolthera> hi [15:51:09] <sL1pKn07> i have a little problem with krita builded from git. only get to use a fusion theme on plasma5 [15:51:24] <Wolthera> That's intentional [15:51:33] <Wolthera> we're halfway through porting [15:51:40] <sL1pKn07> but breeze is listed in available styles [15:52:03] <Wolthera> and we were afraid that we couldn't figure out whether something was a problem with breeze or with QT. [15:52:09] <Wolthera> or with krita [15:52:19] <Wolthera> I have to admit I wouldn't know. [15:52:48] <sL1pKn07> okis. no problem then

sl1pkn07 commented on 2015-12-15 14:33 (UTC)

oh, tnks for the info

greenmanalishi commented on 2015-12-15 12:51 (UTC)

Its fusion style in both screenshots (check the arrow style). It must be hardcoded. @sl1pkn07 that is the color scheme you are pointing to.

neubauten84 commented on 2015-12-10 22:54 (UTC)

Here it is: http://s17.postimg.org/j3rdifn3j/Screen.png As I can see is similar to yours but I'm pretty sure is fusion style!!

sl1pkn07 commented on 2015-12-09 22:51 (UTC)

you can show a screenshot of your krita? http://wstaw.org/m/2015/12/09/Screenshot_20151209_234947.png

neubauten84 commented on 2015-12-09 21:49 (UTC)

Tried everything..with or without oxygen-icons same problem.. Changing theme in qt5ct doesn't affect krita.. I don't know how to solve..

sl1pkn07 commented on 2015-12-08 14:27 (UTC)

mmm you try with qt5ct?

sl1pkn07 commented on 2015-12-08 14:19 (UTC)

Available styles: ("Breeze", "Oxygen", "Windows", "GTK+", "Fusion") I do not have it installed 'oxygen' package, but yes 'oxygen-icons' Available styles: ("Breeze", "Windows", "GTK+", "Fusion") when installing 'oxygen': Available styles: ("Breeze", "Oxygen", "Windows", "GTK+", "Fusion") I can switch between all styles But when I uninstall oxygen-icons: Available styles: ("Breeze", "Oxygen", "Windows", "GTK+", "Fusion") Style: QFusionStyle(0x2b5d290, name = "fusion") Icon theme "oxygen" not found. Icon theme "oxygen" not found. like your message

neubauten84 commented on 2015-12-08 13:56 (UTC)

I have a pure qt5 system and I don't want an oxygen style but a breeze one!! I tried to install krita-git 'cause it's qt5 based but if I can't set a qt5 theme..

sl1pkn07 commented on 2015-12-08 13:42 (UTC) (edited on 2015-12-08 13:42 (UTC) by sl1pkn07)

you have installed oxygen-icons?

neubauten84 commented on 2015-12-08 12:46 (UTC)

Tried but no changes..that's the messages running in terminal: QCoreApplication::applicationDirPath: Please instantiate the QApplication object first >>>>>>>>>>>>>>>>>>> THEMECHANGED <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Available styles: ("Breeze", "Oxygen", "Windows", "GTK+", "Fusion") Style: QFusionStyle(0x20a81b0, name = "fusion") Icon theme "oxygen" not found. Icon theme "oxygen" not found.

sl1pkn07 commented on 2015-12-07 14:11 (UTC)

Settings -> Themes(?)

neubauten84 commented on 2015-12-07 14:09 (UTC)

Hi there!! I have a problem on gui style..Krita starts with fusion theme and I can't set breeze one. How can I modify default gui style?? Tks.

greenmanalishi commented on 2015-11-28 19:11 (UTC)

Sorry my bad fixed it.

sl1pkn07 commented on 2015-11-28 13:39 (UTC)

try install extra-cmake-modules-git

greenmanalishi commented on 2015-11-28 12:05 (UTC)

Right now it fails with this error: CMake Error at CMakeLists.txt:13 (kde_enable_exceptions): Unknown CMake command "kde_enable_exceptions". I have extra-cmake-modules installed.

Archange commented on 2015-11-15 13:21 (UTC)

This package should conflicts and provides calligra-krita instead of krita, and also conflicts the following: calligra-extras, calligra-filters, calligra-libs, calligra-plugins. Thanks

sl1pkn07 commented on 2015-11-11 15:52 (UTC)

try now

anthillsocial commented on 2015-11-11 09:37 (UTC)

I think you need to add "kitemmodels" as a dependency.

sl1pkn07 commented on 2015-10-24 17:41 (UTC)

done

iamlixiao commented on 2015-10-18 14:33 (UTC)

Two problems were found when building: First, eigen should be included as a dependency. Second, krita seems to be lagging behind libkdcraw development, as it's referring to a header that no longer exists in that git package. Removing this dependency may be fine because it's only related to importing raw photos, a function rarely used.