[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] write document failure on windows
From: |
Sebastian Hilbert |
Subject: |
Re: [Gnumed-devel] write document failure on windows |
Date: |
Thu, 12 May 2011 12:44:40 +0200 |
User-agent: |
KMail/1.13.6 (Linux/2.6.38.4-23-desktop; KDE/4.6.0; i686; ; ) |
Am Donnerstag, 12. Mai 2011, 11:36:07 schrieb address@hidden:
Let's see
> 2011-05-12 15:07:37 INFO gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #131): running shell command
> >>>pdflatex.exe -interaction nonstopmode
> c:\docume~1\newuse~1\locals~1\temp\gnumed\gm-r8tppv\gm-L-Template-fksvt1\g
> m-L-Template-fksvt1-instance.tex<<< 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #134): os.system() returned:
> [0]
> 2011-05-12 15:07:40 ERROR gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #139): platform does not
> support exit status differentiation
> 2011-05-12 15:07:40 INFO gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #141): os.system() return value
> contained in acceptable return codes 2011-05-12 15:07:40 INFO
> gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #142): continuing and hoping
> for the best
pdf was created
> 2011-05-12 15:07:40 DEBUG gm.printing
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmprinting::print_file_by_shellscript() #29): printing
> "generic_document":
> [c:\docume~1\newuse~1\locals~1\temp\gnumed\gm-r8tppv\gm-L-Template-fksvt1-i
> nstance.pdf]
wants to print it
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::find_first_binary() #76): looking for [gm-print_doc]
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::detect_external_binary() #18): detecting
> [gm-print_doc]
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::detect_external_binary() #30): [which gm-print_doc]
> failed, exit code: 1
linux shell script not usable. That is ok
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::find_first_binary() #76): looking for
> [gm-print_doc.bat]
That is more like it. However I don't ship such a batch file (at least I need
to check). So this should fail
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::detect_external_binary() #18): detecting
> [gm-print_doc.bat]
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::detect_external_binary() #30): [which
> gm-print_doc.bat] failed, exit code: 1
well the which command does not make much sense on Windows so even if there
was gm-print_doc.bat we need a Windows way of detecting it or put it into the
PATH
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::find_first_binary() #76): looking for [C:\Program
> Files\GNUmed-client\bin\..\external-tools\gm-print_doc]
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::detect_external_binary() #18): detecting [C:\Program
> Files\GNUmed-client\bin\..\external-tools\gm-print_doc]
yep. not there
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::detect_external_binary() #30): [which C:\Program
> Files\GNUmed-client\bin\..\external-tools\gm-print_doc] failed, exit code:
> 1 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::find_first_binary() #76): looking for
> [gm-print_doc.bat]
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::detect_external_binary() #18): detecting
> [gm-print_doc.bat]
we could put the bat file there
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::detect_external_binary() #30): [which
> gm-print_doc.bat] failed, exit code: 1
which command is of no use here
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #99): shell command
> >>>gm-print_doc.bat generic_document
> c:\docume~1\newuse~1\locals~1\temp\gnumed\gm-r8tppv\gm-L-Template-fksvt1-in
> stance.pdf<<<
Guess this is os level shot in the dark ?
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #100): blocking: True
> 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #101): acceptable return codes:
> [0]
> 2011-05-12 15:07:40 INFO gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #131): running shell command
> >>>gm-print_doc.bat generic_document
> c:\docume~1\newuse~1\locals~1\temp\gnumed\gm-r8tppv\gm-L-Template-fksvt1-i
> nstance.pdf<<< 2011-05-12 15:07:40 DEBUG gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #134): os.system() returned:
> [1]
> 2011-05-12 15:07:40 ERROR gm.shell
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmshellapi::run_command_in_shell() #139): platform does not
> support exit status differentiation
> 2011-05-12 15:07:40 ERROR gm.printing
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> pycommon.gmprinting::print_file_by_shellscript() #51): print command failed
no kidding.
> 2011-05-12 15:08:05 ERROR gm.gui
> (c:\workplace\gnumed-client.0.9.4\build\pyi.win32\setup\outpyz1.pyz\gnumed.
> wxpython.gmexceptionhandlingwidgets::mail_log() #357): printing current
> medication
Ok. All I see here is GNUmed trying to run the (non existant) gm-print_doc.bat
I thought there would be other means like Adobe reader and friends ? Did I
overlook this ?
Sebastian
- [Gnumed-devel] write document failure on windows, vbanait, 2011/05/12
- Re: [Gnumed-devel] write document failure on windows,
Sebastian Hilbert <=
- Re: [Gnumed-devel] write document failure on windows, Karsten Hilbert, 2011/05/12
- Re: [Gnumed-devel] write document failure on windows, Sebastian Hilbert, 2011/05/12
- Re: [Gnumed-devel] write document failure on windows, LuisCapriles, 2011/05/13
- Re: [Gnumed-devel] write document failure on windows, Sebastian Hilbert, 2011/05/13
- Re: [Gnumed-devel] write document failure on windows, LuisCapriles, 2011/05/13
- Re: [Gnumed-devel] write document failure on windows, Sebastian Hilbert, 2011/05/13
- Re: [Gnumed-devel] write document failure on windows, Karsten Hilbert, 2011/05/13
- Re: [Gnumed-devel] write document failure on windows, Karsten Hilbert, 2011/05/13
- Re: [Gnumed-devel] write document failure on windows, Karsten Hilbert, 2011/05/13
- Re: [Gnumed-devel] write document failure on windows, Karsten Hilbert, 2011/05/13