[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#316245: tetex-bin: postinst failure while building etex and pdfetex formats



> Well, that symlink is contained in the package tetex-base itself
> (i.e. created during build time). Do you have any clue, why it
> was not written to the disk?

I removed it myself to get rid of the circular symlink.

When I reinstall tetex-base on a system where both language.def symlinks
are removed, the proper /usr/share/texmf/tex/plain/config/language.def
symlink comes back, but I get this error:

# apt-get install --reinstall tetex-base
[...]
Preparing to replace tetex-base 3.0-7 (using .../tetex-base_3.0-7_all.deb) ...
Unpacking replacement tetex-base ...
Replaced by files in installed package tex-common ...
Setting up tetex-base (3.0-7) ...
dpkg: tetex-base: warning - config file `/etc/texmf/plain/language.def' is a circular link
 (= `/etc/texmf/plain/language.def')

and this symlink is created:

lrwxrwxrwx  1 root root 29 2005-09-09 14:12 /etc/texmf/plain/language.def -> /etc/texmf/plain/language.def

If I reinstall tetex-base on a system
where /usr/share/texmf/tex/plain/config/language.def exists, I get:

# apt-get install --reinstall tetex-base
[...]
Preparing to replace tetex-base 3.0-7 (using .../tetex-base_3.0-7_all.deb) ...
Unpacking replacement tetex-base ...
dpkg: tetex-base: warning - config file `etc/texmf/plain/language.def' is a circular link
 (= `/etc/texmf/plain/language.def')
Replaced by files in installed package tex-common ...
Setting up tetex-base (3.0-7) ...
dpkg: tetex-base: warning - config file `/etc/texmf/plain/language.def' is a circular link
 (= `/etc/texmf/plain/language.def')

and the same final result.

> Can you (just for fun) purge you teTeX system on the broken machine
> and do a complete reinstall 3.0? Does that solve the problem?

It is not funny because it would remove 40 packages and 150MB from my
system and reinstalling everything afterwards would be a pain.
Furthermore I would loose the ability to test a potential fix.

BTW, keeping my system in a broken state is a pain.  Should I wait for a
potential fix or fix it myself ?

-- 
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/





Reply to: