Hmm that rules out the obvious problems...
However what is odd is the Access time not being equal to modify time.
Do you have no-acces in mountoptions? Or is that suposed to be this way.
If I do
{18-11-14 18:26}Hephaistos:~ toast% date && stat /var/cache/fontconfig/
November 14, 2018 at 06:26:45
On 11/14/18 16:05, Till Wegmüller wrote:
Hi Predrag
On 14.11.18 15:15, Predrag Zečević - Technical Support Analyst wrote:
Fontconfig warning: Directory/file mtime in the future. New fonts may
not be detected.
Fontconfig warning: Directory/file mtime in the future. New fonts may
not be detected
Hi Predrag
On 14.11.18 15:15, Predrag Zečević - Technical Support Analyst wrote:
> Fontconfig warning: Directory/file mtime in the future. New fonts may
> not be detected.
> Fontconfig warning: Directory/file mtime in the future. New fonts may
> not be detected.
> Fontconfig warning: Directory/fil
On 11/14/18 14:46, Aurélien Larcher wrote:
Obviously I forgot to rename dejavu.
When it comes to your fontconfig issue, how does duplicate packages
mess up since you cannot install both?
Hi Aurélien
Maybe font config looks at wrong directory (not sure what is proper
location at all anymore. I
Obviously I forgot to rename dejavu.
When it comes to your fontconfig issue, how does duplicate packages
mess up since you cannot install both?
On 11/14/18, Predrag Zečević - Technical Support Analyst
wrote:
> Hi all,
>
> which *dejavu* font package to use?
>
> $ pkg list dejavu
> NAME (PUBLISHE
Hi all,
which *dejavu* font package to use?
$ pkg list dejavu
NAME (PUBLISHER) VERSION
IFO
system/font/dejavu2.37-2018.0.0.2
i--
From 'pkg search -r dejavu' command:
pkg.fmri setopenindiana.org/system/f
