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

Bug#488038: marked as done (texlive-base-bin: kpsewhere weirdness)



Your message dated Thu, 26 Jun 2008 21:55:44 +0200
with message-id <87tzfgkm2n.fsf@riesling.zuerich.kuesterei.ch>
and subject line Re: Bug#488038: texlive-base-bin: kpsewhere weirdness
has caused the Debian Bug report #488038,
regarding texlive-base-bin: kpsewhere weirdness
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
488038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488038
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-base-bin
Version: 2007.dfsg.1-4.np.etch.1
Severity: normal

[By the way, Norbert, your etch backport of the package has a higher
version number than the lenny version. I've switched to lenny meanwhile,
but I still have the backport installed until 2007.dfsg.2-1 reaches
testing. Better use ~ in the version number]

kpsewhere acts very strangely here. It looks as if the whole concept of
kpsewhere flawed, maybe only in newer web2c/libkpathsea versions? 

Or is there a Debian-specific breakage?



$ kpsewhere texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf

It does *not* find an other texmf.cnf file I have, nore other duplicate
files. 

$ ls .texmf-config/web2c/texmf.cnf
.texmf-config/web2c/texmf.cnf

So I investigated what kpsewhere does:

$ tail /usr/bin/kpsewhere 

IFS=':'
for file
do
    for path in `kpsewhich --expand-path='$TEXMF'`
    do
        eval TEXMF=\$path kpsewhich $options \"\$file\"
    done
done
exit 0
$ IFS=':'
$ for path in $kpsepath; do echo $path; done
/home/frank/.texmf-config
/home/frank/.texmf-var
/home/frank/texmf
/etc/texmf
/var/lib/texmf
/usr/local/share/texmf
/usr/share/texmf
/usr/share/texmf-texlive

That looks good.

$ for path in $kpsepath; do eval TEXMF=\$path kpsewhich --var-value=TEXMF; done
/home/frank/.texmf-config
/home/frank/.texmf-var
/home/frank/texmf
/etc/texmf
/var/lib/texmf
/usr/local/share/texmf
/usr/share/texmf
/usr/share/texmf-texlive

That too, but

$ for path in $kpsepath; do eval TEXMF=\$path kpsewhich texmf.cnf; done
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf

This behavior doesn't only show up with texmf.cnf, the same with
fmtutil.cnf (with and without --format='web2c files').


Regards, Frank

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (99, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages texlive-base-bin depends on:
ii  ed               0.7-1                   The classic unix line editor
ii  libc6            2.7-10                  GNU C Library: Shared libraries
ii  libkpathsea4     2007.dfsg.1-4.np.etch.1 TeX Live: path search library for 
ii  libncurses5      5.6+20080308-1          Shared libraries for terminal hand
ii  libpng12-0       1.2.27-1                PNG library - runtime
ii  libpoppler0c2    0.4.5-5.1etch2          PDF rendering library
ii  libx11-6         2:1.1.4-2               X11 client-side library
ii  libxaw7          2:1.0.4-2               X11 Athena Widget library
ii  libxmu6          2:1.0.4-1               X11 miscellaneous utility library
ii  libxpm4          1:3.5.7-1               X11 pixmap library
ii  libxt6           1:1.0.5-3               X11 toolkit intrinsics library
ii  mime-support     3.44-1                  MIME files 'mime.types' & 'mailcap
ii  perl             5.10.0-10               Larry Wall's Practical Extraction 
ii  texlive-common   2007.dfsg.1-1           TeX Live: Base component
ii  zlib1g           1:1.2.3.3.dfsg-12       compression library - runtime

Versions of packages texlive-base-bin recommends:
ii  perl-tk          1:804.028-1+b1          Perl module providing the Tk graph
ii  texlive-base-bin 2007.dfsg.1-4.np.etch.1 TeX Live: Documentation files for 

Versions of packages tex-common depends on:
ii  debconf                       1.5.22     Debian configuration management sy
ii  ucf                           3.007      Update Configuration File: preserv

Versions of packages texlive-base-bin is related to:
pn  tetex-base                 <none>        (no description available)
ii  tetex-bin                  2007.dfsg.1-1 TeX Live: teTeX transitional packa
ii  tetex-extra                2007.dfsg.1-1 TeX Live: teTeX transitional packa
ii  tex-common                 1.11          common infrastructure for building

-- debconf information:
  tex-common/check_texmf_wrong:
  tex-common/check_texmf_missing:

-- 
Frank Küster
Debian Developer (teTeX/TeXLive)



--- End Message ---
--- Begin Message ---
Ralf Stubner <ralf.stubner@web.de> wrote:

> rfstubne@nb-rfstubne:~$ kpsewhere --format='web2c files'  fmtutil.cnf
> /home/rfstubne/texmf/web2c/fmtutil.cnf
> /var/lib/texmf/web2c/fmtutil.cnf
> /usr/share/texmf-texlive/web2c/fmtutil.cnf
>
> I also don' think that it is surprising that setting TEXMF does not
> alter the texmf.cnf file found. AFAIK TEXMF is not used when looking
> for texmf.cnf. Instead a compile-time path is used for texmf.cnf and
> all other *.cnf files.

I agree, and I was so sure that I tried what you showed, but you are
right. I know that I also tried other duplicate files when I looked at
the code in kpsewhere and tried to debug it, but here something else hit
me. It's not a TeX-related problem, just that my shell knowledge is too
small:

This code

#!/bin/sh

IFS=':'
kpsepath=$(kpsewhich --expand-path='$TEXMF')
for path in $kpsepath
do 
  eval FOO=\$path echo $FOO
done

Just echo's nothing, and therefore, if we replace "echo $FOO" by a
kpsewhich call and the assignment to FOO with one to TEXMF, nothing
changes. In some strange way, however, it works in kpsewhere.

What I don't understand that --format has such an 


>
> PS: Congratulations to the new inhabitant.
>

-- 
Frank Küster
Debian Developer (teTeX/TeXLive)


--- End Message ---

Reply to: