- Pharo-users - lists.pharo.org

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

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

by Mark Bratcher

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.

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 have the same error, even if I save the slice to a local repository. So my steps are: 1) Open a clean Pharo 5.0 image 2) Modify one class#selector in Regex-Core 3) "Accept" the change (it prompts me to enter my name, which I do as MarkBratcher) 4) Open Monticello, and see "*Regex-Core (TheIntegrator.38)" as the only dirty package 5) Click on Slice, select a fogbugz ID, and let it auto-fill 6) Click the checkbox next to "*Regex-Core (TheIntegrator.38)" (the only dirty package listed) 7) Click OK for the Slice dialog 8) Now "*Regex-Core (TheIntegrator.38)" AND "*SLICE-..." (with Regex-Core (TheIntegrator.38) appearing as part of that package) both appear in the left pane of Monticello 9) Select the SLICE package on the left Monticello pane, select the repository on the right pane 10) Save the SLICE package to the repository (click Save). Both the SLICE and Regex-Core versions bump (Regex-Core (TheIntegrator.38) becomes Regex-Core (MarkBratcher.39)) and are no longer dirty. A success dialog pops up with info about the repository save, including a comment that the SLICE has "Regex-Core (MarkBratcher.39)" as a dependency. 11) Exit Pharo 12) Reopen Pharo with a clean image 13) Open Monticello and open the repository that I saved the slice in 14) Click on the SLICE and click "Load" 15) I get the error that it cannot find the dependency on "Regex-Core (MarkBratcher.39)". I'm not sure why. On 6/14/2016 9:59 PM, Bernardo Ezequiel Contreras 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.

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

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> 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> >>> 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` >>>> 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.

June 15, 2016

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

by Mark Bratcher

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 On Jun 14, 2016, 10:00 PM, at 10:00 PM, Bernardo Ezequiel Contreras <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> >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` >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.

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 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> 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` 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.

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

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> 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` 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.

June 15, 2016

Dependency error trying to submit a proposed enhancement to Pharo 5.0 on Smalltalkhub.com

