Package Details: gimp-git 2:2.99.7.r462.d33c45fb47-1

Git Clone URL: https://aur.archlinux.org/gimp-git.git (read-only, click to copy)
Package Base: gimp-git
Description: GNU Image Manipulation Program
Upstream URL: https://www.gimp.org
Licenses: GPL, LGPL
Conflicts: gimp
Provides: gimp
Submitter: None
Maintainer: bartus
Last Packager: bartus
Votes: 112
Popularity: 0.093042
First Submitted: 2009-05-27 08:12
Last Updated: 2021-10-02 15:55

Dependencies (55)

Required by (125)

Sources (2)

Pinned Comments

bartus commented on 2019-08-01 19:45

Note: If you wont to have both gimp-git and stock gimp installed, there's a non-conflicting version of this package called gimp-develop-git
This package is also hosted on GitHub.
Use env vars to control build process:
  • DISABLE_MESON=1 to build with Autotools build system (disabled by default)
  • MAKEFLAGS="xxx" to override default make flags.
Usage cases:
  • makepkg DISABLE_MESON=1
  • yay -S gimp-git --mflags "DISABLE_MESON=1"
Disclaimer: Package uses Travis to automatically update version of dependencies. Script executes once a day, so please wait a day before reporting dependencies version mismatch, thanks!

Latest Comments

1 2 3 4 5 6 ... Next › Last »

nikdikpik commented on 2021-12-29 15:19

I have no idea?

haawda commented on 2021-12-29 10:33

nikdikpik: why does you build try to build version-2:2.99.7? I built 2:2.99.9.r243 successfully.

nikdikpik commented on 2021-12-28 17:53

Doesn't build.

Configure failed or did not finish! ==> ERROR: A failure occurred in build(). Aborting... error: failed to build 'gimp-git-2:2.99.7.r462.d33c45fb47-1': error: packages failed to build: gimp-git-2:2.99.7.r462.d33c45fb47-1

foxrumor commented on 2021-12-24 05:26

This AUR package does not install everything needed for the new experimental "Paint Select Tool" to function. More information about this here: https://gitlab.gnome.org/GNOME/gimp/-/issues/2912#note_1308011

What needs to be done on install for the paint select tool to be functional:

- build GEGL with maxflow (https://github.com/gerddie/maxflow) and
the option -Dworkshop=true in order to be able to select the
experimental Paint Select tool in the Playground (operation
"gegl:paint-select" is needed).

electricprism commented on 2021-12-03 01:29

@bartus -- thanks paru -S gimp-git --mflags "DISABLE_MESON=1 --nocheck" worked just fine

bartus commented on 2021-12-02 14:30

@maderios: Don't think disabling check() here is an optimal solution. Users that don't care about tests will probably just edit their /etc/makepkg.conf and add !check to BUILDENV ¯\_(ツ)_/¯

btw. it works for PKGBUILD to, add BUILDENV+=(!check) at the beginning of PKGBUILD to disable check()

maderios commented on 2021-12-02 12:27

@bartus For other users, please remove these unnecessary tests from PKBUILD. gimp-git builds fine without these tests.

maderios commented on 2021-12-02 11:07

As Jehan (Gimp developer) said, it's specific Arch Aur issue. I disabled tests this way in PKGBUILD to solve it 

pkgver() {
# shellcheck disable=SC2183,SC2046
#
#check() {
#  if ((DISABLE_MESON)); then
#    cd $_pkgname
#    xvfb-run make check
#   xvfb-run make distcheck
#  else
#    ninja -C "${srcdir}/build" test
#  fi

bartus commented on 2021-12-02 08:20

@electricprism: Meson was disabled in 30b4a0f0f7f6

@electricprism: to pass --nocheck to yay use `yay --mflags "--nocheck" it's described in manual.

@maderios: those are rare issues caused by commits not containing all the relevant changes, usually are fixed within hours a day max.

@foobaz: That's weird, can't see any reference to /etc/gimp in my build logs. Are you sure it's correct?

@maderios: I can't really fix those errors for you, perhaps could add a mask for UI tests in check() but it's beside the point as you will probably defer using --nocheck flag to skip those.

electricprism commented on 2021-12-02 07:15

I'm not really sure how to disable tests to get to compile. Does it require a -- nocheck flag on pkgbuild ??? I've tried yay -S gimp-git --mflags "DISABLE_MESON=1" but it fails the same as building regularly.

I read the bug report listed below and it was difficult to decipher if there was any useful workaround information there.