Bug#487630: SUCCESS after removal of 00tetex.cnf (was: Re: Bug#487630: Bug 487630 exists also in version 2007.dfsg.2-3 (and version 2007.dfsg.2-4))
On Wed, 2008-11-05 at 23:29 +0100, Hilmar Preusse wrote: On 04.11.08 Omer Zak ([EMAIL PROTECTED]) wrote: According to dpkg -S, 00tetex.cnf belongs to no package. The laptop has been running Debian Testing for few years (Sarge Testing, then Etch Testing, and now Lenny Testing), so it is probable that one of the versions of the package, which originally owned it, was uninstalled (or upgraded, rendering the file unneeded) but neglected to remove this file. Well, the postinst- and preinst scripts of teTeX in Debian are/were rather a nightmare regarding which files have to be removed/fixed/changed to resurrect mistakes made before. You may have a look at them just for fun. I guess you run once a testing version of teTeX, which was broken and we didn't make a fix for this special version. I am glad to see that the general problem is being addressed and the answer is not just remove by hand the offending 00tetex.cnf file. Your 00tetex.cnf does not have the magic # -_- DebPkgProvidedMaps -_- snipped, hence is it read when creating the fmtutil.cnf. To get a fix I suggest that the preinst script of an important package (tex-common ?) greps for that snippet through all files in /etc/texmf/fmt.d/ and renames all files, which do not have it (e.g. append the extension unused) and inform the end user about it. Renaming the unused files and warning the user about them would do it. However, identifying them by grepping for the magic snippet won't work. It is possible that a future broken package fails to remove such a file, and it will remain in the filesystem with the magic snippet, and then my problem with 00tetex.cnf will recur. Any further ideas? A tool (dpkg-* or apt-*) for auditing the files in the non-*/local/* and non-/opt/* filesystems, finding files not belonging to any package, and advising the user how to deal with them. Packages, which own subdirectories with names like */*.d/, may provide special scripts and instructions for dealing with files dropped there by other packages (and orphaned by them), and manually by the sysadmin. I think that the subject is now more suitable for one of Debian's mailing lists than for this bug report - please advise which mailing list, and I'll post there a summary of the bug and the discussion so far. --- Omer -- Did you shave a yak today? My own blog is at http://www.zak.co.il/tddpirate/ My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487630: SUCCESS after removal of 00tetex.cnf (was: Re: Bug#487630: Bug 487630 exists also in version 2007.dfsg.2-3 (and version 2007.dfsg.2-4))
On Do, 06 Nov 2008, Omer Zak wrote: I am glad to see that the general problem is being addressed and the answer is not just remove by hand the offending 00tetex.cnf file. As Hilmar pointed out. The *released* packages of teTeX didn't have this problem. You seem to have used intermediate or testing packages, which is not necessarily supported. We try our best, but cannot guarantee anything. For these cases remove by hand is definitely a solution. However, identifying them by grepping for the magic snippet won't work. It is possible that a future broken package fails to remove such a file, It will work, because these snippets are *only* included if the package is installed. If you remove a package without purging, all packages will leave these config files around. That is one of the fundamentals of Debian packaging. But they will not be included in the final fmtutil.cnf, because they are not listed in one of the /var/lib/texmf/... files. Packages, which own subdirectories with names like */*.d/, may provide special scripts and instructions for dealing with files dropped there by other packages (and orphaned by them), and manually by the sysadmin. That is already there, and it is called dh_installtex. If a package on purpose circumvents this, we *cannot* and aren't *allowed* to do that!!! One package cannot remove/rename/whatever the configfile of another package. (tetex here is an exceptions because it comes from us and is already removed!). I think that the subject is now more suitable for one of Debian's mailing lists than for this bug report - please advise which mailing Not it isn't. It is simply that you do not understand the inner working of config files. The *have* to be kept when removing a package (but not when purging). list, and I'll post there a summary of the bug and the discussion so far. Please do so, but don't expect too much. The problem lies somewhere else, namely in the usage of intermediate and not released packages. Best wishes Norbert --- Dr. Norbert Preining [EMAIL PROTECTED]Vienna University of Technology Debian Developer [EMAIL PROTECTED] Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- SHRIVENHAM (n.) One of Germaine Greer's used-up lovers. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487630: SUCCESS after removal of 00tetex.cnf (was: Re: Bug#487630: Bug 487630 exists also in version 2007.dfsg.2-3 (and version 2007.dfsg.2-4))
On 04.11.08 Omer Zak ([EMAIL PROTECTED]) wrote: On Mon, 2008-11-03 at 17:42 +0100, Hilmar Preusse wrote: On 03.11.08 Omer Zak ([EMAIL PROTECTED]) wrote: Hi, /etc/texmf/fmt.d: total 28 drwxr-xr-x 2 root root 4096 Nov 3 16:10 . drwxr-xr-x 21 root root 4096 Nov 3 15:16 .. -rw-r--r-- 1 root root 3704 Sep 2 2004 00tetex.cnf -rw-r--r-- 1 root root 1364 Jul 28 01:53 00tex.cnf And here is the old 00tetex.cnf from teTeX times, which causes your failures. I should have seen in earlier. To which package belongs it? According to dpkg -S, 00tetex.cnf belongs to no package. The laptop has been running Debian Testing for few years (Sarge Testing, then Etch Testing, and now Lenny Testing), so it is probable that one of the versions of the package, which originally owned it, was uninstalled (or upgraded, rendering the file unneeded) but neglected to remove this file. My computer at home has stable and teTeX installed. The file is there too. I'll check to which package the file belongs and hence which package should have removed/renamed it. H. -- sigmentation fault -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487630: SUCCESS after removal of 00tetex.cnf (was: Re: Bug#487630: Bug 487630 exists also in version 2007.dfsg.2-3 (and version 2007.dfsg.2-4))
On 04.11.08 Omer Zak ([EMAIL PROTECTED]) wrote: On Mon, 2008-11-03 at 17:42 +0100, Hilmar Preusse wrote: On 03.11.08 Omer Zak ([EMAIL PROTECTED]) wrote: Hi all, /etc/texmf/fmt.d: total 28 drwxr-xr-x 2 root root 4096 Nov 3 16:10 . drwxr-xr-x 21 root root 4096 Nov 3 15:16 .. -rw-r--r-- 1 root root 3704 Sep 2 2004 00tetex.cnf -rw-r--r-- 1 root root 1364 Jul 28 01:53 00tex.cnf And here is the old 00tetex.cnf from teTeX times, which causes your failures. I should have seen in earlier. To which package belongs it? According to dpkg -S, 00tetex.cnf belongs to no package. The laptop has been running Debian Testing for few years (Sarge Testing, then Etch Testing, and now Lenny Testing), so it is probable that one of the versions of the package, which originally owned it, was uninstalled (or upgraded, rendering the file unneeded) but neglected to remove this file. Well, the postinst- and preinst scripts of teTeX in Debian are/were rather a nightmare regarding which files have to be removed/fixed/changed to resurrect mistakes made before. You may have a look at them just for fun. I guess you run once a testing version of teTeX, which was broken and we didn't make a fix for this special version. Your 00tetex.cnf does not have the magic # -_- DebPkgProvidedMaps -_- snipped, hence is it read when creating the fmtutil.cnf. To get a fix I suggest that the preinst script of an important package (tex-common ?) greps for that snippet through all files in /etc/texmf/fmt.d/ and renames all files, which do not have it (e.g. append the extension unused) and inform the end user about it. Packages providing files in there should have the snippet (I'm not sure about this: update-fmtutil knows the DebPkgProvidedMaps mechanism, but it is not documented in the Debian TeX policy). Any further ideas? H. -- sigmentation fault -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487630: Bug 487630 exists also in version 2007.dfsg.2-3 (and version 2007.dfsg.2-4)
On Mon, 2008-11-03 at 13:30 +0100, Norbert Preining wrote: (pointer to instructions how to check for this bug and how to work around it - would be helpful as well) /usr/share/doc/texlive-common/NEWS.Debian.gz According to this document, no special action is needed. Just install texlive-common-bin and texlive-common and the process of installationconfiguration is supposed to take care of this. I tried to do this (using aptitude). Did not work for me. When trying to reinstall texlive-base and texlive-base-bin, they did not properly configure themselves due to texlive-base-bin failure to reconfigure. Next, I had aptitude remove texlive-base and texlive-base-bin, and all packages depending upon them. Before the actual update, I marked all those packages as ones to be purged rather than deleted. texlive-lang-cyrillic failed to purge due to some missing directory. Then, I re-ran aptitude, purging texlive-lang-cyrillic, and this time it purged. Then I had aptitude re-install texlive and all packages upon which it depends. This attempt ended in error. Attached please find reportbug-created file and fmtutil.* logfile for this attempt. Subject: texlive-base-bin: Another installation attempt failed Followup-For: Bug #487630 Package: texlive-base-bin Version: 2007.dfsg.2-4 -- Package-specific info: If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.latex-einfuehrung.de/mini-en.html (english) or http://www.latex-einfuehrung.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 root root 1154 Nov 3 15:17 /var/lib/texmf/ls-R -rw-rw-r-- 1 root staff 79 Nov 3 15:16 /usr/local/share/texmf/ls-R lrwxrwxrwx 1 root root 29 Nov 3 15:14 /usr/share/texmf/ls-R - /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 27 Nov 3 15:14 /usr/share/texmf-texlive/ls-R - /var/lib/texmf/ls-R-TEXLIVE lrwxrwxrwx 1 root root 27 Nov 3 15:14 /usr/share/texmf-texlive/ls-R - /var/lib/texmf/ls-R-TEXLIVE ## Config files lrwxrwxrwx 1 root root 20 Nov 3 15:14 /usr/share/texmf/web2c/texmf.cnf - /etc/texmf/texmf.cnf -rw-r--r-- 1 root root 6153 Nov 3 15:17 /var/lib/texmf/web2c/fmtutil.cnf -rw-r--r-- 1 root root 5101 Nov 3 15:17 /var/lib/texmf/web2c/updmap.cfg -rw-r--r-- 1 root root 1835 Nov 3 15:17 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ total 4 -rw-r--r-- 1 root root 283 Jul 28 01:53 mktex.cnf ## md5sums of texmf.d 42c20d7e8bd343542772b5a145bf8ad8 /etc/texmf/texmf.d/05TeXMF.cnf 5f7f6652cc8b8071c9e4ea6ba9e9f0a1 /etc/texmf/texmf.d/15Plain.cnf f68e5add6afd6585b982f2f78e2e6a92 /etc/texmf/texmf.d/45TeXinputs.cnf ea33127256c6a9f37145ae5b16fdb80c /etc/texmf/texmf.d/55Fonts.cnf afccf1d3f87057411166a77c58e00bd1 /etc/texmf/texmf.d/65BibTeX.cnf 9da7c1c7b1eaf06f941af91f48a23068 /etc/texmf/texmf.d/75DviPS.cnf 7ae52efac46feb97010986e57877d12e /etc/texmf/texmf.d/80DVIPDFMx.cnf.dpkg-new 37329819f1109e8a457e64b8b58fecdb /etc/texmf/texmf.d/85Misc.cnf a8952d594677235951d447665ec46e9c /etc/texmf/texmf.d/90TeXDoc.cnf 30f4f13357c2761ed01a6a15f28725a5 /etc/texmf/texmf.d/95NonPath.cnf -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages texlive-base-bin depends on: ii ed 0.7-2 The classic unix line editor ii libc6 2.7-15GNU C Library: Shared libraries ii libgcc11:4.3.2-1 GCC support library ii libkpathsea4 2007.dfsg.2-4 TeX Live: path search library for ii libncurses55.6+20080830-1shared libraries for terminal hand ii libpng12-0 1.2.27-2 PNG library - runtime ii libpoppler30.8.7-1 PDF rendering library ii libstdc++6 4.3.2-1 The GNU Standard C++ Library v3 ii libx11-6 2:1.1.5-2 X11 client-side library ii libxaw72:1.0.4-2 X11 Athena Widget library ii libxmu62:1.0.4-1 X11
Bug#487630: Bug 487630 exists also in version 2007.dfsg.2-3 (and version 2007.dfsg.2-4)
On Mo, 03 Nov 2008, Omer Zak wrote: I tried to do this (using aptitude). Did not work for me. When trying to reinstall texlive-base and texlive-base-bin, they did not properly configure themselves due to texlive-base-bin failure to reconfigure. Failure messages? Then I had aptitude re-install texlive and all packages upon which it depends. This attempt ended in error. Attached please find reportbug-created file and fmtutil.* logfile for this attempt. How does it come that you purged all packages and still have texlive-omega installed? Can you as root please set printenv ?? Something is deeply strange on your system. The failures you sent are AFTER purging all packagas and reinstalling the packages? If yes, I can't believe that. modes.mf *is* present in texlive-base, and if you have purged it also the information that it has been removed has disappeared. Reinstalling *must* create the modes.mf file. Then, texlive-omega is still there, strange enough Again, please: kpsewhich --format='web2c files' fmtutil.cnf what does it show? And please attach this file. I really suspect that you have done something strange to your system. About several hundreds to thousands time these packages have been installed from a clean state without breaking ... Best wishes Norbert --- Dr. Norbert Preining [EMAIL PROTECTED]Vienna University of Technology Debian Developer [EMAIL PROTECTED] Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- SCOPWICK (n.) The flap of skin which is torn off you lip when trying to smoke an untipped cigarette. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487630: Bug 487630 exists also in version 2007.dfsg.2-3 (and version 2007.dfsg.2-4)
On Mon, 2008-11-03 at 15:43 +0100, Norbert Preining wrote: On Mo, 03 Nov 2008, Omer Zak wrote: I tried to do this (using aptitude). Did not work for me. When trying to reinstall texlive-base and texlive-base-bin, they did not properly configure themselves due to texlive-base-bin failure to reconfigure. Failure messages? Sorry, I didn't save it. Then I had aptitude re-install texlive and all packages upon which it depends. This attempt ended in error. Attached please find reportbug-created file and fmtutil.* logfile for this attempt. How does it come that you purged all packages and still have texlive-omega installed? I DO NOT have texlive-omega installed. Can you as root please set printenv ?? Here it is (information which I deemed to be sensitive security-wise was replaced by 'blip'): -=-=-=-=-=-=- start of printenv output (sanitized) SSH_AGENT_PID=blip TERM=xterm DESKTOP_STARTUP_ID= SHELL=/bin/bash GTK_RC_FILES=/etc/gtk/gtkrc:/home/blip/.gtkrc-1.2-gnome2 WINDOWID=blip GTK_MODULES=gnomebreakpad USER=root LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.svgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36: GNOME_KEYRING_SOCKET=/tmp/keyring-blip/socket SSH_AUTH_SOCK=/tmp/keyring-blip/ssh USERNAME=blip SESSION_MANAGER=local/blip.il:/tmp/.ICE-unix/blip XPSERVERLIST=:64 MAIL=/var/mail/root PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin DESKTOP_SESSION=default GDM_XSERVER_LOCATION=local PWD=/home/blip PS1=\h:\w\$ GDMSESSION=default HISTCONTROL=ignoredups SHLVL=2 HOME=/root LS_OPTIONS=--color=auto GNOME_DESKTOP_SESSION_ID=Default LOGNAME=root DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-blip,guid=blip LESSOPEN=| /usr/bin/lesspipe %s DISPLAY=:0.0 LESSCLOSE=/usr/bin/lesspipe %s %s XAUTHORITY=/home/blip/.Xauthority COLORTERM=gnome-terminal _=/usr/bin/printenv -=-=-=-=-=-=- end of printenv output (sanitized) Something is deeply strange on your system. The failures you sent are AFTER purging all packagas and reinstalling the packages? Maybe I missed a package or two. If yes, I can't believe that. modes.mf *is* present in texlive-base, and if you have purged it also the information that it has been removed has disappeared. Reinstalling *must* create the modes.mf file. Then, texlive-omega is still there, strange enough As said above, it is not there but somehow texlive-base or its dependencies look for it. Again, please: kpsewhich --format='web2c files' fmtutil.cnf what does it show? It shows: /var/lib/texmf/web2c/fmtutil.cnf The file (fmtutil.cnf) is attached to this E-mail message. I noticed that it has some lines which refer to omega. I really suspect that you have done something strange to your system. About several hundreds to thousands time these packages have been installed from a clean state without breaking ... On Mon, 2008-11-03 at 15:44 +0100, Norbert Preining wrote: On Mo, 03 Nov 2008, Omer Zak wrote: However, this did not work for me. Attached please find the new fmtutil.* logfile made by fmtutil-sys. Answer my other email about texlive-omega ... it seems that you have a local copy of fmtutil.cnf hanging around somewhere. I ran: cd / find . -iname \*fmtutil.cnf\* I got: ./usr/share/man/man5/fmtutil.cnf.5.gz ./var/lib/texmf/web2c/fmtutil.cnf ./etc/texmf/fmtutil.cnf.postinst-bak The last file is dated from 2004 Sep 12, and I am attaching it. I am attaching also the output of 'ls -alR /etc/texmf/' as I noticed that it has some files with timestamps from the last millenium. -- Did you shave a yak today? My own blog is at http://www.zak.co.il/tddpirate/ My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html ### This file was automatically generated by update-fmtutil. # # Please do not edit it directly. If you want to add or change # anything here, please have a look at
Bug#487630: Bug 487630 exists also in version 2007.dfsg.2-3 (and version 2007.dfsg.2-4)
On 03.11.08 Omer Zak ([EMAIL PROTECTED]) wrote: Hi, I DO NOT have texlive-omega installed. Content-Disposition: attachment; filename=fmtutil.cnf Content-Type: text/plain; name=fmtutil.cnf; charset=UTF-8 Cont ### This file was automatically generated by update-fmtutil. # # Please do not edit it directly. If you want to add or change # anything here, please have a look at the files in: # #/etc/texmf/fmt.d/ # # and invoke update-fmtutil. # ### ### From file: /etc/texmf/fmt.d/00tetex.cnf # Thomas Esser, Copyright 1998, 1999. Public domain. # fmtutil.cnf: configuration file for fmtutil. Ae. omega omega - omega.ini lambdaomega language.datlambda.ini Here is the omega. /etc/texmf/fmt.d: total 28 drwxr-xr-x 2 root root 4096 Nov 3 16:10 . drwxr-xr-x 21 root root 4096 Nov 3 15:16 .. -rw-r--r-- 1 root root 3704 Sep 2 2004 00tetex.cnf -rw-r--r-- 1 root root 1364 Jul 28 01:53 00tex.cnf And here is the old 00tetex.cnf from teTeX times, which causes your failures. I should have seen in earlier. To which package belongs it? H. -- sigmentation fault -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487630: SUCCESS after removal of 00tetex.cnf (was: Re: Bug#487630: Bug 487630 exists also in version 2007.dfsg.2-3 (and version 2007.dfsg.2-4))
On Mon, 2008-11-03 at 17:42 +0100, Hilmar Preusse wrote: On 03.11.08 Omer Zak ([EMAIL PROTECTED]) wrote: omega omega - omega.ini lambda omega language.datlambda.ini Here is the omega. /etc/texmf/fmt.d: total 28 drwxr-xr-x 2 root root 4096 Nov 3 16:10 . drwxr-xr-x 21 root root 4096 Nov 3 15:16 .. -rw-r--r-- 1 root root 3704 Sep 2 2004 00tetex.cnf -rw-r--r-- 1 root root 1364 Jul 28 01:53 00tex.cnf And here is the old 00tetex.cnf from teTeX times, which causes your failures. I should have seen in earlier. To which package belongs it? According to dpkg -S, 00tetex.cnf belongs to no package. The laptop has been running Debian Testing for few years (Sarge Testing, then Etch Testing, and now Lenny Testing), so it is probable that one of the versions of the package, which originally owned it, was uninstalled (or upgraded, rendering the file unneeded) but neglected to remove this file. After removing 00tetex.cnf (actually, I moved it to an user's home directory), texlive-base-bin and texlive-base and their dependencies were successfully configured. Subsequently, I successfully ran a task which depends upon them, proving that they are working properly. Thus, the real bug is that at installation time, texlive-base-bin does not verify that there are no problematic leftover files in /etc/texmf and its subdirectories. I think that it is a general problem, which may benefit from a Debian-wide solution. -- Did you shave a yak today? My own blog is at http://www.zak.co.il/tddpirate/ My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
