Arne Ahrend <[EMAIL PROTECTED]> wrote: > Starting after > dpkg --purge tetex-{base,bin,extra} texinfo > it makes a difference whether I do > apt-get install tetex-bin ; apt-get install tetex-extra > (this reproduces the bug) > or just > apt-get install tetex-extra > and let it pull in all the others (this does NOT reproduce the bug).
Interesting (presumably this has nothing to do with the /bin/sh thing, which is reassuring). The installation log (dpkg's messages) would be even more interesting. Maybe the unpack order can make font files appear in an unexpected place if a package installs a symlink /path/to/foo and another package that is unpacked later installs files such as /path/to/foo/bar/baz. But I think the opposite order would give a dpkg error ("trying to overwrite ..."), so I doubt it can be the explanation (and that would probably have been noticed earlier). Just what comes to mind from what you described... -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]