Bug 3340

Hi, thanks for reporting this bug.
As there is no maintainer for this package I had the committers in CC.

Keywords: (none) => PATCH, Triaged, UPSTREAM
CC: (none) => ahmadsamir3891, boklm
Source RPM: (none) => latex2html

(In reply to comment #1)
> Hi, thanks for reporting this bug.
> As there is no maintainer for this package I had the committers in CC.

adding two more committers, removing one

CC: ahmadsamir3891 => eandry, mageia, marja11

Created attachment 1806 [details]
Fix for the latex2html image problem.

The attachment is a patch which fixes this bug.  The problem is that in Mageia, the l2hconf.pm is not properly configured!  All changes are below the line:

####### YOU *MAY* WANT/NEED TO CHANGE SOME OF THESE VARIABLES  ##############

I have compared the Mandriva 2010.0 file with the Mageia one, and the patch is the result of me updating the Mageia file with both my own change (the PDF option) and Mandriva's configuration (PNG and GIF).  So it now has support for images (PNG and GIF) and the PDF option is removed.  I would recommend this change as a fix for Mageia 1 and to be included as part of Mageia 2.

Note there are other Latex2html files with changes between Mandriva 2010.0 and Mageia 1, despite both using the same Latex2html version.  These include /usr/lib/latex2html/cfgcache.pm and /usr/lib/latex2html/docs/manual.cb, as well as a number of files only present in Mandriva:

Only in /mnt/mandriva_usr/lib/latex2html/docs: features.ptr
Only in /mnt/mandriva_usr/lib/latex2html/docs: hypextra.ptr
Only in /mnt/mandriva_usr/lib/latex2html/docs: manual.aux
Only in /mnt/mandriva_usr/lib/latex2html/docs: manual.dvi
Only in /mnt/mandriva_usr/lib/latex2html/docs: manual.glo
Only in /mnt/mandriva_usr/lib/latex2html/docs: manual.idx
Only in /mnt/mandriva_usr/lib/latex2html/docs: manual.lof
Only in /mnt/mandriva_usr/lib/latex2html/docs: manual.log
Only in /mnt/mandriva_usr/lib/latex2html/docs: manual.lot
Only in /mnt/mandriva_usr/lib/latex2html/docs: manual.pdf
Only in /mnt/mandriva_usr/lib/latex2html/docs: manual.ps
Only in /mnt/mandriva_usr/lib/latex2html/docs: manual.toc
Only in /mnt/mandriva_usr/lib/latex2html/docs: overview.ptr
Only in /mnt/mandriva_usr/lib/latex2html/docs: problems.ptr
Only in /mnt/mandriva_usr/lib/latex2html/docs: support.ptr
Only in /mnt/mandriva_usr/lib/latex2html/docs: userman.ptr

Ok, there is more to this bug than just the l2hconf.pm change.  The /usr/bin/latex2html file and cfgcache.pm files also need changing to enable image support, though this also appears to not be enough.  From these files, it looks like there is a config.pl file in the sources (/home/iurt/rpm/BUILD/latex2html-2008), and from this the PNG and GIF support needs to be enabled.  This requires investigation of the srpm file.

I have now built the SRPM file from ftp://ftp5.gwdg.de/pub/linux/mageia/distrib/1/SRPMS/core/release/latex2html-2008-4.mga1.src.rpm and have a perfectly working installation of latex2html!  The build created almost exactly the same files as the Mandriva 2010.0 distribution, except for the DVIPSOPT -Ppdf option.  Was netpbm RPM installed on the build machine?  Maybe the following should be added to the SPEC file:

BuildRequires:	netpbm

I still also recommend changing the /usr/lib/latex2html/l2hconf.pm file option:

$DVIPSOPT = '  -Ppdf  -E';

to:

$DVIPSOPT = '  -E';

This change is essential to remove black lines appearing underneath all images (e.g. see http://einstein.drexel.edu/liki/index.php/Latex2html) and is a very well known bug.

One last problem is that the build process (during configuration) is complaining about the 'ghostscript library' which I cannot find in the Mageia RPMs:

...
checking if dvips supports the combination of -E and -i -S 1... yes
checking for html4-check... no
checking for /usr/bin/gs... /usr/bin/gs
checking for ghostscript version... 9.02
checking for ghostscript portable bitmap device... pnmraw
checking for full color device for anti-aliasing... ppmraw
checking for ghostscript library and font paths... no
Warning: Could not determine GS_LIB path.
         Ghostscript may not work due to missing startup files.
         You need to set the value of GS_LIB manually in cfgcache.pm.
Hint:    Search for the file 'gs_init.ps'. This directory and the 'fonts'
         directory (usually same level) should be set in GS_LIB.
         Separate the entries with the ":" character. The current
         directory "." should be included, too.
...

But this does not seem to be needed.  I cannot find the 'gs_init.ps' file anywhere in the Mageia RPMs.  Is Ghostscript configured properly?

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

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

This bug is still alive and present in Mageia 3.  Please reopen.

Version: 1 => 3
Source RPM: latex2html-2008-4.mga1 => latex2html-2008-7.mga3

The following fixes the problem, for any users affected:

1)  Download the Mageia 3 latex2html-2008-7.mga3.src.rpm file (for example at ftp://ftp5.gwdg.de/pub/linux/mageia/distrib/3/SRPMS/core/release/latex2html-2008-7.mga3.src.rpm).

2)  Install netpbm, lib64netpbm11, lib64netpbm-devel (or libnetpbm11 and libnetpbm-devel for 32-bit systems) through the control centre.  Other devel packages may be required.

3)  Run the following as root:

