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

Bug#251358: Something broken in tetex-bin



I'm essentially repeating a mail I previously sent to the auctex mailing
list: 

Vittorio <v.demartino2@virgilio.it> wrote:

> On Thursday 27 May 2004 20:21, Frank Küster wrote:
>> Vittorio <v.demartino2@virgilio.it> wrote:
>> > I had to uninstall the debian tetex packages  (apt-get remove --purge)
>> > under debian  testing because there was some problem of dependencies
>>
>> May I aks what thoise problems were, exactly? You didn't file a bug
>> report against the tetex packages - is it a bug in a different package?
>
> Submitted to debian-user list, texhash and comp.text.tex:

Thank you for reporting it in the BTS. However, you didn't use
reportbug, which makes us miss some important information. Could you
please use "reportbug tetex-bin", then say "y" when it asks "Is the bug
you found listed above" (even if it isn't), and then enter the bug
number, 251358? Then we will get the information we need (plus the
hashfile grep, see below).

> Setting up tetex-bin (2.0.2-14) ...
> Regenerating /etc/texmf/texmf.cnf ... done
> Running initex. This may take some time. ...
> Error: `etex -ini ?-jobname=3Detex -progname=3Detex *etex.ini' failed
> Error: `pdfetex -ini ?-jobname=3Dpdfetex -progname=3Dpdfetex *pdfetex.ini=
> ' failed

Could you send us /var/lib/texmf/web2c/etex.log, from the run when the
error occured?

> It has become a serious problem!
> After those messages of error I completely uninstalled all the tetex 
> packages the tex connected ones (lyx, texmacs, etc.) by means of 
> "apt-get remove --purge pasckage"; then - to be on the safe side - I 
> removed by hand the
> /etc/texmf & /usr/share/texmf directories with their subdirs.

Which might have deleted files of other packages - e.g. texinfo with
/usr/share/texmf/tex/texinfo does not depend on any tetex package. You
should reinstall this.

> Reinstalling all over again tetex-2.0.2 from the official debian testing
> archive via apt-get install tetex-bin again causes a problem: when 
> setting the package up debian testing complains about  a missing 
> configuration file under /etc/texmf (as I said this dir was removed by 
> hand by me!). In fact, I found that the configuration program of 
> tetex-bin 2.0.2-14  expected an /etc/texmf/texmf/05TeXMF.cnf file that 
                                             ^^^^^
thiss should be /texmf.d/

> actually was codified with something like /usr/share/texmf/..../05TeXMF.cnf.
> I copied the required file under/etc/texmf/texmf/ and the configuration
> complained about a missing /etc/texmf/texmf.cnf file. I found it under 
> the "usual"  /usr/share/texmf/.... and copied in the right position and 
> now the error is as follow:
>
> Regenerating /etc/texmf/texmf.cnf ... done
> update-fmtutil; Something seems wrong.
> dpkg: error processing tetex-bin (--configure):
>   subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>   tetex-bin
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Has anyone any idea on why this has been happening?

This is strange, because if you really _purged_ tetex-bin,
/etc/texmf/texmf.d/05TeXMF.cnf should be reinstalled. Furthermore, there
shouldn't be a "texmf.cnf" file "under the usual /usr/share/texmf", only
in /usr/share/tetex-bin/. 

The same seems to have happened to files in /etc/texmf/fmt.d

> What to do next?

Ideally, you should purge tetex-bin again - you don't need to remove
anything manually - and reinstall it. Assuming that no other packages
are broken on your system, do

dpkg --force-depends --purge tetex-bin
apt-get install tetex-bin

(don't try anything in between, the system will be broken!)
You should be asked debconf questions, answer them as you did before,
and then write the bug report. Also interesting for this would be the
output of 

grep texmf /var/lib/ucf/hashfile

> In this case what are all the directories I should delete?

It shouldn't be necessary to remove any. If there are directories with
harmful files (presumable outside the scope of the package management,
e.g. in /usr/local/share/texmf), we'll find that out easily with the
logfiles. 

Regards, Frank
-- 
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie




Reply to: