Arch Linux

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!
Tasklist

FS#22930 - [latex2html] url.sty shadows texlive-core's url.sty

Attached to Project: Arch Linux
Opened by Andrzej Staniek (cmdr_pain) - Thursday, 17 February 2011, 20:16 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Monday, 25 April 2011, 17:06 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
latex2html includes /usr/share/texmf/tex/latex/html/url.sty
which is used by pdflatex instead of /usr/share/texmf-dist/tex/latex/url/url.sty, which results in unexpected document output (see 'Steps to reproduce').
latex2html is NOT used.
Removing latex2html with pacman results in expected output of the latex
typesetter.

You may look at the debian bug report for a different/clearer explanation.

Additional info:
* package version: latex2html-2008-1


Steps to reproduce:
install:
texlive-bibtexextra
latex2html

Use a simple latex example from e.g(the biblatex one):
http://win.ua.ac.be/~nschloe/content/bibtex-how-cite-website
Then issue:
pdflatex -interaction=batchmode test.tex
bibtex test.aux
pdflatex -interaction=batchmode test.tex
pdflatex -interaction=batchmode test.tex

Open the the resulting pdf, you don't even need to see the log.

See the debian bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589702
for the same issue and its fix (i.e. removing the offending url.sty file from latex2html)
This task depends upon

Closed by  Rémy Oudompheng (remyoudompheng)
Monday, 25 April 2011, 17:06 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 2008-2
Comment by Andrzej Staniek (cmdr_pain) - Thursday, 17 February 2011, 20:18 GMT
btw is the 'high' severity level appropriate for this type of bug ?

Loading...