June 2016 - Pharo-users - lists.pharo.org

Information Theory

by Brice GOVIN

Hi, I'd like to know if someone did a work on information theory algorithm ? I saw a package in Moose about information theory but it is just a kind of document indexation. Is there something more complete (quantities information)? Thanks, -------------- Brice Govin PhD student in RMoD research team at INRIA Lille Software Engineer at THALES AIR SYSTEMS Rungis ENSTA-Bretagne ENSI2014 22 Avenue du General Leclerc 92340 BOURG-LA-REINE

June 15, 2016

Deadline today for ESUG2016 call for talk proposals

by Peter UhnÃ¡k

Hi, today is deadline for submitting tutorial/talk/teaching pearl proposals for ESUG2016. As far as I can tell this was never announced on the Pharo mailing list (only several IWST16 CFP), so some people have missed it. http://www.esug.org/wiki/pier/Conferences/2016/Call-for-Presentations ------------ Call-for-Presentations24rd International Smalltalk Joint Conference - Call for Contributions - Prague, Czech Republic - from 22 to 26 August 2016 - http://www.esug.org/Conferences/2016/ You can support the ESUG conference in many different ways: - Sponsor the conference. New sponsoring packages are described at http://www.esug.org/wiki/pier/About/BecomeSponsor - Submit a talk, a software or a paper to one of the events. See below. - Attend the conference. We'd like to beat the previous record of attendance (170 people at Amsterdam 2008)! - Students can get free registration and hosting if they enrol into the the Student Volunteers program. See below. Developers Forum: International Smalltalk Developers Conference We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45-60 min for hands-on tutorials. The list of topics for the normal talks and tutorials includes, but is not limited to the following: - Micro Services, Container, Cloud, Big Data, - XP practices, Development tools, Experience reports - Model driven development, Web development, Team management - Meta-Modeling, Security, New libraries & frameworks - Educational material, Embedded systems and robotics - SOA and Web services, Interaction with other programming languages Teaching Pearls and Show us Your Business - Show your business 10 min session (Get prepared!!) - Teaching pearls : we want some session on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. We expect to have several 10 to 15 min sessions aggregated. How to submit? - Submissions deadline is 15 of June 2016 - Notification of acceptance will be on done on the fly. - More information at http://www.esug.org/conferences/2016 Pay attention: the places are limited so do not wait till the last minute to apply. Prospective presenters should submit a request to Stephane.Ducasse at inria.fr AND USE THE following header [ESUG 2016 Developers]. Please follow the template below the email will be automatically processed! Subject: [ESUG 2016 Developers] + your name First Name: Last Name: Email where you can always be reached: Title: Type: Tutorial/Talk/Teaching Pearl Abstract: Bio: Any presentation not respecting this form will be discarded automatically. International Workshop on Smalltalk Technologies Read the page: http://www.esug.org/wiki/pier/Conferences/2016/International-Workshop-IWST_… Technology Award Competition The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros during an awards ceremony at the conference. Developers of any Smalltalk-based software are welcome to compete. More information at http://www.esug.org/wiki/pier/Conferences/2016/Innovation-Technology-Awards Student Volunteer Program If you are a student wanting to attend ESUG, have you considered being a student volunteer? Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. More information at http://www.esug.org/wiki/pier/Conferences/2016/Student-volunteers We hope to see you there and have fun together.

June 15, 2016

Re: [Pharo-users] Pharo 5 on FreeBSD - no luck

by Ben Coman

On Wed, Jun 15, 2016 at 5:59 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > On 15 Jun 2016, at 00:40, Petr Fischer <petr.fischer(a)me.com> wrote: > > Hello, trying to install Pharo on my FreeBSD (11-CURRENT 64bit) with no luck > :( > > Facts: > > 1) I can run Linux (even 64bit Linux ELF) binaries on FreeBSD > > interesting, I didnât know. > > 2) but I can't use precompiled Linux 32binaries from Pharo.org, because > there is no 32libs (32bit linux libs) support on 64bit FreeBSD Maybe for a few months until the Image is ready for 64-bit you could run Pharo on 32bit FreeBSD with 32bit linux libs ?? cheers -ben > > mmmâ¦ but you still need 32bits binaries to run Pharo. > > > 3) tried build from https://github.com/pharo-project/pharo-vm - no luck, > because newImage script downloads 5.0 image and Linux VM (!) for > intermediate VMMaker build (I can't build Pharo without working Pharo) > > > one possibility is to used the pre-generated sources: > http://files.pharo.org/vm/src/spur/ > > > 4) tried latest prebuild 64 bit Cog Spur Linux VM from > http://www.mirandabanda.org/cogblog/downloads/ (cogspur64linuxht) - no luck > - I don't know what the "squeak" start SH script is doing and it's intended > for Linux > > > this will not work because: > > 1) you are downloading a 64bits vm, then you need a 64bits image: > http://files.pharo.org/get-files/60/pharo-64.zip > 2) since is 64bits who is work in progress it will still have some important > problems (missing plugins, missing UFFI correct implementation, etc.) > 3) I also donât know what the âhtâ part meansâ¦ > > > Is actual build documentation for latest 64 bit > Cog-Spur-something-something-VM somewhere? > > Will be FFI (New-Native-something-something-FFI) working fine under FreeBSD > (another unix), or will be some low-level core C porting needed? > > > once UFFI it works in 64bits, there is no reason why it will not work on > FreeBSD > > > I can help with adapting build scrits also for FreeBSD - this OS is small, > fast, robust and secure (there is ZFS, Jails for isolation, everything is > simple etc etc) - perfect for running Pharo images on server side - I really > like this combo (BSD+Smalltalk). > > > is not a problem (for now) of scriptsâ¦ the problem is that you are trying to > build a 64bits environment and we are not yet there. Pharo is still 32bitsâ¦ > > now, Iâm working on this and it should be ready in a couple of months, but > for now you are more or less restricted to two options: > > 1) install 32bits dependences > 2) use the *very experimental* 64bits image along with Eliot 64bits spur, > who should be this one: > http://www.mirandabanda.org/files/Cog/VM/latest/cogspur64linux-16.21.3732.t… > > > Thanks, Petr Fischer > > > cheers! > Esteban >

