Re: zp_fontconfig_cache_1.sh exit code 2
On 13 June 2016 at 01:35, Ken Brown wrote: > On 6/12/2016 7:26 PM, Mark McGregor wrote: >> >> Ken wrote: >>> >>> I obtained the output in the attachment, which looks good. Are you saying >>> that the message is bogus and no action is needed? >> >> >> Yes. >> >> >> Ok, thanks! It is nice to know than nothing is broken in this respect. But >> it would be also nice to get less bogus messages. > > > Agreed. I took a brief look at the fontconfig code at one point to see if I > could figure out why this was happening, but I didn't succeed and didn't > feel like spending a lot of time on it. > > Ken I have recently experienced this as well. Some sources (https://bugs.archlinux.org/task/6024 and http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg266900.html) suggest that it is some sort of time stamp related issue? -- VH -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: zp_fontconfig_cache_1.sh exit code 2
On 6/12/2016 7:26 PM, Mark McGregor wrote: Ken wrote: I obtained the output in the attachment, which looks good. Are you saying that the message is bogus and no action is needed? Yes. Ok, thanks! It is nice to know than nothing is broken in this respect. But it would be also nice to get less bogus messages. Agreed. I took a brief look at the fontconfig code at one point to see if I could figure out why this was happening, but I didn't succeed and didn't feel like spending a lot of time on it. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: zp_fontconfig_cache_1.sh exit code 2
Ken wrote: > I obtained the output in the attachment, which looks good. Are you saying > that the message is bogus and no action is needed? Yes. Ok, thanks! It is nice to know than nothing is broken in this respect. But it would be also nice to get less bogus messages. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: zp_fontconfig_cache_1.sh exit code 2
On 6/12/2016 6:32 PM, Mark McGregor wrote: Ken wrote: The exit code is the number of font caches that fontconfig thinks it failed to write. In fact, I'm pretty sure it actually did successfully write the cache, and the error message is bogus. You can test this by adding the -v flag to the fc-cache invocation in zp_fontconfig_cache_1.sh: /usr/libexec/fc-cache-1 -sv I think you'll find that if you rerun zp_fontconfig_cache_1.sh after it has reported "failed to write cache" on a certain font directory, it will then give a message saying the cache is up to date and doesn't need to be rewritten. That's what I've found, anyway. Ken Thank you. After running $ /etc/postinstall/zp_fontconfig_cache_1.sh I obtained the output in the attachment, which looks good. Are you saying that the message is bogus and no action is needed? Yes. While compiling some (seemingly good) LaTeX file I'm getting [ ... xdvipdfmx:fatal: This font using the "seac" command for accented characters... Output file removed. ) Error 256 (driver return code) generating output; file file.pdf may not be valid. ] I have no idea about whether it is related. I suspect it's unrelated. Please make a separate bug report about that, and I'll see if I can help. Try to cut your LaTeX file down to a minimal file that exhibits the problem. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: zp_fontconfig_cache_1.sh exit code 2
Ken wrote: The exit code is the number of font caches that fontconfig thinks it failed to write. In fact, I'm pretty sure it actually did successfully write the cache, and the error message is bogus. You can test this by adding the -v flag to the fc-cache invocation in zp_fontconfig_cache_1.sh: /usr/libexec/fc-cache-1 -sv I think you'll find that if you rerun zp_fontconfig_cache_1.sh after it has reported "failed to write cache" on a certain font directory, it will then give a message saying the cache is up to date and doesn't need to be rewritten. That's what I've found, anyway. Ken Thank you. After running $ /etc/postinstall/zp_fontconfig_cache_1.sh I obtained the output in the attachment, which looks good. Are you saying that the message is bogus and no action is needed? While compiling some (seemingly good) LaTeX file I'm getting [ ... xdvipdfmx:fatal: This font using the "seac" command for accented characters... Output file removed. ) Error 256 (driver return code) generating output; file file.pdf may not be valid. ] I have no idea about whether it is related./usr/share/fonts: skipping, existing cache is valid: 0 fonts, 6 dirs /usr/share/fonts/100dpi: skipping, existing cache is valid: 0 fonts, 0 dirs /usr/share/fonts/75dpi: skipping, existing cache is valid: 0 fonts, 0 dirs /usr/share/fonts/cyrillic: skipping, existing cache is valid: 0 fonts, 0 dirs /usr/share/fonts/dejavu: skipping, existing cache is valid: 21 fonts, 0 dirs /usr/share/fonts/microsoft: skipping, existing cache is valid: 246 fonts, 0 dirs /usr/share/fonts/misc: skipping, existing cache is valid: 0 fonts, 0 dirs /usr/share/X11/fonts/Type1: skipping, no such directory /usr/share/X11/fonts/TTF: skipping, no such directory /usr/share/ghostscript/fonts: skipping, existing cache is valid: 52 fonts, 0 dirs /usr/local/share/fonts: skipping, no such directory /usr/share/texmf-dist/fonts/opentype: skipping, existing cache is valid: 0 fonts, 11 dirs /usr/share/texmf-dist/fonts/opentype/adobe: skipping, existing cache is valid: 0 fonts, 3 dirs /usr/share/texmf-dist/fonts/opentype/adobe/sourcecodepro: skipping, existing cache is valid: 14 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/adobe/sourcesanspro: skipping, existing cache is valid: 12 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/adobe/sourceserifpro: skipping, existing cache is valid: 6 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/arkandis: skipping, existing cache is valid: 0 fonts, 5 dirs /usr/share/texmf-dist/fonts/opentype/arkandis/accanthis: skipping, existing cache is valid: 4 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/arkandis/berenisadf: skipping, existing cache is valid: 8 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/arkandis/gillius: skipping, existing cache is valid: 16 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/arkandis/mintspirit: skipping, existing cache is valid: 8 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/arkandis/universalis: skipping, existing cache is valid: 8 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/google: skipping, existing cache is valid: 0 fonts, 1 dirs /usr/share/texmf-dist/fonts/opentype/google/noto: skipping, existing cache is valid: 8 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/gust: skipping, existing cache is valid: 0 fonts, 1 dirs /usr/share/texmf-dist/fonts/opentype/gust/poltawski: skipping, existing cache is valid: 40 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/iginomarini: skipping, existing cache is valid: 0 fonts, 1 dirs /usr/share/texmf-dist/fonts/opentype/iginomarini/imfellenglish: skipping, existing cache is valid: 3 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/impallari: skipping, existing cache is valid: 0 fonts, 7 dirs /usr/share/texmf-dist/fonts/opentype/impallari/cabin: skipping, existing cache is valid: 16 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/impallari/librebaskerville: skipping, existing cache is valid: 4 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/impallari/librebodoni: skipping, existing cache is valid: 4 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/impallari/librecaslon: skipping, existing cache is valid: 4 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/impallari/lobster2: skipping, existing cache is valid: 4 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/impallari/quattrocento: skipping, existing cache is valid: 8 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/impallari/raleway: skipping, existing cache is valid: 18 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/kosch: skipping, existing cache is valid: 0 fonts, 1 dirs /usr/share/texmf-dist/fonts/opentype/kosch/crimson: skipping, existing cache is valid: 6 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/nowacki: skipping, existing cache is valid: 0 fonts, 2 dirs /usr/share/texmf-dist/fonts/opentype/nowacki/iwona: skipping, existing cache is valid: 20 fonts, 0 dirs /usr/share/texmf-dist/fonts/opentype/nowacki/ku
Re: zp_fontconfig_cache_1.sh exit code 2
On 6/12/2016 5:32 PM, Mark McGregor wrote: ... and after one more installation, I get exit code 1. Don't ask me why. The exit code is the number of font caches that fontconfig thinks it failed to write. In fact, I'm pretty sure it actually did successfully write the cache, and the error message is bogus. You can test this by adding the -v flag to the fc-cache invocation in zp_fontconfig_cache_1.sh: /usr/libexec/fc-cache-1 -sv I think you'll find that if you rerun zp_fontconfig_cache_1.sh after it has reported "failed to write cache" on a certain font directory, it will then give a message saying the cache is up to date and doesn't need to be rewritten. That's what I've found, anyway. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
zp_fontconfig_cache_1.sh exit code 2
... and after one more installation, I get exit code 1. Don't ask me why. Here is a relevant portion of the log for the following installation: [ ... 2016/06/12 23:23:38 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_update-info-dir.dash" Rebuilding info directory install-info: /usr/share/info/de.utf8: empty file install-info: /usr/share/info/es.utf8: empty file install-info: warning: no info dir entry in `/usr/share/info/maxima-index.lisp' install-info: /usr/share/info/pt.utf8: empty file install-info: /usr/share/info/pt_BR.utf8: empty file install-info: warning: no info dir entry in `/usr/share/info/texdraw.info.gz' 2016/06/12 23:23:44 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_desktop-file-utils.sh" 2016/06/12 23:23:44 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_fontconfig_cache_1.sh" /usr/share/texmf-dist/fonts/type1/public: failed to write cache 2016/06/12 23:23:54 abnormal exit: exit code=1 ... ] Executing this guy afterwards seems ok: $ /etc/postinstall/zp_fontconfig_cache_1.sh $ echo $? 0 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
zp_fontconfig_cache_1.sh exit code 2: update
... Some prior post http://cygwin.com/ml/cygwin/2016-05/msg00264.html said this message might be innocuous, but there the exit code was 1, not 2. ... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
zp_fontconfig_cache_1.sh exit code 2
After a today update I got a postinstall script error from the setup-x86_64 program: [ Package: z/Perpetual zp_fontconfig_cache_1.sh exit code 2 ] Here are some relevant parts of /var/log/setup.log.full: [ ... 2016/06/12 22:30:56 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_update-info-dir.dash" Rebuilding info directory install-info: /usr/share/info/de.utf8: empty file install-info: /usr/share/info/es.utf8: empty file install-info: warning: no info dir entry in `/usr/share/info/maxima-index.lisp' install-info: /usr/share/info/pt.utf8: empty file install-info: /usr/share/info/pt_BR.utf8: empty file 2016/06/12 22:31:08 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-formatsextra.sh" fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order): fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil: /usr/share/texmf-dist/web2c/fmtutil.cnf fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes: fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil [INFO]: exiting with status 1 fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order): fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil: /usr/share/texmf-dist/web2c/fmtutil.cnf fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes: fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil [INFO]: exiting with status 1 fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order): fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil: /usr/share/texmf-dist/web2c/fmtutil.cnf fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes: fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil [INFO]: exiting with status 1 fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order): fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil: /usr/share/texmf-dist/web2c/fmtutil.cnf fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes: fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil [INFO]: exiting with status 1 fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order): fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil: /usr/share/texmf-dist/web2c/fmtutil.cnf fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes: fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil [INFO]: exiting with status 1 2016/06/12 22:31:19 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_desktop-file-utils.sh" 2016/06/12 22:31:19 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_fontconfig_cache_1.sh" /usr/share/texmf-dist/fonts/opentype/public: failed to write cache /usr/share/texmf-dist/fonts/type1/public: failed to write cache 2016/06/12 22:31:41 abnormal exit: exit code=2 ... ] Some prior post http://cygwin.com/ml/cygwin/2016-05/msg00264.html said this message might be innocuous, but there the exit code was 2. Moreover, some of my previously good LaTeX files have recently started to fail to compile, so I have to examine the situation anyhow. Any ideas? Mark. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
