[Bug 331884] New: Some omega or xetex files aren' t found by kpsewhich after installation of the relevant packages
https://bugzilla.novell.com/show_bug.cgi?id=331884 Summary: Some omega or xetex files aren't found by kpsewhich after installation of the relevant packages Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: auxsvr@yahoo.com QAContact: qa@suse.de Found By: --- Some files, such as fmt and fonts, aren't found when invoking omega or xetex. The problem is that after installation of texlive-omega or texlive-xetex, texhash isn't run. By the way, this https://bugzilla.novell.com/show_bug.cgi?id=232451 no longer occurs with texlive, everything works fine after a texhash, except from xetex, when selecting fonts. I assume that xetex is unstable, is this correct? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884 Mark Gordon <mtgordon@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtgordon@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |werner@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c1 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |auxsvr@yahoo.com --- Comment #1 from Dr. Werner Fink <werner@novell.com> 2007-10-09 03:46:30 MST --- Please call as root SuSEconfig does this help? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c2 John McManaman <auxsvr@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|auxsvr@yahoo.com | --- Comment #2 from John McManaman <auxsvr@yahoo.com> 2007-10-09 07:53:40 MST --- I removed texlive-omega and the bin RPM from YaST and none of the ls-R (/etc/texmf/ls-R, /var/lib/texmf/ls-R, /var/lib/texmf/db/ls-R) files was updated after I ran SuSEconfig. I did a texhash, installed texlive-omega and the bin and the ls-R files weren't updated again (YaST runs SuSEconfig, I ran it once more). A simple texhash solves the problem. I mount the root filesystem with noatime, is this related? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c3 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |auxsvr@yahoo.com --- Comment #3 from Dr. Werner Fink <werner@novell.com> 2007-10-09 08:06:37 MST --- Yes this could be the reason because SuSEconfig.texlive compares access times to update the ls-R files but not only ls-R also the font maps are updated as well. To test this do a simple touch /var/adm/SuSEconfig/run-texhash /sbin/conf.d/SuSEconfig.texlive then we should see that not only texhash is called but also updmap-sys, see line 53ff of /sbin/conf.d/SuSEconfig.texlive -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c4 John McManaman <auxsvr@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|auxsvr@yahoo.com | --- Comment #4 from John McManaman <auxsvr@yahoo.com> 2007-10-09 09:14:56 MST --- I remounted the filesystem with atime and the problem persists. I checked the te_omega RPM from openSUSE 10.2 and it includes a post-installation script that creates /var/adm/SuSEconfig/run-texhash. The openSUSE 10.3 one doesn't. Adding this should fix the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c5 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |auxsvr@yahoo.com --- Comment #5 from Dr. Werner Fink <werner@novell.com> 2007-10-09 09:53:10 MST --- Hmm .. this I do not understand, see: werner/texlive> rpm -q --scripts -p noarch/texlive-omega.rpm postinstall scriptlet (through /bin/sh): mkdir -p var/adm/SuSEconfig; touch var/adm/SuSEconfig/run-texhash postuninstall scriptlet (through /bin/sh): mkdir -p var/adm/SuSEconfig; touch var/adm/SuSEconfig/run-texhash this is what I have. Please run rpm -q --scripts texlive-omega and paste the result herin -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c6 John McManaman <auxsvr@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|auxsvr@yahoo.com | --- Comment #6 from John McManaman <auxsvr@yahoo.com> 2007-10-10 01:02:55 MST --- Yes, you're correct, I was checking the bin-omega RPM, the omega one is fine as you say. I investigated this further, and if I add: TEST=${1+$@} before line 64, and change line 64 of /sbin/conf.d/SuSEconfig.texlive into: set -- $(find $TEST -prune -type d -and -not -fstype nfs -print 2> /dev/null) , it works fine. If I omit the redirection to /dev/null at the end, find gives a weird error message (find: invalid predicate `'), which makes me think that either bash or find is buggy. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c7 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |auxsvr@yahoo.com --- Comment #7 from Dr. Werner Fink <werner@novell.com> 2007-10-10 03:03:55 MST --- In other words the ${1+"$@"} returns nothing but an empty string, this means that kpsewhich --show-path=ls-R does not return any path for ls-R files. And this seems to happen only after installing texlive-omega ... strange. IMHO kpsewhich should return something like /suse/werner> IFS=':;' /suse/werner> set -- $(kpsewhich --show-path=ls-R 2> /dev/null) /suse/werner> IFS="$OLDIFS" /suse/werner> echo $@ /suse/werner/texmf /usr/local/share/texmf /etc/texmf /var/lib/texmf /usr/share/texmf /var/cache/fonts .. please test if the first command `kpsewhich --show-path=ls-R' returns also an error and if yes which error is returned or does the command return nothing but an empty string? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c8 --- Comment #8 from Dr. Werner Fink <werner@novell.com> 2007-10-10 03:09:58 MST --- Beside this, what does the command texhash return on stdout/stderr? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c9 John McManaman <auxsvr@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|auxsvr@yahoo.com | --- Comment #9 from John McManaman <auxsvr@yahoo.com> 2007-10-10 03:15:47 MST --- Perhaps I didn't explain this well: the find command runs correctly only if it doesn't include the ${1+"$@"}, that's why it looks like a bash bug. If I replace it with a variable, everything works fine. I tried every line in the file and every single line works except for the find. The output of texhash is normal: texhash: Updating /etc/texmf/ls-R... texhash: Updating /usr/share/lilypond/2.10.29/ls-R... texhash: Updating /usr/share/texmf/../../../var/lib/texmf/db/ls-R... texhash: Updating /var/cache/fonts/ls-R... texhash: Updating /var/lib/texmf/ls-R... texhash: Done. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c10 --- Comment #10 from John McManaman <auxsvr@yahoo.com> 2007-10-10 03:22:00 MST --- linux:~ # kpsewhich --show-path=ls-R /root/texmf:/usr/local/share/texmf:/etc/texmf:/var/lib/texmf:/usr/share/texmf::/var/cache/fonts:/usr/share/lilypond/2.10.29 Everything is normal except for the find line. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c11 --- Comment #11 from Dr. Werner Fink <werner@novell.com> 2007-10-10 03:42:27 MST --- Ahh ... the `::' within the path is annoying, this leads to an empty string within the expansion ${1+"$@"} which is visible as `' if `set -x' is used for debugging. Maybe I should use your trick of simply $@ or prepend an `eval' before the find command. Thanks for spotting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c12 --- Comment #12 from Dr. Werner Fink <werner@novell.com> 2007-10-10 03:55:00 MST --- Created an attachment (id=177308) --> (https://bugzilla.novell.com/attachment.cgi?id=177308) /sbin/conf.d/SuSEconfig.texlive A fixed version of SuSEconfig.texlive Could you please test this out? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c13 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |auxsvr@yahoo.com --- Comment #13 from Dr. Werner Fink <werner@novell.com> 2007-10-10 03:59:41 MST --- Does the new /sbin/conf.d/SuSEconfig.texlive in the attachment (id=177308) work for you? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c14 John McManaman <auxsvr@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|auxsvr@yahoo.com | --- Comment #14 from John McManaman <auxsvr@yahoo.com> 2007-10-10 05:37:42 MST --- Yes, this file works fine. The problem above still confuses me, though. What is the difference between TEST=${1+"$@"} and then "find $TEST ...", and find ${1+"$@"}... ? Shouldn't they do exactly the same thing? My version, that works, is: OLDIFS="${IFS}" IFS=':;' set -- $(kpsewhich --show-path=ls-R 2> /dev/null) IFS="${OLDIFS}" TEST=${1+"$@"} set -- $(find $TEST -prune -type d -and -not -fstype nfs -print 2> /dev/null) This one doesn't work: OLDIFS="${IFS}" IFS=':;' set -- $(kpsewhich --show-path=ls-R 2> /dev/null) IFS="${OLDIFS}" # TEST=${1+"$@"} set -- $(find ${1+"$@"} -prune -type d -and -not -fstype nfs -print 2> /dev/null) Why? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c15 --- Comment #15 from Dr. Werner Fink <werner@novell.com> 2007-10-10 06:22:30 MST --- IMHO the line TEST=${1+"$@"} holds the empty string caused by the `::' in the path. Now if you use ${TEST} for the find command this works like eval find ${1+"$@"} -prune -type d -and -not -fstype nfs -print that means that ${1+"$@"} is evaled before the find command and therefore the empty string caused by the `::' is vanished: bash> OLDIFS="$IFS" bash> IFS=":" bash> set -- $(echo a::b:c) bash> IFS="$OLDIFS" bash> echo $# 4 bash> TEST=${1+"$@"} bash> echo ${TEST} | wc -c 6 bash> echo "${TEST}" | wc -c 7 if you use echo a:b:c the number of positional parameters is 3 and both wc tests leads to 6 characters. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c16 --- Comment #16 from John McManaman <auxsvr@yahoo.com> 2007-10-10 11:51:59 MST --- I might be missing something obvious here, yet I still don't understand. How do you explain this: linux:~> OLDIFS="${IFS}" linux:~> IFS=':;' linux:~> set -- $(kpsewhich --show-path=ls-R 2> /dev/null) linux:~> IFS="${OLDIFS}" linux:~> echo ${1+"$@"} /home/$USER/texmf /usr/local/share/texmf /etc/texmf /var/lib/texmf /usr/share/texmf /var/cache/fonts /usr/share/lilypond/2.10.29 and this: linux:~> unset TEST linux:~> OLDIFS="${IFS}" linux:~> IFS=':;' linux:~> set -- $(kpsewhich --show-path=ls-R 2> /dev/null) linux:~> IFS="${OLDIFS}" linux:~> TEST=${1+"$@"} linux:~> echo $TEST /home/$USER/texmf /usr/local/share/texmf /etc/texmf /var/lib/texmf /usr/share/texmf /var/cache/fonts /usr/share/lilypond/2.10.29 The only difference is a double space after /usr/share/texmf. Everything above is normal IMHO, there is no empty string here. Also, in the case of empty variables: linux:~> test -z $NONEXISTENT && echo "NONEXISTENT is empty" NONEXISTENT is empty linux:~> find $NONEXISTENT -prune -type d -and -not -fstype nfs -print <------- this is the output. Everything is normal again! However, linux:~> echo $@ /home/$USER/texmf /usr/local/share/texmf /etc/texmf /var/lib/texmf /usr/share/texmf /var/cache/fonts /usr/share/lilypond/2.10.29 linux:~> find ${1+"$@"} -prune -type d -and -not -fstype nfs -print find: invalid predicate `' This is weird. It makes no sense. ${1+"$@"} is not empty, even if it were, there shouldn't be an error message, which, by the way, makes no sense! I thought bash was substituting to the respective argument positions according to some well-defined rules (e.g. replace $BASH with /bin/bash, arguments are separated with spaces), how do you reproduce the above error message if you do the substitution yourself? linux:~> find -iasd -prune -type d -and -not -fstype nfs -print find: invalid predicate `-iasd' linux:~> find - -prune -type d -and -not -fstype nfs -print find: invalid predicate `-' linux:~/> find -$NONEXISTENT -prune -type d -and -not -fstype nfs -print find: invalid predicate `-' The 3 above make sense, the line with the find ${1+"$@"} doesn't. I wasn't able to find this in the documentation, so I insist that this is a bug or not intended behaviour. I ought to apologize about my persistence, however I'm still not convinced that this is intented and normal behaviour. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c17 --- Comment #17 from Dr. Werner Fink <werner@novell.com> 2007-10-11 02:30:57 MST --- Simple test: bash> set -- '' bash> find ${1+"$@"} find: invalid predicate `' bash> set -- bash> find ${1+"$@"} . ./README.import ./source-dvipdfm-security.patch ./source-poppler.dif ./source-warns.dif ./texmfsrc.tar.bz2 it is the empty string (no space) which endure due to the double quotes around the $@ witin ${1+"$@"} ... this is intended, see manual page of the bash in the section `Special Parameters': [...] @ Expands to the positional parameters, starting from one. When the expansion occurs within double quotes, each parameter expands to a separate word. That is, "$@" is equivalent to "$1" "$2" ... When there are no positional parameters, "$@" and $@ expand to nothing (i.e., they are removed). [...] this can be used to let blanks and spaces survive an expansion: bash> mkdir 'a b' bash> set -- 'a b' bash> echo $1 a b bash> find ${1+"$@"} -ls 54540903 0 drwxr-xr-x 2 werner suse 6 Oct 11 10:28 a\ b -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c18 --- Comment #18 from John McManaman <auxsvr@yahoo.com> 2007-10-12 05:06:14 MST --- I didn't know that empty strings could be interpreted by bash as a separate argument. Thank you for the clarification, it still looks weird, yet is the documented behaviour. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884#c19 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #19 from Dr. Werner Fink <werner@novell.com> 2007-12-03 10:09:03 MST --- fixed and submitted (at least for next release of openSuSE) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331884 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=331884#c20 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Markus.Kuhn@cl.cam.ac.uk --- Comment #20 from Dr. Werner Fink <werner@novell.com> 2008-01-16 06:13:54 MST --- *** Bug 353511 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=353511 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com