Bug 4818

Summary:	texlive-fontsextra install misses a texhash?
Product:	Mageia	Reporter:	Chris Denice <eatdirt>
Component:	RPM Packages	Assignee:	Malo Deniélou <pmdenielou>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	eeeemail, pmdenielou, pterjan, yurchor
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	MGA2TOO MGA3TOO
Source RPM:	texlive-texmf-20110705-5.mga2.src.rpm	CVE:
Status comment:

Description Chris Denice 2012-03-06 16:26:21 CET

Description of problem:

Using latex and dvips produced this error:
dvips: ! Couldn't find header file: texnansi.enc

of which an urpmf texnansi.enc reveals that texnansi.enc is now provided in texlive-fontsextra.

Installing texlive-fontsextra does not yet fix the pb, but logged as root, executing "/usr/bin/texhash" fixes the error

A fix would be to execute "texhash" as %post in the installation of texlive-fontsextra.

Also, although a suggest "texlive_fontsextra" may be welcome (if not done already) in the installation of texlive?


How reproducible:
having a latex file, or postcript using texnansi.enc font

Cheers,
Chris.

Manuel Hiebel 2012-03-07 00:02:10 CET

Assignee: bugsquad => dmorganec

Comment 1 Marja Van Waes 2012-05-26 13:09:23 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 2 Chris Denice 2012-05-26 16:37:04 CEST

My mistake, I have lost that file having tecnansi font so I cannot test it anymore.

If the texhash command has not been added, the bug is likely to be there however; maybe dmorgan can tell?

cheers,
Chris.

Comment 3 Yuri Chornoivan 2012-06-17 12:37:57 CEST

Testcase:

\documentclass[]{article}

\usepackage{texnansi}

\begin{document}

Test

\end{document}

Cannot be successfully compiled without additional texhash command after installing of texlive-fontsextra.

Keywords: NEEDINFO => (none)
CC: (none) => yurchor
Whiteboard: (none) => MGA2TOO

Comment 4 Marja Van Waes 2012-07-06 15:05:46 CEST

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Comment 5 Malo Deniélou 2013-08-22 14:05:48 CEST

I got that problem as well.

CC: (none) => pierre-malo.denielou

Malo Deniélou 2013-08-23 12:36:24 CEST

Status: NEW => ASSIGNED
Assignee: dmorganec => pierre-malo.denielou
Whiteboard: MGA2TOO => MGA2TOO MGA3TOO

Comment 6 Malo Deniélou 2013-08-23 14:48:54 CEST

*** Bug 8753 has been marked as a duplicate of this bug. ***

CC: (none) => pterjan

Comment 7 Malo Deniélou 2013-08-23 14:49:57 CEST

*** Bug 10330 has been marked as a duplicate of this bug. ***

CC: (none) => eeeemail

Comment 8 Malo Deniélou 2013-08-23 16:55:29 CEST

Fixed in svn.

Comment 9 Samuel Verschelde 2015-05-17 18:21:17 CEST

Closing as per comment #8

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