From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josh Holland Subject: bug#35780: [PATCH] attempt to fix polyglossia Date: Fri, 21 Jun 2019 16:40:06 +0100 Message-ID: <20190621154006.GA7268@sirius.localdomain> References: <20190517165152.GA5797@spica.localdomain> <20190517212351.8855-1-josh@inv.alid.pw> <87y334ctfu.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:60309) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heLez-0000te-PQ for bug-guix@gnu.org; Fri, 21 Jun 2019 11:41:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1heLex-0006dG-OT for bug-guix@gnu.org; Fri, 21 Jun 2019 11:41:05 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:37080) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1heLew-0006bx-I5 for bug-guix@gnu.org; Fri, 21 Jun 2019 11:41:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1heLew-0001Ai-Cn for bug-guix@gnu.org; Fri, 21 Jun 2019 11:41:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87y334ctfu.fsf@elephly.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ricardo Wurmus Cc: guix-devel@gnu.org, 35780@debbugs.gnu.org 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