MX 17 Repository: The Krita Thread
MX 17 Repository: The Krita Thread
We now have a backported-from-upstream-Debian build of the popular KDE creative paint program, Krita 3.3.1, in our test repository. Version 3.3.2.1 is in the works.
Krita is intended for the artist that creates from scratch, rather than processing existing digital images.
Krita is intended for the artist that creates from scratch, rather than processing existing digital images.
Re: MX 17 Repository: The Krita Thread
He's on a roll...
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX 17 Repository: The Krita Thread
I did mention I leveled up by learning how to use pbuilder to cross-build packages.
Re: MX 17 Repository: The Krita Thread
Now updated to 3.3.2.1 in the test repo! I also have generic Debian Stretch builds in the openSUSE build service and at least one user reports that it works great.
Re: MX 17 Repository: The Krita Thread
The latest and greatest 4.0.1 release is now in the test repo!
Video explaining the new features: https://youtu.be/OXvHHJUyBDgKrita 4.0 release notes
With a complete rewrite of the vector layer file format, the addition of Python scripting, a new text tool and much more, Krita 4.0 is one of the biggest releases ever. There is so much to explore and enjoy! As a team, we’re happy and proud to have reached this milestone and we’re looking forward to build on Krita 4 for many releases to come!
Before we begin telling you about all the new and improved things, take a moment to read this warning:
Krita 4 has a new file format for vector and text objects. Krita 4 tries to import Krita 3 and older files. Krita 3 and older will not be able to read vector and text objects saved by Krita 4. Because the new file format and the old file format are not 100% compatible, images with vector and text objects might look different in Krita 4. We recommend:
To always keep a backup of your Krita 3 files before working on them in Krita4!
In some cases, to convert your vector and text layers to raster layers before working on your old files in Krita 4!
Note that on all platforms it is possible to keep Krita 3 and Krita 4 running side by side. On Windows, use the zip archive downloads, on Linux the appimages and on OSX the disk images, dragged to some other place than Applications. Krita 4 and Krita 3 share settings and resources.
Re: MX 17 Repository: The Krita Thread
Bug-smashing 4.0.2 release rolls into the test repo. Krita hasn't even yet set up a release announcement...
Re: MX 17 Repository: The Krita Thread
Very nice! I use this all the time when GIMP is way overkill...
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX 17 Repository: The Krita Thread
And we now have updated to the latest 4.0.3 bugfix release in testing.
Re: MX 17 Repository: The Krita Thread
Krita 4.0.4 is now in the test repository. As usual, it's built against standard Debian Stretch packages except for the backported vc-dev build-depend, which means it requires nothing from the test repo for runtime libraries...it's vanilla Stretch-compatible.
The big fix in this update is that it loads the Python library correctly, making the Python scripting usable.
The big fix in this update is that it loads the Python library correctly, making the Python scripting usable.
Re: MX 17 Repository: The Krita Thread
Whoops... forgot a post for the 4.1.0 update. One nice addition is that it adds support for the new heif image format (default for the new iPhones).
Anyway, we now have the 4.1.1 bugfix update in our test repo. After a initial build failure, I managed to track it down to a bit of new code that tested for the version of Windows it might be building against, but required at least Qt 5.9 instead of our 5.7. Luckily, since that code wasn't going to run in a Linux build, patching out the new include line allowed it to build with 5.7.
Anyway, we now have the 4.1.1 bugfix update in our test repo. After a initial build failure, I managed to track it down to a bit of new code that tested for the version of Windows it might be building against, but required at least Qt 5.9 instead of our 5.7. Luckily, since that code wasn't going to run in a Linux build, patching out the new include line allowed it to build with 5.7.