There is a large number of documents around that are maintained as latex files using (among others) the dvipdfm package. I have installed in Mageia4 the following rpms: ghostscript-dvipdf-9.10-2.mga4.x86_64 texlive-fontsextra-20130530-4.mga4.noarch texlive-texmf-20130530-4.mga4.noarch texlive-dist-20130530-4.mga4.noarch texlive-collection-basic-20130530-4.mga4.noarch texlive-20130530-8.mga4.x86_64 all together they seem to provide all needed styles, extensions, fonts etc... Except that dvipdfm.def is replaced by dvipdfmx.def. (see project.ktug.org/dvipdfmx/) The fact that dvipdfmx is better than dvipdfm is IMHO not sufficient to remove dvipdfm.def from the distribution. It looks more like a break in backwards compatibility and a big nuisance since in every document or custom style requiring dvipdfm one now needs to replace the string 'dvipdfm' with the string 'dvipdfmx' just to have the latex compilation working! So, please, bring back dvipdfm.def and good ole dvipdfm & ebb utilities. Note that a soft link dvipdfm.def->dvipdfmx.def will be more or less sufficient, except that in this case 'ebb' should be called as 'ebb -x'.
Assignee: bugsquad => pierre-malo.denielou
Hi, After some additional research it seems to me that 'old dvipdfm' is packaged apart in other distros (google search texlive-dvipdfm). Which seems sensible.
Hi Gilles, Yes, I will try to package it separately as well. We updated texlive from mga3, and every release some things come in and out, and it's not easy to spot them all :-).
Status: NEW => ASSIGNED
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: ASSIGNED => RESOLVEDResolution: (none) => OLD