Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 812401 - media-gfx/gimp-2.10.26: Fails to build with 09-texlive.conf fontconfig enabled
Summary: media-gfx/gimp-2.10.26: Fails to build with 09-texlive.conf fontconfig enabled
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Sergey Torokhov
Keywords: PullRequest
Depends on:
Reported: 2021-09-10 07:56 UTC by Petr Šabata
Modified: 2021-09-30 21:48 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

emerge --info (,7.59 KB, text/plain)
2021-09-10 07:56 UTC, Petr Šabata
build.log (snippet) (,5.93 KB, text/plain)
2021-09-10 08:01 UTC, Petr Šabata
09-texlive.conf (09-texlive.conf,190 bytes, application/xml)
2021-09-10 08:02 UTC, Petr Šabata

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Šabata 2021-09-10 07:56:41 UTC
Created attachment 738760 [details]
emerge --info

Updating to media-gfx/gimp-2.10.26 failed after I enabled 09-texlive.conf, provided by dev-texlive/texlive-xetex-2021.

The build fails while it tries to create temporary files under /usr/share/texmf-dist/fonts/.  It could very well be because 09-texlive.conf defines these absolute paths, so maybe not a GIMP build issue per se.
Comment 1 Petr Šabata 2021-09-10 08:01:08 UTC
Created attachment 738763 [details]
build.log (snippet)

The full log is too large to attach, even compressed.
Comment 2 Petr Šabata 2021-09-10 08:02:13 UTC
Created attachment 738766 [details]

Provided by dev-texlive/texlive-xetex-2021
Comment 3 Petr Šabata 2021-09-10 08:03:24 UTC
Just to clarify, disabling the 09-texlive.conf via `eselect fontconfig` fixes the problem.
Comment 4 Sergey Torokhov 2021-09-12 00:21:57 UTC
This issue looks like
with the difference that there fontconfig enable wasn't mentioned.

I'll try to reproduce and then to discuss it with someone from font team how to handle this case.
Comment 5 Sergey Torokhov 2021-09-13 20:29:15 UTC
I could confirm that issue is reproduced when I do

> eselect fontconfig enable 09-texlive.conf 
after installation of dev-texlive/texlive-xetex package.
Comment 6 Petr Šabata 2021-09-13 21:08:05 UTC
Yes, this is most likely the same as bug 715534.  I think the reporter there just didn't think or remember to mention the fontconfig bit.

Also, 09-texlive.conf is the only config on my system that lists any absolute paths.  I have zero idea about fontconfig files but perhaps that's the problem.
Comment 7 Sergey Torokhov 2021-09-21 15:14:51 UTC
It seems that issue is related that dev-texlive/texlive-xetex didn't install appropreate .uuid files in appropriate dirs/subdirs under /usr/share/texmf-dist/fonts/.

If 09-texlive.conf is enable and then reinstall (or unistall - install) dev-texlive/texlive-xetex again the these .uuid files are generated.

The comment from other issue state that early:

> font.eclass has 'EXPORT_FUNCTIONS pkg_setup src_install pkg_postinst pkg_postrm'.
> Blindly inheriting font.eclass at the end of 'inherit' line results in 
> losing exported functions from other eclasses.

Currently font.eclass is inherited first in  dev-texlive/texlive-xetex. Maybe the order of eclass functions is relevant too.
But I need to check this assumption.
Comment 8 Sergey Torokhov 2021-09-24 16:22:37 UTC
It seems as dev-texlive/texlive-xetex install font into unusual place therefore font.eclass (namely fc-ccache of fontconfig) doesn't generate .uuid files.

But if eselect fontconfig enable 09-texlive.conf is done then fontconfig knows about new unusual place and update fontcache to new directory to and genarate .uuid files.

Without this .uuid files presented sandbox error takes place.

Is it possible to force font.eclass to call fc-ccahe within directories listed in 09-texlive.conf or it require to call additionally fc-ccache for directories in pkg_postinst phase?