- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

by Torsten Bergmann

Hi Alistair, cant look right now but two things: - there are also events in the protocol - if we could hook Pharo into them this would solve the problem without abusing delay (because then you will get informed when the page loading is finished) - you can write "5 seconds wait" in Pharo Bye T. > Gesendet: Freitag, 19. Mai 2017 um 17:51 Uhr > Von: "Alistair Grant" <akgrant0710(a)gmail.com> > An: pharo-dev(a)lists.pharo.org > Betreff: Re: [Pharo-dev] Chrome DevTools Protocol and Pharo > > On Fri, May 19, 2017 at 01:50:28PM +0200, Torsten Bergmann wrote: > > Alistair Grant wrote > > > > > This looks really interesting, thanks for making it available. I'm on > > > linux, so I guess it will need some porting. > > > > I added support for Linux and tried on Ubuntu with Chromium. Works - see screenshot > > Fantastic, thanks! > > I did have to change your script for it to work on my laptop: > > 1. isInDebugMode is false by default, which meant that chrome wasn't > launched with remote debugging enabled. > > 2. Retrieving the remotes in GoogleChrome class>>tabPages failed because > the browser hadn't had time to start up. I'll submit a pull request > which adds a retry with delay. > > 3. I initially got a white image. This appears to be because the script > doesn't wait for the navigation to complete before taking the > screenshot. I just added an ugly delay, but I'm not yet sure what the best > solution here is. > > > | chrome page | > > chrome := GoogleChrome new > debugOn; > open; > yourself. > page := chrome tabPages first. > page navigateTo: 'http://www.pharo.org'. > (Delay forSeconds: 5) wait. > page captureScreenshot scaledToSize: 200@300. > > > > You need to load my OSLinux package (instead of OSOSX) from catalog. Or start > > Chrom manually in debug mode. > > > > In the Pharo settings browser you can set the path to the chrome executable > > and the debug port to use. > > I doubt that the chrome executable is in that many different places. > Would you be open accepting a pull request which adds (what I assume is) > the Ubuntu 16.04 default location? > > > > Will add Windows support as well (using my OSWindows package) > > > > > Do you know how the DevTools protocol relates to headless chome, which > > > will be available in Chrome 59? > > > See https://developers.google.com/web/updates/2017/04/headless-chrome > > > > Dont know - just try it. > > > > > In particular, is it possible to dump the DOM with your package? > > > > I've seen that Brackets editor as well as Netbeans open Chrome to > > display webpages when editing and refresh when typing. Wanted > > to find out how it was done. > > > > I have not implemented the full protocol. Only what was needed to show > > that it is possible and to do things like grabbing screenshots from websites > > using Pharo. > > I've found a page that describes accessing the DOM, so it looks like it > should be possible. I'll see what I can do... > > > There is a DOM domain that one could wrap - basically it is just > > sending JSON around, see > > https://chromedevtools.github.io/devtools-protocol > > > > With > > > > chrome := GoogleChrome open. > > chrome jsProtocolJSON. > > chrome browseProtocolJSON > > > > you can now even retrieve the Protocol as JSON for the specific browser. > > With a little bit more work it should be possible to even generate > > the wrapper classes/methods from such a protocol spec. > > Thanks again, > Alistair > > > >

May 19, 2017

Epicea and #name in #behaviorAffectedName

by Torsten Bergmann

Hi, in latest Pharo 6 image 60494 I run into some trouble today where the deprecation warning dialog popped up and repeated itself unstoppable due to Epicea. It is hard to reproduce but what I found out was that I had a class modification (represented by EpClassModification) which run into a state where "newClass" was nil and therefore in EpClassModification>>#behaviorAffectedName the message #name was sent to nil. So #name was found in Object and as we all know we deprecated it now which lead to the deprecation dialog, leading to the deprecation dialog, leading to the deprecation dialog, ... Nearly all implementors of Epiceas #behaviorAffectedName send #name which is ok if there is a valid object it is sent to. I do not know if we should protect them somehow in case something goes wrong (like having nil in newClass) or if we should keep this untouched. At least I wanted to inform because I do not know if this later gets others into trouble too and losing their changes because Epicea does not record. Thanks T.

May 19, 2017

Re: [Pharo-dev] Launcher and Pharo 6 Errors on Mac

by Sean P. DeNigris

Ben Coman wrote > What do you get installing from the Catalogue into a fresh Image and > manually updating? When you say "fresh image", what do you have in mind because I got the same error with a Pharo 6 from the CI, so it doesn't seem to be a launcher issue. Sorry if I was not clear... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-and-Pharo-6-Errors-on-Mac-tp4947652p4947665.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 19, 2017

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

