Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#79715 - [texlive-langspanish] Some hooks not triggering causes this package to be unusable
Attached to Project:
Arch Linux
Opened by Sergio (bungow) - Sunday, 17 September 2023, 07:45 GMT
Last edited by Antonio Rojas (arojas) - Monday, 18 September 2023, 17:58 GMT
Opened by Sergio (bungow) - Sunday, 17 September 2023, 07:45 GMT
Last edited by Antonio Rojas (arojas) - Monday, 18 September 2023, 17:58 GMT
|
DetailsDescription:
When installing this package and configuring a latex document to use "catalan" language, babel warns that language catalan does not exist. After running /usr/bin/fmtutil-sys --all manually the language is found. Some others packages, like textlive-langpolish seems to trigger this hook. So maybe people that install more language packages don't have this issue. Additional info: texlive-langspanish 2023.66594-19 Steps to reproduce: 1. Install only texlive-langspanish from texlive-lang group. 2. Create a latex document using "\usepackage[catalan]{babel}" 3. Try to compile, and get the following error: /usr/share/texmf-dist/tex/generic/babel/babel.sty|4373 error| Package babel Error: Unknown option 'catalan'. Either you misspelled it or the language definition file catalan.ldf was not found. 4. Run sudo /usr/bin/fmtutil-sys --all 6. Compile again the latex file and there is no error. |
This task depends upon
Closed by Antonio Rojas (arojas)
Monday, 18 September 2023, 17:58 GMT
Reason for closing: Works for me
Monday, 18 September 2023, 17:58 GMT
Reason for closing: Works for me
First and foremost, I want to express my gratitude for your dedication in maintaining these packages.
My pacman logs don't report any errors while installing the package. I can reproduce this in my two computers.
On my side to reproduce this issue I remove the complete texlive-lang group and then I run sudo /usr/bin/fmtutil-sys --all (to ensure this thing regenerate. As I'm a newcomer to latex, I don't understand what this does exactly)
then i install only the spanish lang and babel throws the error. To solve, I have to run sudo /usr/bin/fmtutil-sys --all again.
The thing is this command takes some time to execute, and while I see this time while installing e.g. texlive-langpolish, the installation of spanish package is much faster so I'm sure the fmtutil is not running during install.
*Relevant pacman log
[2023-09-17T09:30:29+0200] [PACMAN] Running 'pacman -S texlive-langspanish'
[2023-09-17T09:30:30+0200] [ALPM] transaction started
[2023-09-17T09:30:30+0200] [ALPM] installed texlive-langspanish (2023.66594-19)
[2023-09-17T09:30:30+0200] [ALPM] transaction completed
[2023-09-17T09:30:30+0200] [ALPM] running '30-systemd-update.hook'...
[2023-09-17T09:30:30+0200] [ALPM] running '70-mktexlsr.hook'...
[2023-09-17T09:30:32+0200] [ALPM] running '71-texlive-language.hook'...
[2023-09-17T09:30:32+0200] [ALPM] running '90-packagekit-refresh.hook'...
$ cat babel.tex
\documentclass{article}
\usepackage[catalan]{babel}
\begin{document}
\end{document}
- Completely uninstalled texlive: pacman -Rdd texlive texlive-lang
- Wiped all config and cache files: rm -fr /var/lib/texmf ~/.texlive
- Reinstalled texlive: pacman -S texlive-meta
- Ran 'latex babel.tex': fails as expected with "! Package babel Error: Unknown option 'catalan'"
- Installed texlive-langspanish
- Ran 'latex babel.tex': succeeds.
I noticed that this issue also appears in the container. When I remove the Spanish package, I can still compile in Catalan language. Do these packages leave some configurations in the system when removed?
P.S.: I used a full TeX file to test, with the same results. In a fresh install, this issue doesn't arise.