Package Details: gimp-gap 2.7-2

Git Clone URL: https://aur.archlinux.org/gimp-gap.git (read-only, click to copy)
Package Base: gimp-gap
Description: Gimp Animation Package, gimp's plugin for animation
Upstream URL: https://www.gimp.org/tutorials/Using_GAP/
Licenses: GPL3
Submitter: ElMastro
Maintainer: ElMastro
Last Packager: ElMastro
Votes: 12
Popularity: 0.000000
First Submitted: 2015-12-03 22:05 (UTC)
Last Updated: 2023-11-11 18:01 (UTC)

Dependencies (11)

Required by (0)

Sources (2)

Latest Comments

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

ElMastro commented on 2016-06-03 14:12 (UTC)

I've tried to make a new version of the PKGBUILD : http://pastie.org/10863095 This one is built from the unstable branch, but it appears to work. I can't be sure because I've got problems with permissions. Can someone try if it si better than the other one?

ElMastro commented on 2016-03-07 14:51 (UTC)

frankspace, you're welcome. However, disabling the libmpeg3 may be a solution, and my version of gimp-gap on my laptop works, but It seems the source has many problems. I've exposed them on the bug board of gimp, and they suggest we could try to install a (newer) version from git. Actually I'm cheking this possibility, so that if it works, we'll move directly on the 2.8, wich should be actually bug free.

frankspace commented on 2016-03-05 04:35 (UTC)

I appreciate your hard work on this. It may just be that unless someone does work on it upstream, it's an unsolveable problem. But I just re-checked the PKGBUILD that I posted previously, and again, it compiles fine on my box and seems to work upon installation, albeit without libmpeg3 (and I admit I don't know how limiting that is, because I actually haven't personally worked with GAP very much, but lots of distros seem to disable it). But without knowing what's different about our respective boxes, I suppose that's not much help.

ElMastro commented on 2016-02-17 17:54 (UTC)

Bad News. It appears as the problem is caused by the vhook fuction of libavfilter wich is deprecated. On the second compilation it skips the "make all" and "make all-recursive" part, and that's why it works. at this point for me it's clear there is a major issue with the source. There aren't yet answers in the forum, so I don't know what to do. for doctorcolossus: Thanks, I'll add them when the PKGBULD works.

doctorcolossus commented on 2016-02-16 05:09 (UTC)

cmake and nasm should be added to the make dependencies.

ElMastro commented on 2016-02-03 13:48 (UTC)

I've tried with intltool, but still doesn't work. Since there's no answer in the forum, I'm trying to figure what changes from the first and the second compilation, expecially with external libraries

magesing commented on 2016-01-31 21:31 (UTC) (edited on 2016-01-31 21:43 (UTC) by magesing)

I managed to get it installed, after installing the `intltool` package first. If you see the following problem when doing `Video->Split Video Into Frames->Mplayer based extraction . . .` ``` 29501 # MPLAYER_PID -aofile has been removed. Use -ao pcm:file=<filename> instead. -jpeg has been removed. Use -vo jpeg:<options> instead. MPlayer SVN-r37379 (C) 2000-2015 MPlayer Team 210 audio & 441 video codecs ``` You need to uncheck the Mplayer 1.0pre5 checkbox in the dialog.

ElMastro commented on 2016-01-30 00:15 (UTC)

The posting regarding this PKGBUILD in the Arch Forum haven't developed for 3 days now. If the package bothers, I'll happily remove/disown it, but certainly I need much time to figure how to create a repo and how it works. Tne reason why I kept the PKGBUILD was that I figured that the problem could be solved easily to solve compiling it twice. From the experience here and in the forum now my guess is that the package has more then one problem, and some of them are really tricky to solve, as problably there's something not working in the source package itself.

komitaltrade commented on 2016-01-28 17:09 (UTC)

OK. In fact, I know, but that is not point of issue. You should first to make some sort of the poll to see how many peoples will be available to be your "testers". If that will satisfy you, than you should to create your own testing repository, what all your "testers" can add to repos and than they will be able to test it. Creating repo is quite simple. Only question remain from begin - do you have enough "testers".

komitaltrade commented on 2016-01-28 15:51 (UTC)

That is the right question. ..... no idea.

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