GNU bug report logs - #35780
texlive-latex-polyglossia package empty

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35780 in the body.
You can then email your comments to 35780 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Josh Holland <josh <at> inv.alid.pw>
To: bug-guix <at> gnu.org
Subject: texlive-latex-polyglossia package empty
Date: Fri, 17 May 2019 17:51:52 +0100

Steps to reproduce:
$ guix build texlive-latex-polyglossia
$ tree /gnu/store/d9nndb33yd22pay1yyg76nb0i56qdmkq-texlive-latex-polyglossia-49435

Expected results:
Something containing the file polyglossia.sty

Actual results:
Only an empty directory share/texmf-dist/tex/latex/polyglossia exists.

Message #8 received at 35780 <at> debbugs.gnu.org (full text, mbox):

From: Josh Holland <josh <at> inv.alid.pw>
To: 35780 <at> debbugs.gnu.org
Cc: Josh Holland <josh <at> inv.alid.pw>
Subject: [PATCH] attempt to fix polyglossia
Date: Fri, 17 May 2019 22:23:51 +0100

---
I had a quick look into fixing this myself, and made a little bit
of progress.  Not being that familiar with how things work yet,
I'm going on what I can guess by looking at gnu/packages/tex.scm,
guix/build-system/texlive.scm and guix/build/texlive-build-system.scm
so I may well be misinterpreting some things.

The source for polyglossia comes in a single file, polyglossia.dtx.
The README embedded within it says to extract the files by running
xetex or luatex on it.  I tried to convince the build system to do
this by this patch, which may or may not have been the right approach.
It does at least get a new error:

Generating file(s) ../README 
! I can't write on file `../README.tex'.

It appears to be trying to write its README file to the directory above
the build directory, which is failing. Is there a way to make this
directory writeable, or to stop the build system from trying to generate
the README there?

 gnu/packages/tex.scm | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gnu/packages/tex.scm b/gnu/packages/tex.scm
index c3ce80c8f5..0894148501 100644
--- a/gnu/packages/tex.scm
+++ b/gnu/packages/tex.scm
@@ -3249,7 +3249,8 @@ array environments; verbatim handling; and syntax diagrams.")
                (base32
                 "03ma58z3ypsbp7zgkzb1ylpn2ygr27cxzkf042ns0rif4g8s491f"))))
     (build-system texlive-build-system)
-    (arguments '(#:tex-directory "latex/polyglossia"))
+    (arguments '(#:tex-directory "latex/polyglossia"
+                 #:build-targets '("polyglossia.dtx")))
     (home-page "https://www.ctan.org/pkg/polyglossia")
     (synopsis "Alternative to babel for XeLaTeX and LuaLaTeX")
     (description
-- 
2.21.0

Message #11 received at 35780 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Josh Holland <josh <at> inv.alid.pw>
Cc: 35780 <at> debbugs.gnu.org
Subject: Re: bug#35780: [PATCH] attempt to fix polyglossia
Date: Sat, 18 May 2019 05:50:13 +0200

Hi Josh,

> I had a quick look into fixing this myself, and made a little bit
> of progress.  Not being that familiar with how things work yet,
> I'm going on what I can guess by looking at gnu/packages/tex.scm,
> guix/build-system/texlive.scm and guix/build/texlive-build-system.scm
> so I may well be misinterpreting some things.
>
> The source for polyglossia comes in a single file, polyglossia.dtx.
> The README embedded within it says to extract the files by running
> xetex or luatex on it.  I tried to convince the build system to do
> this by this patch, which may or may not have been the right approach.

Thanks for giving it a try.  The build system works on “ins” files by
default.  I guess it should try “dtx” files as well.

> It does at least get a new error:
>
> Generating file(s) ../README
> ! I can't write on file `../README.tex'.
>
> It appears to be trying to write its README file to the directory above
> the build directory, which is failing. Is there a way to make this
> directory writeable, or to stop the build system from trying to generate
> the README there?

We can patch the dtx file in a build phase and replace “../README” with
just “README”.  We can’t write to the parent of the build directory, and
extracting everything a level deeper seems wrong.

What do you think?

--
Ricardo

Message #14 received at 35780 <at> debbugs.gnu.org (full text, mbox):

From: Josh Holland <josh <at> inv.alid.pw>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: guix-devel <at> gnu.org, 35780 <at> debbugs.gnu.org
Subject: Re: bug#35780: [PATCH] attempt to fix polyglossia
Date: Fri, 21 Jun 2019 16:40:06 +0100

Hi,

(CCing guix-devel because I'm confused about this and more eyes can't
hurt)

On Sat, May 18, 2019 at 05:50:13AM +0200, Ricardo Wurmus wrote:
> Thanks for giving it a try.  The build system works on “ins” files by
> default.  I guess it should try “dtx” files as well.

Should this be a patch to the build-system?  Although maybe it's not
that simple: https://ctan.org/texarchive/macros/xetex/latex/polyglossia
lists four files, incuding an "ins" file.

> We can patch the dtx file in a build phase and replace “../README” with
> just “README”.

I tried patching the README path as Ricardo suggested.  This got
somewhere, complaining of missing fonts, so I added texlive-fonts-cm
to native-inputs.  With both these changes, the build now fails while
trying to build example-thai.tex, and the errors appear to indicate
trying to build a LaTeX file with plain TeX:

Processing file polyglossia.dtx (example-thai.tex) -> example-thai.tex
File polyglossia.dtx ended by \endinput.
Lines  processed: 11224
Comments removed: 1600
Comments  passed: 215
Codelines passed: 9209

! Undefined control sequence.
l.209 \documentclass
                  [11pt]{ltxdoc}
! Undefined control sequence.
l.210 \usepackage
               {color}
! Undefined control sequence.
l.211 \usepackage
               {xspace,fancyvrb}
! Undefined control sequence.
l.212 \usepackage
               [neverdecrease]{paralist}
! Undefined control sequence.
l.213 \definecolor
                {myblue}{rgb}{0.02,0.04,0.48}
! Undefined control sequence.
l.214 \definecolor
                {lightblue}{rgb}{0.61,.8,.8}
! Undefined control sequence.
l.215 \definecolor
                {myred}{rgb}{0.65,0.04,0.07}
! Undefined control sequence.

(and more...)

I'm not that familiar with the intricacies of properly building TeXLive
from source, but the difference between the file list on CTAN and what
comes from the Subversion repo via texlive-ref smells fishy to me.  If I
manually run any permutation of  `{xe,lua}tex polyglossia.{ins,dtx}`
it mostly seems to build OK, but to my surprise no polyglossia.sty
is produced!  There's no actual build instructions in the README or the
polyglossia.pdf, so I'm rather lost here.

Thanks,

-- 
Josh Holland

Message #19 received at 35780-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: guix-devel <at> gnu.org, 35780-done <at> debbugs.gnu.org
Subject: Re: bug#35780: texlive-latex-polyglossia package empty
Date: Sat, 14 May 2022 01:22:50 -0400

Hello,

The texlive-polyglossia is no longer empty, and works, at least with
XeLaTeX.  You can see it in action building the doc of our
'python-ipython-documentation' package.

Closing!

Thanks,

Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.