June 15, 2016

Re: [Pharo-users] Pharo 5 on FreeBSD - no luck

by Esteban Lorenzano

Hi, > On 15 Jun 2016, at 00:40, Petr Fischer <petr.fischer(a)me.com> wrote: > > Hello, trying to install Pharo on my FreeBSD (11-CURRENT 64bit) with no luck :( > > Facts: > > 1) I can run Linux (even 64bit Linux ELF) binaries on FreeBSD interesting, I didnât know. > > 2) but I can't use precompiled Linux 32binaries from Pharo.org, because there is no 32libs (32bit linux libs) support on 64bit FreeBSD mmmâ¦ but you still need 32bits binaries to run Pharo. > > 3) tried build from https://github.com/pharo-project/pharo-vm - no luck, because newImage script downloads 5.0 image and Linux VM (!) for intermediate VMMaker build (I can't build Pharo without working Pharo) one possibility is to used the pre-generated sources: http://files.pharo.org/vm/src/spur/ <http://files.pharo.org/vm/src/spur/> > > 4) tried latest prebuild 64 bit Cog Spur Linux VM from http://www.mirandabanda.org/cogblog/downloads/ (cogspur64linuxht) - no luck - I don't know what the "squeak" start SH script is doing and it's intended for Linux this will not work because: 1) you are downloading a 64bits vm, then you need a 64bits image: http://files.pharo.org/get-files/60/pharo-64.zip <http://files.pharo.org/get-files/60/pharo-64.zip> 2) since is 64bits who is work in progress it will still have some important problems (missing plugins, missing UFFI correct implementation, etc.) 3) I also donât know what the âhtâ part meansâ¦ > > Is actual build documentation for latest 64 bit Cog-Spur-something-something-VM somewhere? > Will be FFI (New-Native-something-something-FFI) working fine under FreeBSD (another unix), or will be some low-level core C porting needed? once UFFI it works in 64bits, there is no reason why it will not work on FreeBSD > > I can help with adapting build scrits also for FreeBSD - this OS is small, fast, robust and secure (there is ZFS, Jails for isolation, everything is simple etc etc) - perfect for running Pharo images on server side - I really like this combo (BSD+Smalltalk). > is not a problem (for now) of scriptsâ¦ the problem is that you are trying to build a 64bits environment and we are not yet there. Pharo is still 32bitsâ¦ now, Iâm working on this and it should be ready in a couple of months, but for now you are more or less restricted to two options: 1) install 32bits dependences 2) use the *very experimental* 64bits image along with Eliot 64bits spur, who should be this one: http://www.mirandabanda.org/files/Cog/VM/latest/cogspur64linux-16.21.3732.t… <http://www.mirandabanda.org/files/Cog/VM/latest/cogspur64linux-16.21.3732.t…> > Thanks, Petr Fischer > cheers! Esteban

June 15, 2016

Re: [Pharo-users] Dependency error trying to submit a proposed enhancement to Pharo 5.0 on Smalltalkhub.com

by Mark Bratcher