# rpmbuild --rebuild latex2html-2008-7.mga3.src.rpm
# urpmi /root/rpmbuild/RPMS/noarch/latex2html-2008-7.mga3.noarch.rpm

Done!  Latex2html now runs.

Created attachment 4247 [details]
Using the superior Debian patchset.

I would also highly recommend to use the patches from the Debian source files at http://packages.debian.org/ru/source/sid/latex2html rather than the patch set in the Mageia SRPM file, as these are far better.  For example the patches/fix-mathend-mark.patch file in http://ftp.de.debian.org/debian/pool/main/l/latex2html/latex2html_2008-debian1-10.debian.tar.gz removes the annoying mathend000# appearing throughout the document.

The attached file is an alternative solution to get latex2html to a reasonable state on your system.  It will download the Debian packages, unpack them, and apply the patches to the sources in the build/ directory.  First uninstall latex2html.  Then to install this into /usr/local, run:

$ cd build
$ ./configure --prefix=/usr/local
$ make

Finally as root:

# make install

This bug is still present in Mageia 4.  Until the source RPM is patched, this will go nowhere.

Sorry, this bug does not require patching, just a correct build as mentioned in comment #9.  The patching, especially including the Debian ones, would simply fix a pile of other issues.  This rebuild fix is insanely trivial, why can this not be resolved?

Here is how to quickly reproduce this bug on Mageia 1, Mageia 2, Mageia 3, Mageia 4, and Cauldron:

1.  Create a test LaTeX file:

$ touch bad_build.tex

2.  Run:

$ latex2html bad_build.tex


Please reopen this bug report!

I use latex2html to generate HTML documentation for software I am the lead developer of, this can be seen at http://www.nmr-relax.com/manual/index.html.  Therefore I have a strong interest in keeping latex2html functional in Mageia.

You could have reopen this bug yourself then.

By the way, maybe you can become packager, as there is no maintainer, and as all committer are no active. 

Or try by yourself to found someone. 

Unfortunately I don't have competence to resolve so easy bugs, but also don't know what to do if there is no commiters, no maintainer, etc, and I'm sorry for that.

Keywords: (none) => Junior_job
Status: RESOLVED => REOPENED
Resolution: WONTFIX => (none)
Assignee: remco => bugsquad

Does the Mageia team have an introductory document to use as a reference to get people into the system?  Is there a policy and framework for this?

Sure, iirc it's this page, https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

You can also write a mail to the dev mailing https://ml.mageia.org/l/info/dev/

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: REOPENED => RESOLVED
Resolution: (none) => OLD