Package Details: gimp-plugin-resynthesizer-git 2.0.3.r0.gb10d6ed-1

Git Clone URL: (read-only, click to copy)
Package Base: gimp-plugin-resynthesizer-git
Description: Suite of gimp plugins for texture synthesis (like heal-selection). Git-Version
Upstream URL:
Keywords: heal heal-selection
Licenses: GPL2
Conflicts: gimp-resynth, gimp-resynth-git
Provides: gimp-plugin-resynthesizer=2.0
Submitter: TrialnError
Maintainer: TrialnError
Last Packager: TrialnError
Votes: 207
Popularity: 0.81
First Submitted: 2014-10-09 10:24
Last Updated: 2018-01-11 00:50

Latest Comments

1 2 3 4 5 6 Next › Last »

SanskritFritz commented on 2018-10-28 20:56

Since it provides it, no need for a conflict.

0x9fff00 commented on 2018-10-28 17:50

This should conflict with gimp-plugin-resynthesizer.

TrialnError commented on 2015-11-06 22:03

Sure it needs it, but not in any of the depends lines.
autoconf is a package from the base-devel group. And base + base-devel packages need to be installed if someone wants to use the AUR.
And as they're required they won't be included in the PKGBUILD.

So are the Guidelines[0]


MikuroK commented on 2015-11-06 11:46

requires autoconf as a make dependancy

TrialnError commented on 2015-09-17 09:37

Ah, that's the reason supermario asked for it last year. Thanks for the info dreieck. Will add it

dreieck commented on 2015-09-16 16:38

Please add


(or equivalent)
in the PKGBUILD,
so that dependencies can be satisfied (e.g. package "gimp-script-smart-remove" requires "gimp-plugin-resynthesizer").

TrialnError commented on 2015-09-13 21:47

Tested it locally without the shebang changing line and it worked with extra/gimp. So removing it

Thanks for the intel

TrialnError commented on 2015-09-13 21:29

Ok, but still not really clear what's causing it.
Nontheless my choice is to stay with the repo version, where this sed line doesn't do any harm. I will test if it can be removed for it too (or maybe someone has done it already?). Dunno if AUR Repos allow branches. If so I could add this upcoming(?) change in a separate branch.

Another question. Did it work with gimp-git before and stopped only recently?

JonnyRobbie commented on 2015-09-13 18:32

It was a problem with gimp-git (2.9). It didn't happen on gimp (2.8). Commenting out the sed on line 27 in this PKGBUILD worked around the issue. Not sure why it was a problem with the git version and not with the stable one.

Basically the problems was that PKGBUILD of this repo (sed on line 27) changed shebangs from python to python2, which wasn't a problem in stable, but stopped working in git.

mytbk commented on 2015-09-13 14:53

The sed line change python to python2 causes this issue: