Bug#896684: fontconfig-config errors: Maybe tightening the dependencies is an option?
On 2018-11-05 09:34:55 +0100, Laurent Bigonville wrote:
> For what I see, libfontconfig1 package has a dependency against
> fontconfig-config (>= ${source:Version})
>
> Note that the relation is >= and not =
>
> Looking at the git history, I can see the following commit:
>
> commit 7278b583d2ec28786ae75d1917a5eab98c63fbf9
> Author: Keith Packard
> 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
This requirement is really strange. I would say that something is
wrong in the build process. If the build requires some tool that
is built in a first step, it should use some search path relative
to the build directory.
> We could make the dependency more strict again, but that cause issues to
> build the package.
I don't see how a more strict dependency could cause issues to build
the package, since in any case, you need an older version to be
installed first. Then you could install all the needed generated
binary packages (new version) at the same time.
--
Vincent Lefèvre - Web:
Bug#896684: fontconfig-config errors: Maybe tightening the dependencies is an option?
On Thu, 19 Jul 2018 08:39:02 +0200 Thomas Viehmann wrote:
> Hi,
>
> So the original report experienced this - like me - with emacs.
> I could also produce it with just running fc-cache.
>
> Damien's hint is spot-on, thank you Damien!
>
> I had a 2.13 fontconfig-config but 2.12 (lib)fontconfig:
>
> ii fontconfig 2.12.6-0.1
> ii fontconfig-config 2.13.0-5
> ii libfontconfig1:amd64
> 2.12.6-0.1 ii libfontconfig1-dev:amd64
> 2.12.6-0.1
>
> After upgrading everything to 2.13.0-5, the errors are gone.
>
> Would it be an option to require the same (upstream?) version in the
> dependency on fontconfig on fontconfig-config. Clearly fontconfig may
> break if it get's a too new fontconfig-config.
For what I see, libfontconfig1 package has a dependency against
fontconfig-config (>= ${source:Version})
Note that the relation is >= and not =
Looking at the git history, I can see the following commit:
commit 7278b583d2ec28786ae75d1917a5eab98c63fbf9
Author: Keith Packard
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
We could make the dependency more strict again, but that cause issues to
build the package.
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
Bug#896684: fontconfig-config errors: Maybe tightening the dependencies is an option?
Hi, So the original report experienced this - like me - with emacs. I could also produce it with just running fc-cache. Damien's hint is spot-on, thank you Damien! I had a 2.13 fontconfig-config but 2.12 (lib)fontconfig: ii fontconfig 2.12.6-0.1 ii fontconfig-config 2.13.0-5 ii libfontconfig1:amd64 2.12.6-0.1 ii libfontconfig1-dev:amd64 2.12.6-0.1 After upgrading everything to 2.13.0-5, the errors are gone. Would it be an option to require the same (upstream?) version in the dependency on fontconfig on fontconfig-config. Clearly fontconfig may break if it get's a too new fontconfig-config. Best regards Thomas
