February 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by Frank Shearar

On 19 February 2013 22:18, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Responses in the text below. > > 2013/2/19 Frank Shearar <frank.shearar(a)gmail.com>: >> On 19 February 2013 20:51, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >>> Got this thing biting me while testing the relase: >>> >>> I added a project of mine from the ss3.gemstone.com system and the >>> Monticello registration over there says: >>> >>> >>> MCHttpRepository >>> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >>> user: 'PBK' >>> password: '' >>> >>> >>> I add that into Pharo as a ss3 repository. >>> >>> There I am asked for: >>> >>> MCGemstoneRepository >>> location: 'http://ss3.gemstone.com/ss/' >>> user: '' >>> password: '' >> >> Where/what is "there"? Something's prompting you to fill in repository >> details and autofilled it with an MCGemstoneRepository declaration? > > Where is in Pharo 2.0 Monticello when adding an SS3 repository. > That's what the text editor area contains as default text. > >> >>> I didn't noticed the MCGemstoneRepository instead of MCHttpRepository >>> and copy/pasted as usual. >>> >>> Then, error. >>> >>> Took a minute to see why and get my mcz back. >>> >>> So, either SS3 has to change the registration information or Pharo >>> does something weird with SS3. I don't know. >>> >>> Guess I need to put things in SmalltalkHub :-) >> >> Well, ss3 is just an HTTP Monticello repository service. It's not >> ss3's fault that something else mentioned MCGemstoneRepository. > > As long as both would work, it would be a non issue. But using > MCHttpRepository > location: 'http://ss3.gemstone.com/ss/HO-Experiments' > user: 'PBK' > password: '' > > fails miserably in Pharo 2.0. That's why I had to change it to > MCGemstoneRepository for it to work. > > So, either ss3 isn't just an HTTP Monticello repository service or > Pharo 2.0 introduced something special... I don't know. How very odd. I _always_ use MCHTTPRepository when accessing ss3 projects. frank >> frank >> >>> Phil >>> >> >

Feb. 19, 2013

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by Camillo Bruni

>>> Guess I need to put things in SmalltalkHub :-) >> >> Well, ss3 is just an HTTP Monticello repository service. It's not >> ss3's fault that something else mentioned MCGemstoneRepository. > > As long as both would work, it would be a non issue. But using > MCHttpRepository > location: 'http://ss3.gemstone.com/ss/HO-Experiments' > user: 'PBK' > password: '' > > fails miserably in Pharo 2.0. That's why I had to change it to > MCGemstoneRepository for it to work. > > So, either ss3 isn't just an HTTP Monticello repository service or > Pharo 2.0 introduced something special... I don't know. They both work without problems. And technically they are the same. We started to add the specific repositories for speed ups.

Feb. 19, 2013

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by phil＠highoctane.be

Read again. MCGemstoneRepository works. But on ss3, what is listed on the project? For sure not that but: MCHttpRepository. See screenshot. Ese es el problema... Phil 2013/2/19 Camillo Bruni <camillobruni(a)gmail.com>: > I cannot reproduce this on the latest pharo image.... > I added it as a MCGemstoneRepository with the full url and it works... > > MCGemstoneRepository > location: 'http://ss3.gemstone.com/ss/HO-Experiments' > user: '' > password: '' > > I can browse and load files. Can you give me more details? > > On 2013-02-19, at 21:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> Got this thing biting me while testing the relase: >> >> I added a project of mine from the ss3.gemstone.com system and the >> Monticello registration over there says: >> >> >> MCHttpRepository >> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >> user: 'PBK' >> password: '' >> >> >> I add that into Pharo as a ss3 repository. >> >> There I am asked for: >> >> MCGemstoneRepository >> location: 'http://ss3.gemstone.com/ss/' >> user: '' >> password: '' >> >> I didn't noticed the MCGemstoneRepository instead of MCHttpRepository >> and copy/pasted as usual. >> >> Then, error. >> >> Took a minute to see why and get my mcz back. >> >> So, either SS3 has to change the registration information or Pharo >> does something weird with SS3. I don't know. >> >> Guess I need to put things in SmalltalkHub :-) >> >> Phil >> > >

Feb. 19, 2013

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by Max Leske

