Bug 25781 - jadetex missing fmt files
Summary: jadetex missing fmt files
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2019-11-29 02:52 CET by Bruno Cornec
Modified: 2020-12-29 11:31 CET (History)
4 users (show)

See Also:
Source RPM: jadetex-3.13-14.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Bruno Cornec 2019-11-29 02:52:35 CET
Description of problem:

Trying to build a pdf from an sgml file fails (again)

Version-Release number of selected component (if applicable):

jadetex 1.13-14

How reproducible:

Every time

Steps to Reproduce:
1. urpme texlive
2. rm -rf /usr/share/texmf/web2c
3. urpmi docbook-utils-pdf
4. docbook2pdf -d mondorescue-howto.dsl'#pdf' mondorescue-howto.sgml (or whatever sgml file) fails
mktexfmt [INFO]: --- remaking pdfjadetex with pdftex
mktexfmt: running `pdftex -ini   -jobname=pdfjadetex -progname=pdfjadetex *pdfjadetex.ini' ...
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018/Mageia) (INITEX)
 restricted \write18 enabled.
entering extended mode
(/usr/share/texmf-dist/tex/jadetex/pdfjadetex.ini
(/usr/share/texmf-dist/tex/jadetex/jadetex.ltx
! Undefined control sequence.
l.9 \NeedsTeXFormat
                   {LaTeX2e}[1995/06/01]
? 
! Emergency stop.
l.9 \NeedsTeXFormat
                   {LaTeX2e}[1995/06/01]
No pages of output.
Transcript written on pdfjadetex.log.
mktexfmt [ERROR]: running `pdftex -ini   -jobname=pdfjadetex -progname=pdfjadetex *pdfjadetex.ini >&2 </dev/null' return status 1
mktexfmt [ERROR]: return error due to options --strict
mktexfmt [INFO]: Disabled formats: 6
mktexfmt [INFO]: Not selected formats: 43
mktexfmt [INFO]: Failed to build: 1 (pdftex/pdfjadetex)
mktexfmt [INFO]: Total formats: 50
mktexfmt [INFO]: exiting with status 1
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018/Mageia) (preloaded format=pdfjadetex)
 restricted \write18 enabled.
I can't find the format file `pdfjadetex.fmt'!
Comment 1 Bruno Cornec 2019-11-29 02:53:25 CET
This is very similar to an issue I had back in mga1 time: https://bugs.mageia.org/show_bug.cgi?id=1538 and that someone else also had with mga4: https://bugs.mageia.org/show_bug.cgi?id=12069
Comment 2 Bruno Cornec 2019-11-29 02:55:08 CET
Note that the fix I found back in mga1 is still working:

ln -sf /usr/share/texmf-dist/web2c/etex/jadetex.fmt /usr/share/texmf-dist/web2c
ln -sf /usr/share/texmf-dist/web2c/pdfetex/pdfjadetex.fmt /usr/share/texmf-dist/web2c
docbook2pdf -d mondorescue-howto.dsl'#pdf' mondorescue-howto.sgml 
Using catalogs: /etc/sgml/sgml-docbook-4.1.cat
Using stylesheet: /users/bruno/mondo/svn/branches/3.3/mondo-doc/mondorescue-howto.dsl#pdf
Working on: /users/bruno/mondo/svn/branches/3.3/mondo-doc/mondorescue-howto.sgml

So I'd recommend adding a test in the spec file so that if the target file do not exists, we use the ln commands upper.
David Walser 2019-11-29 15:43:50 CET

Summary: missing fmt files => jadetex missing fmt files

Comment 3 Lewis Smith 2019-11-29 21:21:05 CET
Thank you Bruno for the report and a solution.

Assigning to neoclust as the registered maintainer, in the absence of any recent involvement by others.

Source RPM: jadetex => jadetex-3.13-14.mga7.src.rpm
Assignee: bugsquad => mageia

Comment 4 Jani Välimaa 2019-12-01 18:46:32 CET
Pushed updated jadetex-3.13-14.1.mga7 to core/updates_testing. Please test.

Creating .fmt files in %post was broken. It's now fixed, but I'm wondering why we even create .fmt files in %post as they're created during the build already..

CC: (none) => jani.valimaa
Assignee: mageia => qa-bugs

Comment 5 Thomas Andrews 2019-12-21 23:27:14 CET
I had hoped that the reporter would give this a test to see if his issue was resolved, but as it hasn't happened I thought I'd see what I could do. 

It seemed simple enough - until I went looking for an sgml file. Our mondo package contains Rescue howto files in html and pdf, but not sgml. Looking at the Mondo Rescue web page, I see that they don't have the sgml format for download, either. I also see that the reporter is one of the Mondo developers, so that explains where he found his example, but not, of course, where I am to find mine.

So I looked at Bug 1538, where I found that Claire Robinson (Mrs.B) ran into the same problem. She tried "Configuration.sgml" frpm the proftpd package, with little to no success. If Claire couldn't get anywhere I don't know how I would, but I continued anyway. I installed that, and tried the same thing she did, getting nowhere either before or after updating jadetex. The errors I saw were nothing like those in Comment 0, and indicated quite profoundly that I didn't know what I was doing.

I looked elsewhere, but didn't find anything that could help. So I'm stuck. I could pass this on a clean install, but that's it. So this is going to have to wait for someone who knows something to come along before anything more happens.

CC: (none) => andrewsfarm

Comment 6 Thomas Andrews 2020-01-04 16:59:43 CET
It's been two weeks, and no one has stepped up. So, OKing this on the basis of a clean install, and validating.

Whiteboard: (none) => MGA7-64-OK
CC: (none) => sysadmin-bugs
Keywords: (none) => validated_update

Thomas Backlund 2020-01-05 15:26:25 CET

Keywords: (none) => advisory
CC: (none) => tmb

Comment 7 Mageia Robot 2020-01-05 16:39:27 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0004.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 8 Bruno Cornec 2020-12-29 11:31:31 CET
Sorry, I missed the updates for this BR :-(

FTR, the source is available at http://trac.mondorescue.org/browser/MondoRescue/branches/3.3/mondo-doc/mondorescue-howto.sgml and will be delivered as part of an upcoming mondo-doc package update. (dsl at the same place)

And I can confirm that the fix is indeed working !

Note You need to log in before you can comment on or make changes to this bug.