I just tried it on my Ubuntu workstation and it appeared to save everything like it should. So it seems specific to the Windows version. On 6/14/2016 11:37 PM, Bernardo Ezequiel Contreras wrote: > im on debian with > Pharo5.0 > Latest update: #50760 > > i just add a whitespace in the class comment of the class RxParser and > then follow your steps, saving the slice locally in a directory. > > > > On Wed, Jun 15, 2016 at 12:08 AM, Mark Bratcher <mdbratch(a)gmail.com > <mailto:mdbratch@gmail.com>> wrote: > > Thanks for trying it. Are you on Windows and Pharo 5.0? > > Can you tell me what item you changed? I'd be curious just to try > the same thing. > > > On 6/14/2016 11:04 PM, Bernardo Ezequiel Contreras wrote: >> i tried your steps locally in a directory with a fake change and >> i couldnt reproduce the bug, i got the slice and the dependent >> package(with the fake change). >> please report it, someone with more knowledge should check it. >> >> >> >> On Tue, Jun 14, 2016 at 11:54 PM, Mark Bratcher >> <mdbratch(a)gmail.com <mailto:mdbratch@gmail.com>> wrote: >> >> Just saving the slice to the repository (as the instructions >> indicate) does not save the code also, and Monticello marks >> the slice and associated packages all clean when just saving >> the slice. So I'm thinking bug...? >> >> >> On 6/14/2016 10:38 PM, Bernardo Ezequiel Contreras wrote: >>> the slice has no code, it just a reference to the >>> dependencies (the dirty packages), those dirty packages >>> should be save in the repository(files ended with mcz in >>> your directory) >>> if you don't have those files in the local >>> repository(directory), theres a bug. >>> >>> On Tue, Jun 14, 2016 at 11:33 PM, Mark Bratcher >>> <mdbratch(a)gmail.com <mailto:mdbratch@gmail.com>> wrote: >>> >>> I opened the MCZ file saved for the slice package and it >>> has no code changes in it. It just has the dependency >>> information. So it does seem that more has to be saved >>> to the repository than just the SLICE. Or, the SLICE >>> operation isn't "capturing" the code properly as part of >>> the package. In one of my attempts, I did try saving >>> both the SLICE and the package independently, but that >>> didn't get rid of the error. >>> >>> >>> On 6/14/2016 10:23 PM, Bernardo Ezequiel Contreras wrote: >>>> there's something fishy going on. (the dependency >>>> wasn't save to the inbox). >>>> in the other hand, the contribution steps could be improved >>>> >>>> >>>> >>>> On Tue, Jun 14, 2016 at 11:03 PM, Mark Bratcher >>>> <mdbratch(a)gmail.com <mailto:mdbratch@gmail.com>> wrote: >>>> >>>> Bernardo >>>> >>>> Thank you. That's a good idea. I'll try that. I was >>>> surprised that it didn't go to the inbox as I >>>> thought I set up the repository path properly. >>>> >>>> Mark >>>> >>>> Sent from TypeApp <http://www.typeapp.com/r> >>>> >>>> On Jun 14, 2016, at 10:00 PM, Bernardo Ezequiel >>>> Contreras <vonbecmann(a)gmail.com >>>> <mailto:vonbecmann@gmail.com>> wrote: >>>> >>>> i forgot to mention that i used to save my >>>> slices locally in a directory, and test the >>>> slice with a new image and see if the merge of >>>> the slice has no conflicts, to be sure that the >>>> monkey will work without problems. >>>> and then i copy the slice to the inbox >>>> >>>> >>>> On Tue, Jun 14, 2016 at 10:53 PM, Bernardo >>>> Ezequiel Contreras <vonbecmann(a)gmail.com >>>> <mailto:vonbecmann@gmail.com>> wrote: >>>> >>>> Hi mark, >>>> it seems that your >>>> package: Regex-Core-MarkBratcher.39.mcz is >>>> not the inbox. >>>> if you have the package, then you can >>>> Copy(button in the monticello browser) it >>>> to the inbox, and try again. >>>> >>>> >>>> >>>> On Tue, Jun 14, 2016 at 9:53 PM, Mark >>>> Bratcher <mdbratch(a)gmail.com >>>> <mailto:mdbratch@gmail.com>> wrote: >>>> >>>> I am trying to push a simple >>>> enhancement to Pharo50inbox on >>>> smalltalkhub.com >>>> <http://smalltalkhub.com>. I am running >>>> Pharo 5.0 (downloaded within the last >>>> month) on Windows 10. >>>> >>>> I started from a completely clean >>>> image, made my small change (about 5 >>>> lines in an existing Pharo 5.0 class), >>>> and I followed all of the directions to >>>> contribute a proposed fix >>>> <http://pharo.org/contribute-propose-fix> >>>> very carefully. All the steps went >>>> smoothly, as expected, until it came >>>> time to pull and verify the slice. >>>> >>>> Here is a snapshot of my Monticello >>>> browser right BEFORE pushing >>>> <http://i.stack.imgur.com/Zv2bZ.jpg> >>>> the suggested change slice. What is >>>> listed as dirty are the SLICE itself >>>> (containing Regex-Core >>>> (TheIntegrator.38)) and the package >>>> itself, listed separately, as dirty >>>> (Regex-Core (TheIntegrator.38)). >>>> >>>> As indicated in the instructions, I >>>> highlighted the SLICE and did a Save to >>>> the >>>> `http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main` >>>> repository. That went smoothly. After >>>> clicking save, Monticello showed >>>> <http://i.stack.imgur.com/BYfVf.jpg> >>>> that the SLICE (with subpackage) and >>>> the separately listed package were no >>>> longer marked dirty and version had >>>> been bumped with my name associated >>>> (both now called, "Regex-Core >>>> (MarkBratcher.39)"). >>>> >>>> The dialog that popped up after the >>>> save indicated that there is a >>>> dependency on `Regex-Core >>>> (MarkBratcher.39)` which surprised me a >>>> bit, but since I followed the >>>> instructions exactly, I wasn't >>>> concerned yet... >>>> >>>> When I tried to verify, I started with >>>> a clean image again (as recommended in >>>> the instructions, opened Monticello, >>>> opened the Pharo50Inbox repository, >>>> found and highlighted my slice, and >>>> clicked "Load". Then I got an error >>>> that there was a missing dependency on >>>> the package: `Regex-Core >>>> (MarkBratcher.39)`. I thought that >>>> package was integrated as part of the >>>> SLICE. >>>> >>>> If I followed the linked instructions >>>> precisely, what am I missing? >>>> >>>> >>>> >>>> >>>> -- >>>> Bernardo E.C. >>>> >>>> Sent from a cheap desktop computer in South >>>> America. >>>> >>>> >>>> >>>> >>>> -- >>>> Bernardo E.C. >>>> >>>> Sent from a cheap desktop computer in South >>>> America. >>>> >>>> >>>> >>>> >>>> -- >>>> Bernardo E.C. >>>> >>>> Sent from a cheap desktop computer in South America. >>> >>> >>> >>> >>> -- >>> Bernardo E.C. >>> >>> Sent from a cheap desktop computer in South America. >> >> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. > > > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America.

June 15, 2016

Re: [Pharo-users] Dependency error trying to submit a proposed enhancement to Pharo 5.0 on Smalltalkhub.com

by Bernardo Ezequiel Contreras

