Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 120319 - tetex-3.0_p1-r1 does not install latex
Summary: tetex-3.0_p1-r1 does not install latex
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Text-Markup Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 124511
  Show dependency tree
 
Reported: 2006-01-25 09:49 UTC by Diego Chantrain
Modified: 2006-04-13 13:20 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Files installed by the ebuild (output.log.bz2,37.69 KB, application/x-bzip)
2006-01-25 13:27 UTC, Diego Chantrain
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Chantrain 2006-01-25 09:49:46 UTC
After emerging tetex-3.0_p1-r1, I cannot find latex. It is not in /usr/bin.


emerge info:

Portage 2.1_pre3-r1 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.6-r2, 2.6.15-suspend2-r4 i686)
=================================================================
System uname: 2.6.15-suspend2-r4 i686 Intel(R) Pentium(R) M processor 1500MHz
Gentoo Base System version 1.12.0_pre15
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1-r1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium3 -msse2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/texmf/web2c /etc/env.d"
CXXFLAGS="-O2 -march=pentium3 -msse2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo ftp://mirr
h.ch/mirror/gentoo/ ftp://ftp.solnet.ch/mirror/Gentoo"
LC_ALL="en_US.utf8"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X a52 aac acpi alsa apm asf audiofile avi berkdb bitmap-fonts bluetooth browserplugin bzip2 cairo cddb cdparanoia cdr cdrom crd crypt css cups dbus dvd dvdr dvdread dvi ed
 encode esd exif expat fam firefox flac foomaticdb fortran gdbm gif glut gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml hal id3 idn imlib ipod ipv6 java jpeg junit lcms libg++ libwww
te mad maildir matroska mikmod mmx mng mono motif mp3 mpeg mplayer musicbrainz nautilus ncurses nls ntfs offensive ogg oggvorbis on-the-fly-crypt opengl oss pam pcre pdf pdflib per
thon qt quicktime rar readline real samba scanner sdl spell sse2 ssl tcpd tetex tiff transcode truetype truetype-fonts type1-fonts udev unicode usb utf8 visualization vorbis win32c
a wmf xfs xine xinerama xml2 xmms xscreensaver xv zlib elibc_glibc kernel_linux userland_GNU"
Unset:  ASFLAGS, CTARGET, LANG, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Comment 1 Martin Ehmsen (RETIRED) gentoo-dev 2006-01-25 11:10:48 UTC
Could you try to re-emerge tetex.
If that does not help, then give us the list of files that are installed (the output at the end of the emerge).
Comment 2 Diego Chantrain 2006-01-25 13:27:22 UTC
Created attachment 78101 [details]
Files installed by the ebuild

Re-emerging does not seem to solve the problem. Here is the relevant part of the emerge log.
Comment 3 Alexandre Buisse (RETIRED) gentoo-dev 2006-01-26 02:07:00 UTC
As a quick fix, make a symlink from /usr/bin/latex to /usr/bin/pdfetex, as this is what the ebuild should do anyway.

There is dark symlink magic going on in the tetex eclasses, I'll try to see what causes that.

Comment 4 Martin Ehmsen (RETIRED) gentoo-dev 2006-02-09 03:24:15 UTC
Could you try the new -r2 and see if your problem is fixed in that?
Comment 5 Diego Chantrain 2006-03-01 04:22:11 UTC
I have latex now with the -r2. Works for me. Thanks.
Comment 6 Martin Ehmsen (RETIRED) gentoo-dev 2006-03-07 02:56:00 UTC
I don't know what to think of this.
The modifications from -r1 to -r2 should not imho have had any effect on the latex binary being installed.

@nattfodd: What do you think of this?
Comment 7 Alexandre Buisse (RETIRED) gentoo-dev 2006-03-07 09:16:57 UTC
Nothing more than in comment #3: there is symlink dark magic going on. Maybe you commited -r2 on a full moon day?
Comment 8 Tobias Hahn 2006-04-12 04:19:14 UTC
I works for me neither with -r2 nor with -r3. I agree on the dark magic.
Comment 9 Martin Ehmsen (RETIRED) gentoo-dev 2006-04-13 07:31:56 UTC
(In reply to comment #8)
> I works for me neither with -r2 nor with -r3. I agree on the dark magic.

Do you mean that it works or that it does not work?
Comment 10 Martin Ehmsen (RETIRED) gentoo-dev 2006-04-13 11:58:15 UTC
Could you with missing latex symlink please try running
texlinks --multiplatform
and report back if that works.
Comment 11 Martin Ehmsen (RETIRED) gentoo-dev 2006-04-13 13:20:09 UTC
I have finally figured this one out!
It is texmf-update script which calls texconfig-sys init which in turn calls texlinks --multiplatform which creates the symlinks for latex and is relatives which all uses pdfetex.
That explains why it was fixed by upgrading from -r1 to -r2 and why so few users has been hit by this.
Upgradning from -r1 to -r2 fixes it, because it (re)introduces the call to texmf-update which accidently was removed (in an attempt to fix elatex, bug 98029).
The reason so few users has seen this bug is because if they at one time has had the symlink from pointing latex to pdfetex then it wont disappear when unemering/upgrading tetex (since the symlink was created by texmf-update after the qmerge phase, so portage doesn't record it). Hence only users which emerge the -r1 revision from a scratch system would be hit, not users upgrading to -r1.

I'm going to close it now since i'm convinced that it is fixed. If it's not, feel free to reopen.