by Ben Coman

Would you be interested in trying it with BSD Licensed Chromium... https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md which could be packaged with a Pharo distribution. cheers -ben P.S. on the idea of an in-Image browser, this looks interesting... https://en.wikipedia.org/wiki/Chromium_Embedded_Framework On Fri, May 19, 2017 at 3:20 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > I played around with remote controlling Google Chrome from > Pharo using Chrome DevTools Protocol [1] (based on WebSockets). > > The video shows an example using latest Pharo 6 on Mac: > https://www.youtube.com/watch?v=9F5FrQTEJWY > > Initial Code is on GitHub [2] if someone is interested, > requires OSOSX and Zinc Websockets to be loaded. > > Have fun > T. > > [1] https://chromedevtools.github.io/devtools-protocol > [2] https://github.com/astares/Pharo-Chrome > >

May 19, 2017

Re: [Pharo-dev] Launcher and Pharo 6 Errors on Mac

by Ben Coman

What do you get installing from the Catalogue into a fresh Image and manually updating? cheers -ben On Fri, May 19, 2017 at 10:48 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > On image start, I get "PrimitiveFailed: primitive #createDirectory: in > MacStore failed" for > /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kc0000gn > /T/AppTranslocation/4EF86F92-66D6-4944-8B30-FBCD96118FCC/d/ > Pharo.app/Contents/Resources/pharo-local > > When I try to Quit, I get "PrimitiveFailed: primitive #primSize: in > MultiByteFileStream failed" from `SourceFiles changesFileStream size` > > FYI I got the same results when I downloaded: > - the latest Launcher from > https://ci.inria.fr/pharo/view/Launcher/job/Launcher/ > PHARO=60,VERSION=stable,VM=vm,label=linux/lastSuccessfulBuild/artifact/ > Pharo-mac.zip > - Pharo 6 from http://files.pharo.org/platform/Pharo6.0-mac.zip > > Mac Sierra 10.12.3 > > From the Pharo 6 download: > > Image > ----- > /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kc0000gn > /T/AppTranslocation/C2941508-46E0-4CEC-8573-CBC4488351B0/d/ > Pharo6.0.app/Contents/Resources/Pharo6.0.image > Pharo6.0 > Latest update: #60494 > Unnamed > > Virtual Machine > --------------- > /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kc0000gn > /T/AppTranslocation/C2941508-46E0-4CEC-8573-CBC4488351B0/d/ > Pharo6.0.app/Contents/MacOS/Pharo > CoInterpreter VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > Mac OS X built on May 2 2017 17:03:29 UTC Compiler: 4.2.1 Compatible Apple > LLVM 6.1.0 (clang-602.0.53) > VMMaker versionString VM: 201705021552 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 2 > 08:52:41 2017 -0700 $ Plugins: 201705021552 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > CoInterpreter VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ > Launcher-and-Pharo-6-Errors-on-Mac-tp4947652.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

May 19, 2017

Re: [Pharo-dev] [Pharo-users] Need help with Pillar

by Alexandre Bergel

