gimp cage tool - fix in 16.04?

[Simon Quigley]

Hello Robert,

I'm doing some casual poking around at the moment to see how easy it
would be for this patch to be applied.

> The cage tool in 2.8.16-1ubuntu1.1 is broken. Details can be found here:
> https://bugzilla.gnome.org/show_bug.cgi?id=678085
> 
> If I am not mistaken 2.8.18 does not fix the issue. At least the
> changelog at [1] does not indicate anything about a fix and target
> milestone of the bug is 2.10. Do you see any chance that the fix for
> this issue will be made available via patch in 16.04?

I think otherwise. Look at when this Git tag was set upstream:
https://git.gnome.org/browse/gimp/tag/?h=GIMP_2_8_18

tag date	2016-07-13 20:27:19 (GMT)

This is the date for 2.8.16:

tag date	2015-11-21 18:04:13 (GMT)

Let's look at the timestamps on the two commits that were done to fix
this problem:

2016-02-02 11:21:15 (GMT)

2016-02-07 17:50:11 (GMT)

So unless there is some magical way to ensure commits don't land in a
Git tag (which I highly doubt they would even WANT to do either way), it
should be fixed.

Since you know this issue better than I do, I've backported Yakkety's
GIMP (2.8.18-1) to Xenial and I put it in ppa:tsimonq2/gimp-xenial for
you to test. If this solves your issue, then I'll work on getting a
debdiff for you to test against the Xenial version. It will most likely
take (at least) a half an hour for all the sources to publish, so if you
are reading this email right after I send it, please wait. :)

After that, the process is fairly simple. Either of us would file a bug
in Launchpad, then the Stable Release Update process[1] is followed to
get it into Xenial[2].

Thanks for bringing this up! :)

[1] https://wiki.ubuntu.com/StableReleaseUpdates
[2] This is why I need to know if it exists in Yakkety, so I know if the
fix needs to be uploaded to Yakkety first, because that's usually how
the procedure goes.

-- 
Simon Quigley
tsimonq2 at ubuntu.com
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4