After updating from app-text/tetex-1.0.7-r12 to app-text/tetex-2.0 the following entries from pkg_postinst all fail: exconfig init &>/dev/null texconfig confall &>/dev/null texconfig font vardir /var/cache/fonts &>/dev/null The error message is in all cases: "Could not find default config file for divpdfm (config). The program will exit now." Either tetex-2.0 is missing a config file are a dependency on divpdfm (which I had not installed). After installing divpdfm, most part of the pgk_postinst script works. But 'texconfig font vardir /var/cache/fonts' still errors out with: cp: `/usr/share/texmf/dvipdfm/config/config' and `/usr/share/texmf/dvipdfm/config/config' are the same file /usr/share/texmf/web2c/mktexupd: /usr/share/texmf/dvipdfm/config not a file.
One more comment: /usr/share/texmf/dvipdfm/config is not a file but a directory. # ls /usr/share/texmf/dvipdfm/config cmr.map config lw35urwa.map lw35urw.map psbase14.map t1fonts.map
Interesting. Could you try unmerging tetex-1.0.7-r12 and then merging tetex-2.0? I wonder if this is an upgrade issue.
Also, what are your USE? We might have to work through USE problems with the new version...
He is my USE value: x86 oss apm arts avi encode jpeg kde libg++ mikmod mpeg ncurses nls pdflib qtmt quicktime spell xmms xv zlib gdbm berkdb slang readline tetex svga tcltk java sdl gpm libwww ssl perl python imlib gnome qt motif cdr 3dnow alsa crypt cups doc dvd esd gif gtk gtk2 imap lcms maildir mmx mozilla oggvorbis opengl pam png sse tcpd tiff truetype X xml2 I will post the results of unmerging/emerging later.
It seems to be an update issue. I unmerged both tetex and dvipdfm and emerged tetex-2.0. No error.
Same problem here. I don't have dvipdfm installed (nor do I have any need for it). (The installation has apparently completed.) Here is my "emerge info". (make.conf contains: USE="X gtk gnome cups tcltk".) I get the same error when I try to run "texconfig font rw". Biggest pain for this emerge problem is that error message is popped up under curses and blocks the build process until you hit "enter". But, on the positive side, the man pages are installed in the right place, and everything appears to be running ok. phil Portage 2.0.46-r9 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r3) ================================================================= System uname: 2.4.20-gentoo-r1 i686 AMD Athlon(tm) Processor GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm avi crypt encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png qtmt quicktime spell truetype xml2 xmms xv zlib alsa gdbm berkdb slang readline arts tetex svga java guile mysql sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis qt kde motif opengl mozilla cdr X gtk gnome cups tcltk" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon -O3 -pipe" CXXFLAGS="-march=athlon -O3 -pipe" ACCEPT_KEYWORDS="x86 ~x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
Ok, I'm working on a solution. Should have it implemented soon enough.
Ok, the problem was in the installation phase. What happened was that the installation wanted to overwrite what was previously a directory (/usr/share/texmf/dvipdfm/config) with what is now a file. So the distribution of files got a bit fuddled up, and confused texconfig. I've fixed this in the tetex-2.0 ebuild; if you want to test it out, try: # emerge rsync ; emerge unmerge tetex ; emerge "=tetex-1.0.7-r12" ; emerge -u tetex And let me know if it doesn't work. I've tested this a couple times, and I'm fairly sure that it does indeed work. If it doesn't, feel free to reopen -- but for now, I'm closing. :)
This build failed for me. The difference is that I did not have divpdfm installed and tetex was looking for it and failing with an error. Maybe it should be a requirement?
tetex-2.0 comes with dvipdfm. What happens is this: tetex-1.0.7-r12 installs the directory /usr/share/texmf/dvipdfm/config IF you install dvipdfm, it installs files into /usr/share/texmf/dvipdfm/config and /usr/share/texmf/dvipdfm When upgrading to tetex-2.0, first it builds tetex-2.0, which includes dvipdfm. Then it installs to an image directory, which is then merged into the live filesystem. Then tetex-1.0.7 is removed -- portage typically does this very intelligently, but it let us down in this case where a directory changed to a file. When tetex-2.0 tries to copy the *file* config to /usr/share/texmf/dvipdfm it copies it instead to /usr/share/texmf/dvipdfm/config/config . Then when texconfig init looks for it, it gives an error. Please copy and paste the exact error. If it says it can't find the defaults file for dvipdfm, this is the problem -- it's a directory, not a file. Did you emerge rsync before testing the new build?
The problem you describe in comment #10 bit me as well. Won't this get everybody that updates from 1.0.7 to 2.0.0?
Actually, when I hit this bug, the config file is missing completely. No directory, no file. I suspect remerging will fix the problem for me... (testing)
No, it shouldn't bite everyone any more. I committed changes about 24 hours ago to conditionally remove that directory. I'm going to bump the revision in a little while, and that revision will contain this fix as well (obviously.)
Is this still an issue for anyone?
I can no longer reproduce the failure when updating from tetex-1.0.7-r12 to tetex-2.0-r1.
Ok. I've put in a request to have this problem dealt with in future portage versions, as well. I'm closing the bug.
I know the bugs closed, but just wanted to confirm that updating to 2.0-r1 (from the "broken" 2.0 directly without backtracking to 1.0.7-r12) works fine.
