[ubuntu/bionic-proposed] fontconfig 2.12.6-0ubuntu2 (Accepted)

[Iain Lane]

fontconfig (2.12.6-0ubuntu2) bionic; urgency=medium

  * Upload proposed patch from upstream bug #103652. If the fontconfig cache
    was built on a system that has nanosecond timestamps and then later
    transplanted to one that doesn't - for example by mksquashfs as part of a
    live CD build - we consider the cache invalid and rebuild it during the
    boot process. Depending on the fonts involved, this can take a significant
    amount of time and potentially cause knock-on timeouts. The approach in
    this patch is to ignore the nanosecond portion of the cache's value if we
    get 0 when stat()ing the referenced directory, meaning it is considered
    fresh if the rest of the timestamp matches. (LP: #1749546)

Date: Thu, 05 Apr 2018 17:13:52 +0100
Changed-By: Iain Lane <iain at orangesquash.org.uk>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/fontconfig/2.12.6-0ubuntu2
-------------- next part --------------
Format: 1.8
Date: Thu, 05 Apr 2018 17:13:52 +0100
Source: fontconfig
Binary: fontconfig fontconfig-config fontconfig-udeb libfontconfig1-dev libfontconfig1
Architecture: source
Version: 2.12.6-0ubuntu2
Distribution: bionic
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Iain Lane <iain at orangesquash.org.uk>
Description:
 fontconfig - generic font configuration library - support binaries
 fontconfig-config - generic font configuration library - configuration
 fontconfig-udeb - generic font configuration library - minimal runtime (udeb)
 libfontconfig1 - generic font configuration library - runtime
 libfontconfig1-dev - generic font configuration library - development
Launchpad-Bugs-Fixed: 1749546
Changes:
 fontconfig (2.12.6-0ubuntu2) bionic; urgency=medium
 .
   * Upload proposed patch from upstream bug #103652. If the fontconfig cache
     was built on a system that has nanosecond timestamps and then later
     transplanted to one that doesn't - for example by mksquashfs as part of a
     live CD build - we consider the cache invalid and rebuild it during the
     boot process. Depending on the fonts involved, this can take a significant
     amount of time and potentially cause knock-on timeouts. The approach in
     this patch is to ignore the nanosecond portion of the cache's value if we
     get 0 when stat()ing the referenced directory, meaning it is considered
     fresh if the rest of the timestamp matches. (LP: #1749546)
Checksums-Sha1:
 525d1635504912663fbc4a23ec7884e58f0c1c4b 2384 fontconfig_2.12.6-0ubuntu2.dsc
 534b2acb61bfc4b7568493abd1b01955f0c6f421 29168 fontconfig_2.12.6-0ubuntu2.debian.tar.xz
 8c01ad5ba4bb9820f8e046e3d91d92ff62f92956 13236 fontconfig_2.12.6-0ubuntu2_source.buildinfo
Checksums-Sha256:
 e7109f728f73761ad17ff5c5ec066ad940b67b779a78a094b67a7af4cfafadcc 2384 fontconfig_2.12.6-0ubuntu2.dsc
 75c259e2d6b1944fe76a49f89b806b3ee34fe7a42eb25efd289e38b1b5e16517 29168 fontconfig_2.12.6-0ubuntu2.debian.tar.xz
 fa0e4591b1779eba5cdc8336adcc1e7c7f289741ae8ec920cb9d4542f2204411 13236 fontconfig_2.12.6-0ubuntu2_source.buildinfo
Files:
 1cb09aa53947e6b442a1b8bd736127d6 2384 fonts optional fontconfig_2.12.6-0ubuntu2.dsc
 e49b6389d0f44c4145b2b9c8e5e7e0d9 29168 fonts optional fontconfig_2.12.6-0ubuntu2.debian.tar.xz
 0d7d4be2ef4db7ad2b37aefdcbfad20b 13236 fonts optional fontconfig_2.12.6-0ubuntu2_source.buildinfo
Original-Maintainer: Keith Packard <keithp at debian.org>