Bug#366907: tetex-bin: Fails to configure, updmap failed
On 5/14/06, Ralf Stubner <ralf.stubner@web.de> wrote:
On Sat, May 13, 2006 at 19:57 +0200, Ralf Stubner wrote:
> Even though I modified 05TeXMF.cnf, I was /not asked/ about this during
> reinstallation of tex-common!
Meanwhile this makes sense to me. 05TeXMF.cnf is managed by ucf, and ucf
sees that the 'previously installed' version and the 'to be installed'
version have the same md5sum, hence my changed version is preserved, as
it is supposed to be.
Which seems like a defect in the change-detection algorithm. Why are
the md5sums of the different files the same? Wouldn't it make more
sense to use "diff" to see if there's a difference? In any case, this
doesn't explain my experience; my md5sums are very different:
ec6c37a0d317ed545a3e66409cf54630 05TeXMF.cnf-home
dd2b65e95a497637be4033ecbecdd2bd /etc/texmf/texmf.d/05TeXMF.cnf
> Even though the settings in 05TeXMF.cnf
> would /break/ the system, since TEXMFDIST is not set, the checks in
> tex-common's postinst did /not detect/ this! What is going wrong here?
I think I have found an explanation for this. In check_texmf() in the
postinst script, $checkfailed is allways set to false in the beginning.
Hence if some check in the middle fails but the last one not, this is
not detected. Moving the failing chack to the end or removing that line
makes the postinst fail. However, it fails without any further notice,
so I think this is not the whole story. All the debconf stuff in
check_texmf() does not work within my pbuilder. Strange ...
I don't understand this; I don't know what "fails without any further
notice" means, but it certainly seems like a bug.
cheerio
ralf
Liam
Reply to: