> In other words, it was only committed to master after the gimp-2-8 > branch was made; and there's no evidence that this was cherry-picked > onto the gimp-2-8 branch (from a quick log inspection). It indeed does > not appear that this commit is in 2.8.18, although it should be in 2.9.4 > (an unstable-series release). It might be worth asking upstream whether > it can be fixed in the 2.8 series.
Nice catch, thank you. I *thought* that was on master at the time of the git tag, but the web interface tricked me. I learned a new git command today. ;) So in other words, Robert, it's very unlikely that the package I uploaded to that PPA will fix your problem. We'll have to wait for that patch to be backported, and I don't know if there's a clean way to do that as that branch might be far ahead of master. I'll keep the PPA there and I'll keep my eye out for when that gets into master (so it can be applied easily). I'll dig into this more in a bit, and I'll see if I can comment on that bug, citing this email thread. Thanks again, Colin! -- Simon Quigley [email protected] tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-devel-discuss mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