Okay, will check! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 19, 2017, at 10:35 AM, Damien Pollet <damien.pollet+pharo(a)gmail.com> wrote: > > I think it would have updated stuff. Hopefully. > > As an alternative, to run in docker : > - delete pharo-vm (because if it's a mac VM it will not work in the linux container) > - docker run --rm -tiv $PWD:/work dpollet/texlive:pillar make pdfbook > > Docker is what the travis builds use, you can check the config file in books that I have recently updated, e.g. https://github.com/SquareBracketAssociates/Booklet-Glorp/blob/master/.travi… <https://github.com/SquareBracketAssociates/Booklet-Glorp/blob/master/.travi…> > > > On 19 May 2017 at 16:27, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > I get the following: > > ~/Dropbox/Pillar> tlmgr update --self --all > TeX Live 2016 is frozen forever and will no > longer be updated. This happens in preparation for a new release. > > If you're interested in helping to pretest the new release (when > pretests are available), please read http://tug.org/texlive/pretest.html <http://tug.org/texlive/pretest.html>. > Otherwise, just wait, and the new release will be ready in due time. > tlmgr: package repository http://ftp.inf.utfsm.cl/pub/tex-archive/systems/texlive/tlnet <http://ftp.inf.utfsm.cl/pub/tex-archive/systems/texlive/tlnet> (not verified: gnupg not available) > You don't have permission to change the installation in any way, > specifically, the directory /usr/local/texlive/2016/tlpkg/ is not writable. > Please run this program as administrator, or contact your local admin. > tlmgr: An error has occurred. See above messages. Exiting. > ~/Dropbox/Pillar> > > I use the installation of TeXlive on my machine since I have no idea who to make the docker image use my local files. > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On May 19, 2017, at 10:06 AM, Damien Pollet <damien.pollet(a)gmail.com <mailto:damien.pollet@gmail.com>> wrote: >> >> I think you still have a TeXlive snapshot from earlier this year. Try this : >> tlmgr update --self --all >> >> On 19 May 2017 at 15:19, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> Hi Damien! >> >> Apparently the INRIA CI is getting better. I could get the archetype. I have another error when compiling the book. I get: >> Sidefoothsep and sidefootwidth: 2.46019mm and 44.98633mm >> Sidefootvsep and sidefootheight: 4.21747mm and 192.73828mm >> ****************************************************** >> >> (/usr/local/texlive/2016/texmf-dist/tex/latex/datetime2/datetime2.sty >> (/usr/local/texlive/2016/texmf-dist/tex/latex/tracklang/tracklang.sty >> (/usr/local/texlive/2016/texmf-dist/tex/generic/tracklang/tracklang.tex))) >> Runaway argument? >> \pdffeedback creationdate\@dtm@endparsepdfdatetime \let \@dtm@currentyear \ETC. >> >> ./root/support/latex/common.tex:5: File ended while scanning use of \@dtm@parse >> pdfdatetime. >> <inserted text> >> \par >> l.5 >> >> 1217 words of node memory still in use: >> 2 hlist, 1 rule, 1 dir, 34 glue, 9 attribute, 167 glue_spec, 9 attribute_lis >> t, 3 write, 1 pdf_colorstack nodes >> avail lists: 2:24,3:1,5:2,6:4,7:1,8:1,9:2 >> ./root/support/latex/common.tex:5: ==> Fatal error occurred, no output PDF fil >> e produced! >> Transcript written on book.log. >> Latexmk: Errors, so I did not complete making targets >> Collected error summary (may duplicate other messages): >> pdflatex: Command for 'pdflatex' gave return code 256 >> Latexmk: Use the -f option to force complete processing, >> unless error was exceeding maximum runs of latex/pdflatex. >> make[1]: *** [book.pdf] Error 12 >> make: *** [build/book.pdf] Error 2 >> ~/Dropbox/Pillar> >> >> Is it because of some missing Latex .cls? If yes, which one? How can I install them? >> >> Thanks for your help! >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On May 18, 2017, at 7:43 AM, Damien Pollet <damien.pollet(a)gmail.com <mailto:damien.pollet@gmail.com>> wrote: >>> >>> On 18 May 2017 at 01:34, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>> curl https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh <https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh> | bash >>> >>> I had to copy PharoV50.sources in the folder pharo-vm/ apparently. >>> >>> Hmm strange I got that this morning as well with ClÃ©ment's book. >>> The script installs a PharoV60.sources so most probably it installs the latest VM; might be a problem if Pillar really relies on Pharo 5â¦ >>> >>> Getting the archetype book gives me an error: >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >>> /tmp/pillar> ./pillar archetype book >>> >>> Which website is it trying to get access to? >>> >>> That would be Inria CI, they're having problems with CloudStack currently >>> >>> >>> -- >>> Damien Pollet >>> type less, do more [ | ] http://people.untyped.org/damien.pollet <http://people.untyped.org/damien.pollet> >> >> >> >> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet <http://people.untyped.org/damien.pollet> > >

May 19, 2017

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

by Alistair Grant

On Fri, May 19, 2017 at 01:50:28PM +0200, Torsten Bergmann wrote: > Alistair Grant wrote > > > This looks really interesting, thanks for making it available. I'm on > > linux, so I guess it will need some porting. > > I added support for Linux and tried on Ubuntu with Chromium. Works - see screenshot Fantastic, thanks! I did have to change your script for it to work on my laptop: 1. isInDebugMode is false by default, which meant that chrome wasn't launched with remote debugging enabled. 2. Retrieving the remotes in GoogleChrome class>>tabPages failed because the browser hadn't had time to start up. I'll submit a pull request which adds a retry with delay. 3. I initially got a white image. This appears to be because the script doesn't wait for the navigation to complete before taking the screenshot. I just added an ugly delay, but I'm not yet sure what the best solution here is. | chrome page | chrome := GoogleChrome new debugOn; open; yourself. page := chrome tabPages first. page navigateTo: 'http://www.pharo.org'. (Delay forSeconds: 5) wait. page captureScreenshot scaledToSize: 200@300. > You need to load my OSLinux package (instead of OSOSX) from catalog. Or start > Chrom manually in debug mode. > > In the Pharo settings browser you can set the path to the chrome executable > and the debug port to use. I doubt that the chrome executable is in that many different places. Would you be open accepting a pull request which adds (what I assume is) the Ubuntu 16.04 default location? > Will add Windows support as well (using my OSWindows package) > > > Do you know how the DevTools protocol relates to headless chome, which > > will be available in Chrome 59? > > See https://developers.google.com/web/updates/2017/04/headless-chrome > > Dont know - just try it. > > > In particular, is it possible to dump the DOM with your package? > > I've seen that Brackets editor as well as Netbeans open Chrome to > display webpages when editing and refresh when typing. Wanted > to find out how it was done. > > I have not implemented the full protocol. Only what was needed to show > that it is possible and to do things like grabbing screenshots from websites > using Pharo. I've found a page that describes accessing the DOM, so it looks like it should be possible. I'll see what I can do... > There is a DOM domain that one could wrap - basically it is just > sending JSON around, see > https://chromedevtools.github.io/devtools-protocol > > With > > chrome := GoogleChrome open. > chrome jsProtocolJSON. > chrome browseProtocolJSON > > you can now even retrieve the Protocol as JSON for the specific browser. > With a little bit more work it should be possible to even generate > the wrapper classes/methods from such a protocol spec. Thanks again, Alistair

May 19, 2017

Re: [Pharo-dev] bug in command line handler

by K K Subbu

On Friday 19 May 2017 05:40 PM, Damien Pollet wrote: > I wouldn't want to sound sarcastic, but I'm not sure there is such a > concept as "correct" in the context of ANSI escape sequences. > Still, according to the legends, 97 is supposed to be high intensity > white (for some subset of existing implementations). ;-). My context was command line usage in linux terminals. Anyway, attached is a patch for the annoying bug which fixed the problem for me. I would appreciate if anyone else using the command line can confirm if the patch works for them. E.g. ~~~~ $ ./pharo Pharo.image eval 'ProtoObject methodDict size\;^MProtoObject methodDict keys' Syntax Error on line 1: 'Variable or expression expected' ========================================================= 1: ProtoObject methodDict size\; _^_ 2: ProtoObject methodDict keys $ ./pharo Pharo.image eval 'ProtoObject methodDict size.^MProtoObject methodDict keys;' Syntax Error on line 2: 'Message expected' ========================================== 1: ProtoObject methodDict size. 2: ProtoObject methodDict keys; _^_ $ ~~~~ Thanks .. Subbu

