Bug#265611: tetex-extra and fmtutil
jimmy@g-tec.co.at wrote:
> On Mon, Aug 16, 2004 at 03:00:22PM +0200, Frank Küster wrote:
>> jimmy@g-tec.co.at wrote:
>>
>> > On Sun, Aug 15, 2004 at 11:41:32PM +0200, Hilmar Preusse wrote:
>> >> On 15.08.04 Andreas Gredler (jimmy@g-tec.co.at) wrote:
>> >>
>> >> Hi,
>> >>
>> >> > I'm writing you this personal mail because I don't want to discuss
>> >> > everything on the bug list(Long bug reports are hard to read, IMO)
>>
>> Which is a good way to have your issues resolved much more slowly, and
>> for shutting out other people from valuable information. It also made it
>> harder to me to find your original bug report.
>
> I understand. My intention was to keep the bugreport small and to
> provide the needed information afterwards. It's really hard to find
> information in bug reports when everybody posts his whole sytem output.
It's even harder to resolve bugs and work with packaging if the
information in the BTS is incomplete. It's our archive, it's the place
where we work. I am glad if people restrict their information to what is
really necessary - but please please mail to the bug.
>> Here, VARTEXMF is there. It seems that update-texmf has not been called
>> during upgrade of tetex-bin, which is strange. Did you get any error
>> messages when tetex-bin was last upgraded? What happens if you do
>
> Yes, same problems. But it was solved by the next upgrade.
Hm? If tetex-bin had the same problems as you described for tetex-extra,
but those problems went away, then how can it be that you still don't
have VARTEXMF in your texmf.cnf? If VARTEXMF isn't in there, you should
get problems with tetex-bin, too.
>> dpkg-reconfigure tetex-bin
>
> Never tested, since my sytem worked again after I hacked the postinst script.
So please do it for us. Or have you also hacked tetex-bin's postinst?
Then please do, in this order,
apt-get --reinstall install tetex-base
apt-get --reinstall install tetex-bin
apt-get --reinstall install tetex-extra
and report all error messages.
>> > Because I had the same problem with tetex-base, which was solved after
>> > the next upgrade, I took a look in the newer postinst script.
>> > IMO they solved this problem by NOT calling fmtutil and updmap. All
>>
>> they are we.
>
> Sorry? Don't understand.
the "they" you mentioned, the tetex-base maintainers, are the same as
the maintainers of tetex-extra (and tetex-bin and -doc and -src): We,
the group of Debian teTeX maintainers.
> My main intention was to report it, since I was wondering that the
> problem is solved in tetex-base but not in tetex-extra.
Thank you for that.
Regards, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Reply to: