Dear Frank, dear all teTeX maintainers!
I got the following bug report for texinfo which I do not understand:
On Son, 12 Feb 2006, Justin Pryzby wrote:
> Package: texinfo
> Version: 4.8-4
> Severity: important
>
> While dist-upgrading:
>
> Preparing to replace texinfo 4.8-2 (using .../texinfo_4.8-4_i386.deb) ...
> Unpacking replacement texinfo ...
> kpsewhich: error while loading shared libraries: libkpathsea.so.4: cannot
> open shared object file: No such file or directory
> mktexlsr: Done.
>
> I think the dependencies need to be tighter:
> Depends: libc6 (>= 2.3.5-1), tex-common | tetex-bin (<< 3.0)
>
> Why is tex-common sufficient?
>
> I think the problem might be calling the previous packages
> maintscripts, after upgrading some dependencies, but before
> configuring dependencies of those dependencies; right?
My explanation is that:
- tetex, libkpathsea, and texinfo are upgraded at the same time
- since texinfo does not depend on tetex >= 3 it happens that it is
configured *before* tetex/libkpathsea is configured
- tetex is already unpacked (but not configured), so the
which fmtutil-sys
test succeeds and fmtutil-sys is called, thus kpsewhich
I don't want to tighten the depends to include tetex/texlive, because
some users might want to use texinfo only for generating info documents
or html documents etc.
So I guess I have to add a check wether tetex is configured? Probably it
is enough to call
kpsewhich
once and see if there is an error.
So my questions: Is the above interpretation correct, and do you have
any suggestions different from the one I made to fix this problem?
Best wishes
Norbert
---
Dr. Norbert Preining Università di Siena
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
---
The suit into which the man's body had been stuffed looked
as if it's only purpose in life was to demonstrate how
difficult it was to get this sort of body into a suit.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]