Bug 73170 - Updated teTeX port build probles, can't find ushyphen.tex
Summary: Updated teTeX port build probles, can't find ushyphen.tex
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Hiroki Sato
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-26 18:30 UTC by Nick Christenson
Modified: 2004-10-30 18:57 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Christenson 2004-10-26 18:30:15 UTC
	The teTeX port seems to have been updated on October 25, 2004.
	The only non-default option used was that when updating the port
	I selected US "letter" paper size.
	When running "portupgrade -rR teTeX" the build of the port fails.
	The output of this command captured by "script" is attached.  Note 
	that at "Please type another input file name:" it pauses for input.  
	I have not modfied any of the existing TeX installation files.
	The file "ushyphen.tex" appears nowhere on my system.

	script output of the portupgrade command:
Script started on Tue Oct 26 09:58:41 2004
prometheus# portupgrade -rR teTeX
--->  Upgrading 'teTeX-2.0.2_5' to 'teTeX-2.0.2_6' (print/teTeX)
--->  Building '/usr/ports/print/teTeX'
===>  Cleaning for libiconv-1.9.2_1
===>  Cleaning for gettext-0.13.1_1
===>  Cleaning for gmake-3.80_2
===>  Cleaning for imake-4.4.0
===>  Cleaning for libtool-1.3.5_2
===>  Cleaning for libtool-1.5.10
===>  Cleaning for pkgconfig-0.15.0_1
===>  Cleaning for t1lib-5.0.1,1
===>  Cleaning for png-1.2.7
===>  Cleaning for perl-5.8.5
===>  Cleaning for dvipsk-tetex-5.92b_1
===>  Cleaning for freetype2-2.1.7_3
===>  Cleaning for teTeX-base-2.0.2_2
===>  Cleaning for teTeX-latex2e-1.0.20031201
===>  Cleaning for teTeX-texmf-2.0.2_1
===>  Cleaning for tex-texmflocal-1.5
===>  Cleaning for xdvik-tetex-22.78_2
===>  Cleaning for expat-1.95.8
===>  Cleaning for libwww-5.4.0_1
===>  Cleaning for fontconfig-2.2.3,1
===>  Cleaning for XFree86-libraries-4.4.0_1
===>  Cleaning for teTeX-2.0.2_6
===>  Vulnerability check disabled
===>  Found saved configuration for teTeX-2.0.2_4
===>  Extracting for teTeX-2.0.2_6
===>  Patching for teTeX-2.0.2_6
===>  Configuring for teTeX-2.0.2_6
/usr/bin/sed -e s!%%TETEX_MODESW%%!/usr/local/bin/tetex-modesw!g -e s!%%MODE%%!tetex!g  < /usr/ports/print/teTeX/files/pkg-install.in > /usr/ports/print/teTeX/work/pkg-install.sh
/bin/chmod 0755 /usr/ports/print/teTeX/work/pkg-install.sh
===>  Building for teTeX-2.0.2_6
--->  Backing up the old version
--->  Uninstalling the old version
--->  Deinstalling 'teTeX-2.0.2_5'
[Updating the pkgdb <format:bdb1_btree> in /var/db/pkg ... - 356 packages found (-1 +0) (...) done]
--->  Installing the new version via the port
===>  Installing for teTeX-2.0.2_6
===>   teTeX-2.0.2_6 depends on file: /usr/local/bin/tetex-modesw - found
===>   teTeX-2.0.2_6 depends on file: /usr/local/share/texmf/LICENSE.texmf - found
===>   teTeX-2.0.2_6 depends on executable: latex - found
===>   teTeX-2.0.2_6 depends on file: /usr/local/share/texmf-local/tex/latex/base/latex.ltx - not found
===>    Verifying reinstall for /usr/local/share/texmf-local/tex/latex/base/latex.ltx in /usr/ports/print/teTeX-latex2e
===>  Vulnerability check disabled
===>  Extracting for teTeX-latex2e-1.0.20031201

Fix: 

Off the top of my head, I don't know how to fix this problem.  I've
	got some ideas how to kludge it, but that's no good.
How-To-Repeat: 	portupgrade -rR teTeX
Comment 1 Pav Lucistnik freebsd_committer freebsd_triage 2004-10-27 19:58:18 UTC
Responsible Changed
From-To: freebsd-ports-bugs->hrs

Over to maintainer.
Comment 2 Hiroki Sato freebsd_committer freebsd_triage 2004-10-28 18:57:02 UTC
State Changed
From-To: open->feedback

A fix has been committed.  Could you please try the latest ports and 
let me know if it works properly?  Thanks!
Comment 3 Hiroki Sato freebsd_committer freebsd_triage 2004-10-30 18:56:43 UTC
State Changed
From-To: feedback->closed

This problem has been fixed.  Thank you for the report!