getnonfreefonts fetches the wrong year's script from tug.org

Bug #394780 reported by dhn
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
texlive-extra (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: texlive-base-bin

The getnonfreefonts and getnonfreefonts-sys script have a variable set to retrieve the appropriate getfonts<year> script from tug.org. In the current jaunty version, this is set to 2007, which causes e.g. 'getnonfreefonts garamond' to fail due to changes in the organization of CTAN.

Attached diff will fix it.

$ dpkg --status texlive-base-bin
Package: texlive-base-bin
Status: install ok installed
Priority: optional
Section: tex
Installed-Size: 8752
Maintainer: Ubuntu Core Developers <email address hidden>
Architecture: i386
Source: texlive-bin
Version: 2007.dfsg.2-4ubuntu2
<...>

Revision history for this message
dhn (ubuntu-neilson) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

Looking at the attachments in this bug report, I noticed that "getnonfreefonts.patch" was not flagged as a patch. A patch contains changes to an Ubuntu package that will resolve a bug and this attachment is one! Subsequently, I've checked the patch flag for it. In the future when submitting patches please use the patch checkbox as there are some Launchpad searches that use this feature. You can learn more about patch workflow at https://wiki.ubuntu.com/Bugs/Patches. Thanks for your contribution dhn!

Changed in texlive-bin (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Philip Muškovac (yofel) wrote :

getnonfreefonts is now part of texlive-extra-utils, so changing package. Also, in 2009-7ubuntu3 it downloads
ftp://tug.org/tex/getnonfreefonts/getfont2009
so this bug is fixed in lucid. Thank you for taking your time to report this bug and submitting your patch, please report any other bugs you may find.

affects: texlive-bin (Ubuntu) → texlive-extra (Ubuntu)
Changed in texlive-extra (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.