May 19, 2017

Launcher and Pharo 6 Errors on Mac

by Sean P. DeNigris

On image start, I get "PrimitiveFailed: primitive #createDirectory: in MacStore failed" for /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kc0000gn/T/AppTranslocation/4EF86F92-66D6-4944-8B30-FBCD96118FCC/d/Pharo.app/Contents/Resources/pharo-local When I try to Quit, I get "PrimitiveFailed: primitive #primSize: in MultiByteFileStream failed" from `SourceFiles changesFileStream size` FYI I got the same results when I downloaded: - the latest Launcher from https://ci.inria.fr/pharo/view/Launcher/job/Launcher/PHARO=60,VERSION=stabl… - Pharo 6 from http://files.pharo.org/platform/Pharo6.0-mac.zip Mac Sierra 10.12.3 >From the Pharo 6 download: Image ----- /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kc0000gn/T/AppTranslocation/C2941508-46E0-4CEC-8573-CBC4488351B0/d/Pharo6.0.app/Contents/Resources/Pharo6.0.image Pharo6.0 Latest update: #60494 Unnamed Virtual Machine --------------- /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kc0000gn/T/AppTranslocation/C2941508-46E0-4CEC-8573-CBC4488351B0/d/Pharo6.0.app/Contents/MacOS/Pharo CoInterpreter VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Mac OS X built on May 2 2017 17:03:29 UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53) VMMaker versionString VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ CoInterpreter VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-and-Pharo-6-Errors-on-Mac-tp4947652.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 19, 2017

Re: [Pharo-dev] [Pharo-users] Need help with Pillar

by Damien Pollet