I think I know what you might mean Phil, I've seen this myself: If you enter a username but no password for a repository (like the snippet from ss3 shows) then MC will prompt for username and pw. If you remove the username (empty string), you'll be fine. Not terribly bad but quite annoying. Max On 19.02.2013, at 23:11, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I cannot reproduce this on the latest pharo image.... > I added it as a MCGemstoneRepository with the full url and it works... > > MCGemstoneRepository > location: 'http://ss3.gemstone.com/ss/HO-Experiments' > user: '' > password: '' > > I can browse and load files. Can you give me more details? > > On 2013-02-19, at 21:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> Got this thing biting me while testing the relase: >> >> I added a project of mine from the ss3.gemstone.com system and the >> Monticello registration over there says: >> >> >> MCHttpRepository >> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >> user: 'PBK' >> password: '' >> >> >> I add that into Pharo as a ss3 repository. >> >> There I am asked for: >> >> MCGemstoneRepository >> location: 'http://ss3.gemstone.com/ss/' >> user: '' >> password: '' >> >> I didn't noticed the MCGemstoneRepository instead of MCHttpRepository >> and copy/pasted as usual. >> >> Then, error. >> >> Took a minute to see why and get my mcz back. >> >> So, either SS3 has to change the registration information or Pharo >> does something weird with SS3. I don't know. >> >> Guess I need to put things in SmalltalkHub :-) >> >> Phil >> > >

Feb. 19, 2013

Re: [Pharo-project] please test 2.0

by Camillo Bruni

I start to believe that it might be your VM? Which version are you using? Smalltalk vm version does the trick. On 2013-02-19, at 21:45, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Pharo 2.0 not 1.4 > > The World Menu > System >Software Update started working and then > threw me in teh debugger where I had the error. I inspected several > variables and then did some Restart,, Over, Over, ..Proceed and things > went fine. > > There was a ZnClient in there but I can't figure out why there was a > mention of SmallInteger. > > Phil > > 2013/2/19 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>> Even weirder: played with the debugger and sayed Over Over Over then >>> Proceed and it worked. Strange.... >>> >> What do you mean exactly ? You were not able to Proceed after clicking on >> Over several times on Pharo 1.4 ? >> I've just made a fix in the debugger that was integrated today.Give me more >> details to know if I have to look at it. >> >> Clement >> >>> Phil >>> >>> 2013/2/19 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> Hi, >>>> >>>> We are almost there for the release, but we still need a little effort >>>> more. >>>> Would be terrific if everyone of you took the latest 2.0 image and test >>>> it with your usual workflows (we cannot imagine all, they are infinite :) >>>> >>>> And please report bugs, and JUST bugs :) >>>> >>>> all the "nice to have" can be reported, but in 3.0 milestone (or not >>>> milestone at all). >>>> >>>> cheers, >>>> Esteban >>> >> >

Feb. 19, 2013

Re: [Pharo-project] Continuing weirdness with SS3.gemstone.com and Monticello in Pharo 2.0

by Camillo Bruni

this is rather strange. We're using gemstone for all pharo development and we haven't had any problems with it. I loaded all the stuff from your test-repository and it worked. more details? ;) On 2013-02-19, at 22:06, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > So, I wanted to merge my stuff from the SS3 project. > > When loading it needed to have BitBltPen (which I had somewhere as in > BitBltPen-MarianoMartinezPeck.4.mcz) > > I wanted to put that into my SS3 area and so, added the repository to > the list of repos in monticello, then took the mcz and then added the > repository to the package. > > Net result: Frozen image. > > No amount of Cmd-. could do anything. > > See screenshot. > > ... now restarting VM... > > Phil > <Capture dâÃ©cran 2013-02-19 Ã 22.01.46.png>

Feb. 19, 2013

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by phil＠highoctane.be

