[Bug 1803534] Re: Backport uuid based cache file naming scheme

[Ubuntu Foundations Team Bug Bot]

The attachment "fontconfig_2.12.6-0ubuntu2_2.12.6-0ubuntu3.diff" seems
to be a debdiff.  The ubuntu-sponsors team has been subscribed to the
bug report so that they can review and hopefully sponsor the debdiff.
If the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1803534

Title:
  Backport uuid based cache file naming scheme

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Fontconfig 2.13.0 changed the cache file naming scheme to be based on
  the contents of ".uuid" file in the directory rather than a hash of
  the directory name.  On a pure debs system this doesn't really matter
  since everything is using the same libfontconfig.so.

  When snaps are involved, it can lead to some apps not seeing the cache
  files produced by a different fontconfig version.  In particular,
  while libfontconfig 2.13 can reuse 2.12's cache files for read only
  directories, the reverse is not true.  This will be a problem for apps
  built on top of the "core18" base snap when run on later Ubuntu
  releases (cosmic, disco, etc).

  By providing a backport of the UUID cache file feature to bionic for
  use by snap applications, we'd avoid this.  Having it in bionic-
  updates would be ideal so that snapcraft picks it up automatically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+subscriptions