Bug#855930: Bug#853119: Request to take a look at #855930

2017-02-27 Thread Vincent Danjean
Le 27/02/2017 à 00:45, Norbert Preining a écrit : >>> So lulaatex seems to really use the HOME directory. > > Yes, of course, because it has to update the font database. > > Complain to the author of the whole setup about extra > font database in lua format (Hans Hagen of ConTeXt) for > that

Bug#855930: Bug#853119: Request to take a look at #855930

2017-02-26 Thread Norbert Preining
> > So lulaatex seems to really use the HOME directory. PS @Tomasz, that was my question concerning /var writable! I used a cowbuilder where the building user is root, thus the font database is built in /var/lib/texmf (TEXMFSYSVAR), while when run as other user it is ~/.texlive2016/... (TEXMFVAR)

Bug#855930: Bug#853119: Request to take a look at #855930

2017-02-26 Thread Norbert Preining
> > So lulaatex seems to really use the HOME directory. Yes, of course, because it has to update the font database. Complain to the author of the whole setup about extra font database in lua format (Hans Hagen of ConTeXt) for that requirement, but that is the way it is. Lualatex maintains a

Bug#855930: Bug#853119: Request to take a look at #855930

2017-02-26 Thread Tomasz Buchert
On 26/02/17 23:49, Vincent Danjean wrote: > [...] > > And, for more info: > $ mkdir p > $ HOME=p lualatex lualatex-example.tex > This is LuaTeX, Version 0.95.0 (TeX Live 2016/Debian) > [...] > luaotfload | db : Font names database not found, generating new one. > luaotfload | db : This can take

Bug#855930: Bug#853119: Request to take a look at #855930

2017-02-26 Thread Vincent Danjean
Le 26/02/2017 à 23:37, Vincent Danjean a écrit : > I eventually succeeded in reproducing the bug: lualatex needs a > writable HOME directory. On my plain (sid) system: > $ cat lualatex-example.tex > \documentclass{article} > \usepackage{luacode} > \begin{document} > A random number: >

Bug#855930: Bug#853119: Request to take a look at #855930

2017-02-26 Thread Vincent Danjean
Le 26/02/2017 à 22:37, Lucas Nussbaum a écrit : > On 26/02/17 at 21:41 +0100, Vincent Danjean wrote: >> Can you elaborate? I cannot reproduce this failure. It works >> in my sbuild environment. > > if you have a successful build with sbuild, please provide the build > log: it's usually useful to

Bug#855930: Bug#853119: Request to take a look at #855930

2017-02-26 Thread Lucas Nussbaum
On 26/02/17 at 21:41 +0100, Vincent Danjean wrote: > Lucas: can you tell us how more on how the build environment > is generated ? Hi, I used sbuild-createchroot, then manually cleaned it with debfoster. But there should be nothing special about it, except the removal of lsb-base and tzdata

Bug#855930: Bug#853119: Request to take a look at #855930

2017-02-26 Thread Vincent Danjean
Le 26/02/2017 à 15:29, Tomasz Buchert a écrit : > On 26/02/17 10:25, Norbert Preining wrote: >> On Sun, 26 Feb 2017, Norbert Preining wrote: >>> I will try to run it in a clean cowbuilder with only the build-deps >>> installed and see what might be the reason. > > Thanks for looking into it. >