by Mark Bratcher

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` 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?

June 15, 2016

Re: [Pharo-users] Pharo 5 accented chars bug/regression

by Ben Coman

On Wed, Jun 15, 2016 at 1:27 AM, Milan Vavra via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Milan Vavra <vavra_milan(a)yahoo.com> > To: pharo-users(a)lists.pharo.org > Cc: > Date: Tue, 14 Jun 2016 09:47:21 -0700 (PDT) > Subject: Re: Pharo 5 accented chars bug/regression > Thank you all, > your feedback is appreciated. > > You have raised many points and so I probably won't be addressing > them all. But thanks again for all. I did read all the responses. > I will re-read them for more inspiration. > > I understand posting on this list is like going into a room with over > a 100 people and saying something. So if 100 people spend 10 minutes to > read this - that's a lot of minutes. > > So I don't want to waste your time. Feel free NOT to read this. But if > you do read this, there is an attempt at a joke towards the end. You > might even find it funny. Or not. > > I'm posting this through Nabble and it seems to post everything I post > twice. Once as 'Pharo Smalltalk Users mailing list' and as 'Milan Vavra' > too. I have no idea why. Enlighten me if you can. > > My original motivation was and is to be able to show to a potential > employer before and/or during the interview the sort problem fixing that > I can do. Even should the job have nothing to do with Smalltalk or Pharo > (then it might be an opportunity for a little Pharo/Smalltalk evangelism > but I digress). If there is an easy way to show that version X has a > problem - then I can show that I have the skills to fix that. If it is > fixed in the meantime I can just point to the fixed version Y and say: > "yeah, I fixed that". If there is some supporting evidence that should > give more credibility to my other claims that are unverifiable due to > the fact that they involved proprietary code that I just can not show > anyone. So their value in an interview is limited because it depends > on trust or a reference from someone else (trust again but vested in > the reference). But the Pharo fix should be an independently verifiable > claim. Of course there is a chance that I hired someone to fix that issue > for me and I don't have the skills. So a few follow up questions should > be in order to see whether or not I know what I am talking about. You wont get the best value from this bringing it up as a new topic in an interview. Interviews are a big cost for the employer and usually by the time you get there, they already think they want you. The interviewer already has an agenda basically verifying things they have already learnt about you. What you want to do is get it on the agenda pre-interview, to help you get through the front door to interview stage. The *very* best thing you can do is write a blog about your experiences, then link to it on your resume. The interviewer *will* review it and they "get to know you" - which really helps you stand out in their mind from all the other pieces of paper that float across their desk. Take a few articles to write about your journey discovering Pharo, intermediate experience, what makes it stand out from other environments and culminate in describing your feelings about making your first contribution and *why* you've chosen to do so. You might even get your post linked from Pharo Weekly. btw, after your contribution is integrated, submit your details to be added to pharo contributors http://pharo.org/about > On positive feedback. I think negative feedback is ok. Please > do give me negative feedback. I can take it. It can point me to > perceived problems I were not aware of. What I do want however is > ***constructive*** feedback. Actionable feedback. If you have a strong > opinion state it clearly but it should be of the kind: "To do [thing] > is stupid/ugly/whatever. We/you should do [something else] because > [explanation]." > > > I think Peter raised the issue: "is it fair that everyone gets mentioned > even though their contributions are not comparable". I am not ashamed > to say: "YES!". However it is not the same as saying that what I can > (potentially, you have not seen it yet) do is more valuable than what > others did in making Pharo happen in the first place. I had a minor role > in the movie. But I deserve a place in the credits. If there were no you > (all of you who have contributed so far) Pharo would not be what it is > today. A sexy development environment. If there were no me, someone else > would have to step up and do what I did. I am fully aware of that. Me > trying to contribute is a "thank you" of sorts to all of you. > > Small contribution with big impact. In a way it is not that small a > contribution considering the impact it can have on Pharo adoption. In > Smalltalk "a little code goes a long way". Consider this scenario, > a true story: I first downloaded my first Pharo back when 3.0 was > new. On Windows XP. I played with it a little. Got excited (sooooo > sexy!). But then came the blow. What? I can not type Ä? Is my keyboard > broken? Severed cable? No? Oh ok. It just won't let me. There goes my > contact management application. Bummer. It seems the IDE is not used by > anyone in the Czech Republic on Windows. Otherwise someone would have > noticed. Oh. Well. I don't have the skill to debug this yet. I am not > sure how to report this. Oh well let's wait until someone fixes this. And > it gave me the impression Pharo 3.0 is immature technology. This could > be happening in any country that uses Ä as part of their language > - Latvia, Lithuania, Serbia, Slovakia (Russia, Bulgaria, Croatia - > for the russian characters). A year later Pharo 4.0 came out and it > still was not fixed. Then Pharo 5.0 - same story. I have been learning > Smalltalk in small steps on Squeak and Pharo trying things from SBE > and PBE and my contact management example based on an excellent video > by Laurent Laffont. To cut a long story short only this month I have > reached the point that I was thinking maybe now I have what it takes to > fix this. And the excellent videos of the Pharo MOOC definitely played > a part too. Thanks to everyone involved. Anyway I tried to debug this > issue and it worked. So what if you were able to wave the magic wand to > make that bug go away? I have that wand. I'll see if I can jump through > the hoops of the contribution process although it might take some time. > > On a lighter note, I had a bright vision of how I could get some credit > for being able to fix this. I would find hire some really hot hostess > or two for an upcoming Pharo conference in Prague. They would have the > following on their T-shirts. One: 'Ä, Ä, Ä, Anyone?' and the other > 'Ð ,Ð, Ð, Ð, Ð, Ð, Anyone?' and 'Ask me how' on the back. :-). And > their job would be to hand out my email address to anyone interested. Or > even point to me standing in the distance. I bet they would command > some attention. I don't really want to be the one to discourage hot hostesses ;) but I think this would come across a bit false - like buying your way to fame. Your money is probably better spent on donating a few pizzas to the hacking sessions that often accompany these events. Or offer your time and effort into help organise the event (plus you end up interfacing with a lot of people.) If you a up for public speaking, be the one introducing the speakers, or get a ten minute presentation slot just to introduce yourself and give a newcomers perspective, for other newcomers in the audience to identify with and perhaps be encouraged to follow the same path. cheers -ben > > Mentoring. It would be nice to know how to find a mentor for the > contribution process, possibly beyond. > > Thanks for your attention, > Milan

June 15, 2016