0> In article <[EMAIL PROTECTED]>, 0> Frank Küster <URL:mailto:[EMAIL PROTECTED]> ("fant") wrote:
fant> I've built a package with that change. [Toby], would you please fant> test whether this helps? I'm not even sure whether it's sufficient fant> to change libkpathsea4, or you also need tetex-bin. And of course fant> during the upgrade, some old executables will also be used in the fant> maintainer scripts, so you can't expect it to be completely quiet. fant> fant> The packages are at fant> fant> http://people.debian.org/~frank/libkpathsea4_3.0-22~1_i386.deb fant> http://people.debian.org/~frank/tetex-bin_3.0-22~1_i386.deb Thanks. I upgraded libkpathsea4 first, with no problems, and then tetex-bin (I had to upgrade tex-common first). I still got lots of syslog output, so I then re-installed the new tetex-bin (to ensure we're using all the new binaries), and the same happened. Watching that install with xconsole next to the xterm I was using showed that the accesses to /share all happened during the following stages: /-------- | Running fmtutil-sys. This may take some time... done. | Running updmap-sys. This may take some time... done. \-------- Both these programs are part of tetex-bin, so the install should be using the new ones by that stage - unless there's some conffile I need to check? (P.S. forgot to mention that something in cron.daily has this effect, too)