im on debian with Pharo5.0 Latest update: #50760 i just add a whitespace in the class comment of the class RxParser and then follow your steps, saving the slice locally in a directory. On Wed, Jun 15, 2016 at 12:08 AM, Mark Bratcher <mdbratch(a)gmail.com> wrote: > Thanks for trying it. Are you on Windows and Pharo 5.0? > > Can you tell me what item you changed? I'd be curious just to try the same > thing. > > On 6/14/2016 11:04 PM, Bernardo Ezequiel Contreras wrote: > > i tried your steps locally in a directory with a fake change and i couldnt > reproduce the bug, i got the slice and the dependent package(with the fake > change). > please report it, someone with more knowledge should check it. > > > > On Tue, Jun 14, 2016 at 11:54 PM, Mark Bratcher <mdbratch(a)gmail.com> > wrote: > >> Just saving the slice to the repository (as the instructions indicate) >> does not save the code also, and Monticello marks the slice and associated >> packages all clean when just saving the slice. So I'm thinking bug...? >> >> On 6/14/2016 10:38 PM, Bernardo Ezequiel Contreras wrote: >> >> the slice has no code, it just a reference to the dependencies (the dirty >> packages), those dirty packages should be save in the repository(files >> ended with mcz in your directory) >> if you don't have those files in the local repository(directory), theres >> a bug. >> >> On Tue, Jun 14, 2016 at 11:33 PM, Mark Bratcher < <mdbratch(a)gmail.com> >> mdbratch(a)gmail.com> wrote: >> >>> I opened the MCZ file saved for the slice package and it has no code >>> changes in it. It just has the dependency information. So it does seem that >>> more has to be saved to the repository than just the SLICE. Or, the SLICE >>> operation isn't "capturing" the code properly as part of the package. In >>> one of my attempts, I did try saving both the SLICE and the package >>> independently, but that didn't get rid of the error. >>> >>> >>> On 6/14/2016 10:23 PM, Bernardo Ezequiel Contreras wrote: >>> >>> there's something fishy going on. (the dependency wasn't save to the >>> inbox). >>> in the other hand, the contribution steps could be improved >>> >>> >>> >>> On Tue, Jun 14, 2016 at 11:03 PM, Mark Bratcher < <mdbratch(a)gmail.com> >>> mdbratch(a)gmail.com> wrote: >>> >>>> Bernardo >>>> >>>> Thank you. That's a good idea. I'll try that. I was surprised that it >>>> didn't go to the inbox as I thought I set up the repository path properly. >>>> >>>> Mark >>>> >>>> Sent from TypeApp <http://www.typeapp.com/r> >>>> >>>> On Jun 14, 2016, at 10:00 PM, Bernardo Ezequiel Contreras < >>>> <vonbecmann(a)gmail.com>vonbecmann(a)gmail.com> wrote: >>>>> >>>>> i forgot to mention that i used to save my slices locally in a >>>>> directory, and test the slice with a new image and see if the merge of the >>>>> slice has no conflicts, to be sure that the monkey will work without >>>>> problems. >>>>> and then i copy the slice to the inbox >>>>> >>>>> >>>>> On Tue, Jun 14, 2016 at 10:53 PM, Bernardo Ezequiel Contreras < >>>>> <vonbecmann(a)gmail.com>vonbecmann(a)gmail.com> wrote: >>>>> >>>>>> Hi mark, >>>>>> it seems that your package: Regex-Core-MarkBratcher.39.mcz is not >>>>>> the inbox. >>>>>> if you have the package, then you can Copy(button in the monticello >>>>>> browser) it to the inbox, and try again. >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Jun 14, 2016 at 9:53 PM, Mark Bratcher < <mdbratch(a)gmail.com> >>>>>> mdbratch(a)gmail.com> wrote: >>>>>> >>>>>>> I am trying to push a simple enhancement to Pharo50inbox on >>>>>>> smalltalkhub.com. I am running Pharo 5.0 (downloaded within the >>>>>>> last month) on Windows 10. >>>>>>> >>>>>>> I started from a completely clean image, made my small change (about >>>>>>> 5 lines in an existing Pharo 5.0 class), and I followed all of the >>>>>>> directions to contribute a proposed fix >>>>>>> <http://pharo.org/contribute-propose-fix> very carefully. All the >>>>>>> steps went smoothly, as expected, until it came time to pull and verify the >>>>>>> slice. >>>>>>> >>>>>>> Here is a snapshot of my Monticello browser right BEFORE pushing >>>>>>> <http://i.stack.imgur.com/Zv2bZ.jpg> the suggested change slice. >>>>>>> What is listed as dirty are the SLICE itself (containing Regex-Core >>>>>>> (TheIntegrator.38)) and the package itself, listed separately, as dirty >>>>>>> (Regex-Core (TheIntegrator.38)). >>>>>>> >>>>>>> As indicated in the instructions, I highlighted the SLICE and did a >>>>>>> Save to the ` <http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main> >>>>>>> http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main` repository. >>>>>>> That went smoothly. After clicking save, Monticello showed >>>>>>> <http://i.stack.imgur.com/BYfVf.jpg> that the SLICE (with >>>>>>> subpackage) and the separately listed package were no longer marked dirty >>>>>>> and version had been bumped with my name associated (both now called, >>>>>>> "Regex-Core (MarkBratcher.39)"). >>>>>>> >>>>>>> The dialog that popped up after the save indicated that there is a >>>>>>> dependency on `Regex-Core (MarkBratcher.39)` which surprised me a bit, but >>>>>>> since I followed the instructions exactly, I wasn't concerned yet... >>>>>>> >>>>>>> When I tried to verify, I started with a clean image again (as >>>>>>> recommended in the instructions, opened Monticello, opened the Pharo50Inbox >>>>>>> repository, found and highlighted my slice, and clicked "Load". Then I got >>>>>>> an error that there was a missing dependency on the package: `Regex-Core >>>>>>> (MarkBratcher.39)`. I thought that package was integrated as part of the >>>>>>> SLICE. >>>>>>> >>>>>>> If I followed the linked instructions precisely, what am I missing? >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Bernardo E.C. >>>>>> >>>>>> Sent from a cheap desktop computer in South America. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Bernardo E.C. >>>>> >>>>> Sent from a cheap desktop computer in South America. >>>>> >>>> >>> >>> >>> -- >>> Bernardo E.C. >>> >>> Sent from a cheap desktop computer in South America. >>> >>> >>> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. >> >> >> > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America. > > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

