<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On Thu, 19 Jul 2018 08:39:02 +0200 Thomas Viehmann
<a class="moz-txt-link-rfc2396E" href="mailto:tv@beamnet.de"><tv@beamnet.de></a> wrote:<br>
> Hi,<br>
> <br>
> So the original report experienced this - like me - with emacs.<br>
> I could also produce it with just running fc-cache.<br>
> <br>
> Damien's hint is spot-on, thank you Damien!<br>
> <br>
> I had a 2.13 fontconfig-config but 2.12 (lib)fontconfig:<br>
> <br>
> ii fontconfig 2.12.6-0.1 <br>
> ii fontconfig-config 2.13.0-5 <br>
> ii libfontconfig1:amd64 <br>
> 2.12.6-0.1 ii libfontconfig1-dev:amd64 <br>
> 2.12.6-0.1<br>
> <br>
> After upgrading everything to 2.13.0-5, the errors are gone.<br>
> <br>
> Would it be an option to require the same (upstream?) version
in the <br>
> dependency on fontconfig on fontconfig-config. Clearly
fontconfig may <br>
> break if it get's a too new fontconfig-config.<br>
<p>For what I see, libfontconfig1 package has a dependency against
fontconfig-config (>= ${source:Version})<br>
</p>
<p>Note that the relation is >= and not =</p>
<p>Looking at the git history, I can see the following commit:</p>
<pre>commit 7278b583d2ec28786ae75d1917a5eab98c63fbf9
Author: Keith Packard <a class="moz-txt-link-rfc2396E" href="mailto:keithp@keithp.com"><keithp@keithp.com></a>
Date: Sun Feb 23 14:29:53 2014 -0800
Relax libfontconfig1 dependency on fontconfig-config to >=
This will allow building the package on other architectures where
the build dependencies require that fontconfig be installed in order
to build fontconfig.
Signed-off-by: Keith Packard <a class="moz-txt-link-rfc2396E" href="mailto:keithp@keithp.com"><keithp@keithp.com></a></pre>
<p>We could make the dependency more strict again, but that cause
issues to build the package.</p>
<p>For what I can see, the circular dependency is caused by
texlive-binaries (used for the documentation generation) that
pulls libfontconfig1. That could be a good example for using the
nodoc build profile<br>
</p>
</body>
</html>