Responses in the text below. 2013/2/19 Frank Shearar <frank.shearar(a)gmail.com>: > On 19 February 2013 20:51, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> Got this thing biting me while testing the relase: >> >> I added a project of mine from the ss3.gemstone.com system and the >> Monticello registration over there says: >> >> >> MCHttpRepository >> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >> user: 'PBK' >> password: '' >> >> >> I add that into Pharo as a ss3 repository. >> >> There I am asked for: >> >> MCGemstoneRepository >> location: 'http://ss3.gemstone.com/ss/' >> user: '' >> password: '' > > Where/what is "there"? Something's prompting you to fill in repository > details and autofilled it with an MCGemstoneRepository declaration? Where is in Pharo 2.0 Monticello when adding an SS3 repository. That's what the text editor area contains as default text. > >> I didn't noticed the MCGemstoneRepository instead of MCHttpRepository >> and copy/pasted as usual. >> >> Then, error. >> >> Took a minute to see why and get my mcz back. >> >> So, either SS3 has to change the registration information or Pharo >> does something weird with SS3. I don't know. >> >> Guess I need to put things in SmalltalkHub :-) > > Well, ss3 is just an HTTP Monticello repository service. It's not > ss3's fault that something else mentioned MCGemstoneRepository. As long as both would work, it would be a non issue. But using MCHttpRepository location: 'http://ss3.gemstone.com/ss/HO-Experiments' user: 'PBK' password: '' fails miserably in Pharo 2.0. That's why I had to change it to MCGemstoneRepository for it to work. So, either ss3 isn't just an HTTP Monticello repository service or Pharo 2.0 introduced something special... I don't know. > > frank > >> Phil >> >

Feb. 19, 2013

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by Camillo Bruni

I cannot reproduce this on the latest pharo image.... I added it as a MCGemstoneRepository with the full url and it works... MCGemstoneRepository location: 'http://ss3.gemstone.com/ss/HO-Experiments' user: '' password: '' I can browse and load files. Can you give me more details? On 2013-02-19, at 21:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Got this thing biting me while testing the relase: > > I added a project of mine from the ss3.gemstone.com system and the > Monticello registration over there says: > > > MCHttpRepository > location: 'http://ss3.gemstone.com/ss/HO-Experiments' > user: 'PBK' > password: '' > > > I add that into Pharo as a ss3 repository. > > There I am asked for: > > MCGemstoneRepository > location: 'http://ss3.gemstone.com/ss/' > user: '' > password: '' > > I didn't noticed the MCGemstoneRepository instead of MCHttpRepository > and copy/pasted as usual. > > Then, error. > > Took a minute to see why and get my mcz back. > > So, either SS3 has to change the registration information or Pharo > does something weird with SS3. I don't know. > > Guess I need to put things in SmalltalkHub :-) > > Phil >

Feb. 19, 2013

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by Frank Shearar

On 19 February 2013 20:51, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Got this thing biting me while testing the relase: > > I added a project of mine from the ss3.gemstone.com system and the > Monticello registration over there says: > > > MCHttpRepository > location: 'http://ss3.gemstone.com/ss/HO-Experiments' > user: 'PBK' > password: '' > > > I add that into Pharo as a ss3 repository. > > There I am asked for: > > MCGemstoneRepository > location: 'http://ss3.gemstone.com/ss/' > user: '' > password: '' Where/what is "there"? Something's prompting you to fill in repository details and autofilled it with an MCGemstoneRepository declaration? > I didn't noticed the MCGemstoneRepository instead of MCHttpRepository > and copy/pasted as usual. > > Then, error. > > Took a minute to see why and get my mcz back. > > So, either SS3 has to change the registration information or Pharo > does something weird with SS3. I don't know. > > Guess I need to put things in SmalltalkHub :-) Well, ss3 is just an HTTP Monticello repository service. It's not ss3's fault that something else mentioned MCGemstoneRepository. frank > Phil >

Feb. 19, 2013

Re: [Pharo-project] Slices and monticello - add to package... or add package to ... ? + procedure

by Sean P. DeNigris

Thanks for updating this, phil! philippeback wrote > I was educating myself on slices. Maybe I'll be able to contribute a > bit properly one of these days. It's actually sooo easy now... much has been streamlined... philippeback wrote > All right, I can understand but this feels like unnatural to be on a > repository and ask to "Add to package..." where what I want to do is > to add the package to the repository. I agree that this part of the UI is counter-intuitive, but the good news is, you don't have to do this step for slices anymore. The inbox is added automatically. philippeback wrote > Select your package-cache repository on the right hand pane. This step is no longer necessary. philippeback wrote > You will be prompted for a log message (for each one of them ?) There's just one commit message for the whole slice. philippeback wrote > Make sure to give the number of the issue your SLICE addresses in the > comment. Interesting. I never do that. Why is it necessary? philippeback wrote > Right click the repository and select "Add to package..." (this will > associate the package to the repository). Again, not necessary. Also, why save to the package cache first? I always save directly to the inbox and I'm pretty sure is automatically saves to the cache as well... Cheers, Sean -- View this message in context: http://forum.world.st/Slices-and-monticello-add-to-package-or-add-package-t… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 19, 2013