June 15, 2016

Re: [Pharo-users] Dependency error trying to submit a proposed enhancement to Pharo 5.0 on Smalltalkhub.com

by Mark Bratcher

Thanks for trying it. Are you on Windows and Pharo 5.0? Can you tell me what item you changed? I'd be curious just to try the same thing. On 6/14/2016 11:04 PM, Bernardo Ezequiel Contreras wrote: > i tried your steps locally in a directory with a fake change and i > couldnt reproduce the bug, i got the slice and the dependent > package(with the fake change). > please report it, someone with more knowledge should check it. > > > > On Tue, Jun 14, 2016 at 11:54 PM, Mark Bratcher <mdbratch(a)gmail.com > <mailto:mdbratch@gmail.com>> wrote: > > Just saving the slice to the repository (as the instructions > indicate) does not save the code also, and Monticello marks the > slice and associated packages all clean when just saving the > slice. So I'm thinking bug...? > > > On 6/14/2016 10:38 PM, Bernardo Ezequiel Contreras wrote: >> the slice has no code, it just a reference to the dependencies >> (the dirty packages), those dirty packages should be save in the >> repository(files ended with mcz in your directory) >> if you don't have those files in the local repository(directory), >> theres a bug. >> >> On Tue, Jun 14, 2016 at 11:33 PM, Mark Bratcher >> <mdbratch(a)gmail.com <mailto:mdbratch@gmail.com>> wrote: >> >> I opened the MCZ file saved for the slice package and it has >> no code changes in it. It just has the dependency >> information. So it does seem that more has to be saved to the >> repository than just the SLICE. Or, the SLICE operation isn't >> "capturing" the code properly as part of the package. In one >> of my attempts, I did try saving both the SLICE and the >> package independently, but that didn't get rid of the error. >> >> >> On 6/14/2016 10:23 PM, Bernardo Ezequiel Contreras wrote: >>> there's something fishy going on. (the dependency wasn't >>> save to the inbox). >>> in the other hand, the contribution steps could be improved >>> >>> >>> >>> On Tue, Jun 14, 2016 at 11:03 PM, Mark Bratcher >>> <mdbratch(a)gmail.com <mailto:mdbratch@gmail.com>> wrote: >>> >>> Bernardo >>> >>> Thank you. That's a good idea. I'll try that. I was >>> surprised that it didn't go to the inbox as I thought I >>> set up the repository path properly. >>> >>> Mark >>> >>> Sent from TypeApp <http://www.typeapp.com/r> >>> >>> On Jun 14, 2016, at 10:00 PM, Bernardo Ezequiel >>> Contreras <vonbecmann(a)gmail.com >>> <mailto:vonbecmann@gmail.com>> wrote: >>> >>> i forgot to mention that i used to save my slices >>> locally in a directory, and test the slice with a >>> new image and see if the merge of the slice has no >>> conflicts, to be sure that the monkey will work >>> without problems. >>> and then i copy the slice to the inbox >>> >>> >>> On Tue, Jun 14, 2016 at 10:53 PM, Bernardo Ezequiel >>> Contreras <vonbecmann(a)gmail.com >>> <mailto:vonbecmann@gmail.com>> wrote: >>> >>> Hi mark, >>> it seems that your >>> package: Regex-Core-MarkBratcher.39.mcz is not >>> the inbox. >>> if you have the package, then you can >>> Copy(button in the monticello browser) it to the >>> inbox, and try again. >>> >>> >>> >>> On Tue, Jun 14, 2016 at 9:53 PM, Mark Bratcher >>> <mdbratch(a)gmail.com <mailto:mdbratch@gmail.com>> >>> wrote: >>> >>> I am trying to push a simple enhancement to >>> Pharo50inbox on smalltalkhub.com >>> <http://smalltalkhub.com>. I am running >>> Pharo 5.0 (downloaded within the last month) >>> on Windows 10. >>> >>> I started from a completely clean image, >>> made my small change (about 5 lines in an >>> existing Pharo 5.0 class), and I followed >>> all of the directions to contribute a >>> proposed fix >>> <http://pharo.org/contribute-propose-fix> >>> very carefully. All the steps went smoothly, >>> as expected, until it came time to pull and >>> verify the slice. >>> >>> Here is a snapshot of my Monticello browser >>> right BEFORE pushing >>> <http://i.stack.imgur.com/Zv2bZ.jpg> the >>> suggested change slice. What is listed as >>> dirty are the SLICE itself (containing >>> Regex-Core (TheIntegrator.38)) and the >>> package itself, listed separately, as dirty >>> (Regex-Core (TheIntegrator.38)). >>> >>> As indicated in the instructions, I >>> highlighted the SLICE and did a Save to the >>> `http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main` >>> repository. That went smoothly. After >>> clicking save, Monticello showed >>> <http://i.stack.imgur.com/BYfVf.jpg> that >>> the SLICE (with subpackage) and the >>> separately listed package were no longer >>> marked dirty and version had been bumped >>> with my name associated (both now called, >>> "Regex-Core (MarkBratcher.39)"). >>> >>> The dialog that popped up after the save >>> indicated that there is a dependency on >>> `Regex-Core (MarkBratcher.39)` which >>> surprised me a bit, but since I followed the >>> instructions exactly, I wasn't concerned yet... >>> >>> When I tried to verify, I started with a >>> clean image again (as recommended in the >>> instructions, opened Monticello, opened the >>> Pharo50Inbox repository, found and >>> highlighted my slice, and clicked "Load". >>> Then I got an error that there was a missing >>> dependency on the package: `Regex-Core >>> (MarkBratcher.39)`. I thought that package >>> was integrated as part of the SLICE. >>> >>> If I followed the linked instructions >>> precisely, what am I missing? >>> >>> >>> >>> >>> -- >>> Bernardo E.C. >>> >>> Sent from a cheap desktop computer in South >>> America. >>> >>> >>> >>> >>> -- >>> Bernardo E.C. >>> >>> Sent from a cheap desktop computer in South America. >>> >>> >>> >>> >>> -- >>> Bernardo E.C. >>> >>> Sent from a cheap desktop computer in South America. >> >> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. > > > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America.

June 15, 2016

Re: [Pharo-users] Dependency error trying to submit a proposed enhancement to Pharo 5.0 on Smalltalkhub.com

by Bernardo Ezequiel Contreras

i tried your steps locally in a directory with a fake change and i couldnt reproduce the bug, i got the slice and the dependent package(with the fake change). please report it, someone with more knowledge should check it. On Tue, Jun 14, 2016 at 11:54 PM, Mark Bratcher <mdbratch(a)gmail.com> wrote: > Just saving the slice to the repository (as the instructions indicate) > does not save the code also, and Monticello marks the slice and associated > packages all clean when just saving the slice. So I'm thinking bug...? > > On 6/14/2016 10:38 PM, Bernardo Ezequiel Contreras wrote: > > the slice has no code, it just a reference to the dependencies (the dirty > packages), those dirty packages should be save in the repository(files > ended with mcz in your directory) > if you don't have those files in the local repository(directory), theres a > bug. > > On Tue, Jun 14, 2016 at 11:33 PM, Mark Bratcher <mdbratch(a)gmail.com> > wrote: > >> I opened the MCZ file saved for the slice package and it has no code >> changes in it. It just has the dependency information. So it does seem that >> more has to be saved to the repository than just the SLICE. Or, the SLICE >> operation isn't "capturing" the code properly as part of the package. In >> one of my attempts, I did try saving both the SLICE and the package >> independently, but that didn't get rid of the error. >> >> >> On 6/14/2016 10:23 PM, Bernardo Ezequiel Contreras wrote: >> >> there's something fishy going on. (the dependency wasn't save to the >> inbox). >> in the other hand, the contribution steps could be improved >> >> >> >> On Tue, Jun 14, 2016 at 11:03 PM, Mark Bratcher < <mdbratch(a)gmail.com> >> mdbratch(a)gmail.com> wrote: >> >>> Bernardo >>> >>> Thank you. That's a good idea. I'll try that. I was surprised that it >>> didn't go to the inbox as I thought I set up the repository path properly. >>> >>> Mark >>> >>> Sent from TypeApp <http://www.typeapp.com/r> >>> >>> On Jun 14, 2016, at 10:00 PM, Bernardo Ezequiel Contreras < >>> <vonbecmann(a)gmail.com>vonbecmann(a)gmail.com> wrote: >>>> >>>> i forgot to mention that i used to save my slices locally in a >>>> directory, and test the slice with a new image and see if the merge of the >>>> slice has no conflicts, to be sure that the monkey will work without >>>> problems. >>>> and then i copy the slice to the inbox >>>> >>>> >>>> On Tue, Jun 14, 2016 at 10:53 PM, Bernardo Ezequiel Contreras < >>>> <vonbecmann(a)gmail.com>vonbecmann(a)gmail.com> wrote: >>>> >>>>> Hi mark, >>>>> it seems that your package: Regex-Core-MarkBratcher.39.mcz is not the >>>>> inbox. >>>>> if you have the package, then you can Copy(button in the monticello >>>>> browser) it to the inbox, and try again. >>>>> >>>>> >>>>> >>>>> On Tue, Jun 14, 2016 at 9:53 PM, Mark Bratcher < <mdbratch(a)gmail.com> >>>>> mdbratch(a)gmail.com> wrote: >>>>> >>>>>> I am trying to push a simple enhancement to Pharo50inbox on >>>>>> smalltalkhub.com. I am running Pharo 5.0 (downloaded within the last >>>>>> month) on Windows 10. >>>>>> >>>>>> I started from a completely clean image, made my small change (about >>>>>> 5 lines in an existing Pharo 5.0 class), and I followed all of the >>>>>> directions to contribute a proposed fix >>>>>> <http://pharo.org/contribute-propose-fix> very carefully. All the >>>>>> steps went smoothly, as expected, until it came time to pull and verify the >>>>>> slice. >>>>>> >>>>>> Here is a snapshot of my Monticello browser right BEFORE pushing >>>>>> <http://i.stack.imgur.com/Zv2bZ.jpg> the suggested change slice. >>>>>> What is listed as dirty are the SLICE itself (containing Regex-Core >>>>>> (TheIntegrator.38)) and the package itself, listed separately, as dirty >>>>>> (Regex-Core (TheIntegrator.38)). >>>>>> >>>>>> As indicated in the instructions, I highlighted the SLICE and did a >>>>>> Save to the ` <http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main> >>>>>> http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main` repository. That >>>>>> went smoothly. After clicking save, Monticello showed >>>>>> <http://i.stack.imgur.com/BYfVf.jpg> that the SLICE (with >>>>>> subpackage) and the separately listed package were no longer marked dirty >>>>>> and version had been bumped with my name associated (both now called, >>>>>> "Regex-Core (MarkBratcher.39)"). >>>>>> >>>>>> The dialog that popped up after the save indicated that there is a >>>>>> dependency on `Regex-Core (MarkBratcher.39)` which surprised me a bit, but >>>>>> since I followed the instructions exactly, I wasn't concerned yet... >>>>>> >>>>>> When I tried to verify, I started with a clean image again (as >>>>>> recommended in the instructions, opened Monticello, opened the Pharo50Inbox >>>>>> repository, found and highlighted my slice, and clicked "Load". Then I got >>>>>> an error that there was a missing dependency on the package: `Regex-Core >>>>>> (MarkBratcher.39)`. I thought that package was integrated as part of the >>>>>> SLICE. >>>>>> >>>>>> If I followed the linked instructions precisely, what am I missing? >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Bernardo E.C. >>>>> >>>>> Sent from a cheap desktop computer in South America. >>>>> >>>> >>>> >>>> >>>> -- >>>> Bernardo E.C. >>>> >>>> Sent from a cheap desktop computer in South America. >>>> >>> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. >> >> >> > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America. > > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

June 15, 2016

Re: [Pharo-users] Dependency error trying to submit a proposed enhancement to Pharo 5.0 on Smalltalkhub.com

by Mark Bratcher

Just saving the slice to the repository (as the instructions indicate) does not save the code also, and Monticello marks the slice and associated packages all clean when just saving the slice. So I'm thinking bug...? On 6/14/2016 10:38 PM, Bernardo Ezequiel Contreras wrote: > the slice has no code, it just a reference to the dependencies (the > dirty packages), those dirty packages should be save in the > repository(files ended with mcz in your directory) > if you don't have those files in the local repository(directory), > theres a bug. > > On Tue, Jun 14, 2016 at 11:33 PM, Mark Bratcher <mdbratch(a)gmail.com > <mailto:mdbratch@gmail.com>> wrote: > > I opened the MCZ file saved for the slice package and it has no > code changes in it. It just has the dependency information. So it > does seem that more has to be saved to the repository than just > the SLICE. Or, the SLICE operation isn't "capturing" the code > properly as part of the package. In one of my attempts, I did try > saving both the SLICE and the package independently, but that > didn't get rid of the error. > > > On 6/14/2016 10:23 PM, Bernardo Ezequiel Contreras wrote: >> there's something fishy going on. (the dependency wasn't save to >> the inbox). >> in the other hand, the contribution steps could be improved >> >> >> >> On Tue, Jun 14, 2016 at 11:03 PM, Mark Bratcher >> <mdbratch(a)gmail.com <mailto:mdbratch@gmail.com>> wrote: >> >> Bernardo >> >> Thank you. That's a good idea. I'll try that. I was surprised >> that it didn't go to the inbox as I thought I set up the >> repository path properly. >> >> Mark >> >> Sent from TypeApp <http://www.typeapp.com/r> >> >> On Jun 14, 2016, at 10:00 PM, Bernardo Ezequiel Contreras >> <vonbecmann(a)gmail.com <mailto:vonbecmann@gmail.com>> wrote: >> >> i forgot to mention that i used to save my slices locally >> in a directory, and test the slice with a new image and >> see if the merge of the slice has no conflicts, to be >> sure that the monkey will work without problems. >> and then i copy the slice to the inbox >> >> >> On Tue, Jun 14, 2016 at 10:53 PM, Bernardo Ezequiel >> Contreras <vonbecmann(a)gmail.com >> <mailto:vonbecmann@gmail.com>> wrote: >> >> Hi mark, >> it seems that your >> package: Regex-Core-MarkBratcher.39.mcz is not the >> inbox. >> if you have the package, then you can Copy(button in >> the monticello browser) it to the inbox, and try again. >> >> >> >> On Tue, Jun 14, 2016 at 9:53 PM, Mark Bratcher >> <mdbratch(a)gmail.com <mailto:mdbratch@gmail.com>> wrote: >> >> I am trying to push a simple enhancement to >> Pharo50inbox on smalltalkhub.com >> <http://smalltalkhub.com>. I am running Pharo 5.0 >> (downloaded within the last month) on Windows 10. >> >> I started from a completely clean image, made my >> small change (about 5 lines in an existing Pharo >> 5.0 class), and I followed all of the directions >> to contribute a proposed fix >> <http://pharo.org/contribute-propose-fix> very >> carefully. All the steps went smoothly, as >> expected, until it came time to pull and verify >> the slice. >> >> Here is a snapshot of my Monticello browser right >> BEFORE pushing >> <http://i.stack.imgur.com/Zv2bZ.jpg> the >> suggested change slice. What is listed as dirty >> are the SLICE itself (containing Regex-Core >> (TheIntegrator.38)) and the package itself, >> listed separately, as dirty (Regex-Core >> (TheIntegrator.38)). >> >> As indicated in the instructions, I highlighted >> the SLICE and did a Save to the >> `http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main` >> repository. That went smoothly. After clicking >> save, Monticello showed >> <http://i.stack.imgur.com/BYfVf.jpg> that the >> SLICE (with subpackage) and the separately listed >> package were no longer marked dirty and version >> had been bumped with my name associated (both now >> called, "Regex-Core (MarkBratcher.39)"). >> >> The dialog that popped up after the save >> indicated that there is a dependency on >> `Regex-Core (MarkBratcher.39)` which surprised me >> a bit, but since I followed the instructions >> exactly, I wasn't concerned yet... >> >> When I tried to verify, I started with a clean >> image again (as recommended in the instructions, >> opened Monticello, opened the Pharo50Inbox >> repository, found and highlighted my slice, and >> clicked "Load". Then I got an error that there >> was a missing dependency on the package: >> `Regex-Core (MarkBratcher.39)`. I thought that >> package was integrated as part of the SLICE. >> >> If I followed the linked instructions precisely, >> what am I missing? >> >> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. >> >> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. >> >> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. > > > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America.

June 15, 2016

Re: [Pharo-users] Dependency error trying to submit a proposed enhancement to Pharo 5.0 on Smalltalkhub.com

by Bernardo Ezequiel Contreras

the slice has no code, it just a reference to the dependencies (the dirty packages), those dirty packages should be save in the repository(files ended with mcz in your directory) if you don't have those files in the local repository(directory), theres a bug. On Tue, Jun 14, 2016 at 11:33 PM, Mark Bratcher <mdbratch(a)gmail.com> wrote: > I opened the MCZ file saved for the slice package and it has no code > changes in it. It just has the dependency information. So it does seem that > more has to be saved to the repository than just the SLICE. Or, the SLICE > operation isn't "capturing" the code properly as part of the package. In > one of my attempts, I did try saving both the SLICE and the package > independently, but that didn't get rid of the error. > > > On 6/14/2016 10:23 PM, Bernardo Ezequiel Contreras wrote: > > there's something fishy going on. (the dependency wasn't save to the > inbox). > in the other hand, the contribution steps could be improved > > > > On Tue, Jun 14, 2016 at 11:03 PM, Mark Bratcher <mdbratch(a)gmail.com> > wrote: > >> Bernardo >> >> Thank you. That's a good idea. I'll try that. I was surprised that it >> didn't go to the inbox as I thought I set up the repository path properly. >> >> Mark >> >> Sent from TypeApp <http://www.typeapp.com/r> >> >> On Jun 14, 2016, at 10:00 PM, Bernardo Ezequiel Contreras < >> <vonbecmann(a)gmail.com>vonbecmann(a)gmail.com> wrote: >>> >>> i forgot to mention that i used to save my slices locally in a >>> directory, and test the slice with a new image and see if the merge of the >>> slice has no conflicts, to be sure that the monkey will work without >>> problems. >>> and then i copy the slice to the inbox >>> >>> >>> On Tue, Jun 14, 2016 at 10:53 PM, Bernardo Ezequiel Contreras < >>> vonbecmann(a)gmail.com> wrote: >>> >>>> Hi mark, >>>> it seems that your package: Regex-Core-MarkBratcher.39.mcz is not the >>>> inbox. >>>> if you have the package, then you can Copy(button in the monticello >>>> browser) it to the inbox, and try again. >>>> >>>> >>>> >>>> On Tue, Jun 14, 2016 at 9:53 PM, Mark Bratcher < <mdbratch(a)gmail.com> >>>> mdbratch(a)gmail.com> wrote: >>>> >>>>> I am trying to push a simple enhancement to Pharo50inbox on >>>>> smalltalkhub.com. I am running Pharo 5.0 (downloaded within the last >>>>> month) on Windows 10. >>>>> >>>>> I started from a completely clean image, made my small change (about 5 >>>>> lines in an existing Pharo 5.0 class), and I followed all of the directions >>>>> to contribute a proposed fix <http://pharo.org/contribute-propose-fix> >>>>> very carefully. All the steps went smoothly, as expected, until it came >>>>> time to pull and verify the slice. >>>>> >>>>> Here is a snapshot of my Monticello browser right BEFORE pushing >>>>> <http://i.stack.imgur.com/Zv2bZ.jpg> the suggested change slice. What >>>>> is listed as dirty are the SLICE itself (containing Regex-Core >>>>> (TheIntegrator.38)) and the package itself, listed separately, as dirty >>>>> (Regex-Core (TheIntegrator.38)). >>>>> >>>>> As indicated in the instructions, I highlighted the SLICE and did a >>>>> Save to the ` <http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main> >>>>> http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main` repository. That >>>>> went smoothly. After clicking save, Monticello showed >>>>> <http://i.stack.imgur.com/BYfVf.jpg> that the SLICE (with subpackage) >>>>> and the separately listed package were no longer marked dirty and version >>>>> had been bumped with my name associated (both now called, "Regex-Core >>>>> (MarkBratcher.39)"). >>>>> >>>>> The dialog that popped up after the save indicated that there is a >>>>> dependency on `Regex-Core (MarkBratcher.39)` which surprised me a bit, but >>>>> since I followed the instructions exactly, I wasn't concerned yet... >>>>> >>>>> When I tried to verify, I started with a clean image again (as >>>>> recommended in the instructions, opened Monticello, opened the Pharo50Inbox >>>>> repository, found and highlighted my slice, and clicked "Load". Then I got >>>>> an error that there was a missing dependency on the package: `Regex-Core >>>>> (MarkBratcher.39)`. I thought that package was integrated as part of the >>>>> SLICE. >>>>> >>>>> If I followed the linked instructions precisely, what am I missing? >>>>> >>>>> >>>> >>>> >>>> -- >>>> Bernardo E.C. >>>> >>>> Sent from a cheap desktop computer in South America. >>>> >>> >>> >>> >>> -- >>> Bernardo E.C. >>> >>> Sent from a cheap desktop computer in South America. >>> >> > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America. > > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

June 15, 2016