Bug#810617: applying fix to stable

[chrysn]

On Tue, Sep 12, 2017 at 08:46:52PM +0200, chrysn wrote:
> unless [...], the next easiest solution would be packaging a 1.15
> version (fix is in everythin newer than 1.15.4).

After a closer look at cairo's versioning scheme, it has become clear
that packaging 1.15.8 is not directly an option, as odd numbers there
indicate snapshots rather than releases.

Nevertheless, I gave it a try (turned out that taking the snapshot as a
new orig tarball takes no more than the usual
merging/changelogging/patch-refreshing, plus a few new symbols), and
indeed the issue is fixed in "1.15.8-0.1".

Maintainers, if having something like that in experimental is appealing
to you, I can push branches upstream-experimental-snapshots and
experimental-snapshots and a tag upstream-experimental-snapshots/1.15.8
to collab-maint (or to another place or with other names depending on
how you manage those things).

Best regards
chrysn

-- 
You don't use science to show that you're right, you use science to become 
right.
  -- Randall Munroe


signature.asc
Description: PGP signature

Bug#810617: applying fix to stable

[chrysn]

The patch linked to in the report Dennis found[1] applies to stable with
some offsets, but fails to build; there is a new is_vector member on
targets which I didn't track down any further.

I've asked upstream about porting the patch back to the 1.14 series;
unless that turns out positive, the next easiest solution would be
packaging a 1.15 version (fix is in everythin newer than 1.15.4).

If there are any attempts around backporting this to 1.14, they should
probably also include [3], a fixup to [1].

Best regards
chrysn

[1]: 
https://cgit.freedesktop.org/cairo/commit/?id=190678f6444ad879847d603c3c9eaf8e9ab6887a
[2]: https://bugs.freedesktop.org/show_bug.cgi?id=94615#c5
[3]: 
https://cgit.freedesktop.org/cairo/commit/?id=d28b6d9b128675dfa9b3b6b793844144183aff64


signature.asc
Description: PGP signature