I think it would have updated stuff. Hopefully. As an alternative, to run in docker : - delete pharo-vm (because if it's a mac VM it will not work in the linux container) - docker run --rm -tiv $PWD:/work dpollet/texlive:pillar make pdfbook Docker is what the travis builds use, you can check the config file in books that I have recently updated, e.g. https://github.com/SquareBracketAssociates/Booklet-Glorp/blob/master/.travi… On 19 May 2017 at 16:27, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > I get the following: > > ~/Dropbox/Pillar> tlmgr update --self --all > TeX Live 2016 is frozen forever and will no > longer be updated. This happens in preparation for a new release. > > If you're interested in helping to pretest the new release (when > pretests are available), please read http://tug.org/texlive/pretest.html. > Otherwise, just wait, and the new release will be ready in due time. > tlmgr: package repository http://ftp.inf.utfsm.cl/pub/ > tex-archive/systems/texlive/tlnet (not verified: gnupg not available) > You don't have permission to change the installation in any way, > specifically, the directory /usr/local/texlive/2016/tlpkg/ is not writable. > Please run this program as administrator, or contact your local admin. > tlmgr: An error has occurred. See above messages. Exiting. > ~/Dropbox/Pillar> > > I use the installation of TeXlive on my machine since I have no idea who > to make the docker image use my local files. > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On May 19, 2017, at 10:06 AM, Damien Pollet <damien.pollet(a)gmail.com> > wrote: > > I think you still have a TeXlive snapshot from earlier this year. Try this > : > tlmgr update --self --all > > On 19 May 2017 at 15:19, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> Hi Damien! >> >> Apparently the INRIA CI is getting better. I could get the archetype. I >> have another error when compiling the book. I get: >> Sidefoothsep and sidefootwidth: 2.46019mm and 44.98633mm >> Sidefootvsep and sidefootheight: 4.21747mm and 192.73828mm >> ****************************************************** >> >> (/usr/local/texlive/2016/texmf-dist/tex/latex/datetime2/datetime2.sty >> (/usr/local/texlive/2016/texmf-dist/tex/latex/tracklang/tracklang.sty >> (/usr/local/texlive/2016/texmf-dist/tex/generic/tracklang/ >> tracklang.tex))) >> Runaway argument? >> \pdffeedback creationdate\@dtm@endparsepdfdatetime \let \@dtm@currentyear >> \ETC. >> >> ./root/support/latex/common.tex:5: File ended while scanning use of >> \@dtm@parse >> pdfdatetime. >> <inserted text> >> \par >> l.5 >> >> 1217 words of node memory still in use: >> 2 hlist, 1 rule, 1 dir, 34 glue, 9 attribute, 167 glue_spec, 9 >> attribute_lis >> t, 3 write, 1 pdf_colorstack nodes >> avail lists: 2:24,3:1,5:2,6:4,7:1,8:1,9:2 >> ./root/support/latex/common.tex:5: ==> Fatal error occurred, no output >> PDF fil >> e produced! >> Transcript written on book.log. >> Latexmk: Errors, so I did not complete making targets >> Collected error summary (may duplicate other messages): >> pdflatex: Command for 'pdflatex' gave return code 256 >> Latexmk: Use the -f option to force complete processing, >> unless error was exceeding maximum runs of latex/pdflatex. >> make[1]: *** [book.pdf] Error 12 >> make: *** [build/book.pdf] Error 2 >> ~/Dropbox/Pillar> >> >> Is it because of some missing Latex .cls? If yes, which one? How can I >> install them? >> >> Thanks for your help! >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> On May 18, 2017, at 7:43 AM, Damien Pollet <damien.pollet(a)gmail.com> >> wrote: >> >> On 18 May 2017 at 01:34, Alexandre Bergel <alexandre.bergel(a)me.com> >> wrote: >> >>> curl https://raw.githubusercontent.com/pillar-markup/pillar/maste >>> r/download.sh | bash >>> >>> I had to copy PharoV50.sources in the folder pharo-vm/ apparently. >>> >> >> Hmm strange I got that this morning as well with ClÃ©ment's book. >> The script installs a PharoV60.sources so most probably it installs the >> latest VM; might be a problem if Pillar really relies on Pharo 5â¦ >> >> >>> Getting the archetype book gives me an error: >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >>> /tmp/pillar> ./pillar archetype book >>> >>> Which website is it trying to get access to? >>> >> >> That would be Inria CI, they're having problems with CloudStack currently >> >> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet >> >> >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > >

May 19, 2017