- Pharo-users - lists.pharo.org

Re: [Pharo-users] Syntax Error: Message pattern expected

by Johannes Brauer

I have got an image with my application running, so I could repair my rep. So, we can close the âissueâ. Cheers Johannes > Am 03.08.2017 um 20:45 schrieb Alistair Grant <akgrant0710(a)gmail.com>: > > On Thu, Aug 03, 2017 at 06:04:37PM +0000, Johannes Brauer wrote: >> Hi Ben, hi Alistair! >> >> Thank for your adjustment. In the meantime I looked backward in the version >> history and I found an older version which I can load without problems. Then I >> looked at the changes of the next higher version (producing the syntax error) >> and I found the following problem: >> [cid] >> Indeed, there is no message pattern, I have not a clue how something like that >> can happen. The question is: Can the repository be repaired? > > I've never really become familiar with mcz packages as I much prefer > git, so started using Iceberg as soon as possible, so someone else may > have a much better answer, however... > > It may be easier to load the previous version and manually apply the > changes in the latest version. If not... > > .mcz packages are just zip archives of a particular structure. You can > unzip the archive, find the corrupted method definition, manually fix > it, and re-zip the archive. It should then load. > > Cheers, > Alistair > > > > >> Johannes >> >> Am 03.08.2017 um 16:38 schrieb Ben Coman <btc(a)openinworld.com>: >> >> Hi Johannes, >> >> Is your Monticello repo public? Perhaps someone else could try to load the >> package to check something in it is not corrupt? >> >> cheers -ben >> >> On Thu, Aug 3, 2017 at 9:00 PM, Alistair Grant <akgrant0710(a)gmail.com> >> wrote: >> >> Hi Johannes, >> >> On Wed, Aug 02, 2017 at 08:59:33PM +0000, Johannes Brauer wrote: >>> >>>> Am 02.08.2017 um 21:44 schrieb Alistair Grant < >> akgrant0710(a)gmail.com>: >>>> >>>> On Wed, Aug 02, 2017 at 12:22:38PM -0700, jb wrote: >>>>> Hi everyone! >>>>> >>>>> I get this error when I try to load a package from my Monticello >> rep. I have >>>>> never seen this before and have not a clue where to look for the >> mistake. >>>>> >>>>> The error message window show: >>>>> Object <none> >>>>> >>>>> Any hints what to do? >>>>> >>>>> Johannes >>>> >>>> Someone may recognise this and be able to answer it straight off, >> but >>>> otherwise... >>>> >>>> Supply: >>>> >>>> - Pharo version and image number (World Menu -> System -> About) >>> Pharo4.0 >>> Latest update: #40626 >>>> - OS >>> macOs 10.12.6 >>>> - PharoDebug.log (if possible delete the old version and recreate >> the >>>> error) >>> PharoDebug.log is empty >>> >>> BTW, I tried to do the same with >>> Pharo 6.0 >>> Latest update: #60508 >>> >>> Same behavior >> >> One more piece of information I should have requested: >> >> Steps to reproduce (or even better, code that reproduces) the problem. >> >> Cheers, >> Alistair >

Aug. 3, 2017

Re: [Pharo-users] How to load a baseline in Iceberg? Get #addTo: sent to nil?

by Tim Mackinnon

So I dont think I am going crazy - but there are so many different ways of working. I'll raise a bug in the morning. The trouble with enabling metacello support is that baselines aren't configs and so they don't have methods like #project that it seems to rely on. Tim Sent from my iPhone > On 3 Aug 2017, at 20:29, Alistair Grant <akgrant0710(a)gmail.com> wrote: > >> On Thu, Aug 03, 2017 at 05:28:33PM +0100, Tim Mackinnon wrote: >> Alistair - does that mean you?ve not tried using that menu item on a baseline >> package? I think its there for this reason - but maybe Esteban will comment >> when he?s back from holiday. > > OK, that's embarrassing... I didn't read your email properly, and no, I > hadn't tried it. > > The error occurs when Iceberg's metacello integration is disabled. So > if you execute: > > Iceberg enableMetacelloIntegration: true. > > And then load the baseline, it will work, although Iceberg doesn't > refresh its display properly. > > Can you open a fogbugz issue on the error case? > > >> So on a related front - do you go to a separate workspace and type in >> >> >> Metacello new >> baseline: ?MyBaseline'; >> repository: 'filetree://./local-project/src'; >> load. >> >> ? > > Yep, but normally in a completely separate image so that it is a clean > environment. I normally have a script that loads all the required > packages, so I can just: > > pharo-ui Pharo.image load_all.st > > In the development environment (where I'm using Iceberg) everything is > loaded, so I'm just testing the package functionality, not loading the > packages. > > > Cheers, > Alistair > > > >> I have tried loading all the packages in iceberg and then tried to load them >> with a script like this (but its very awkward - and I hadn?t thought of just >> using the Metacello variant) >> >> BaselineOfLambda project version spec packageSpecsInLoadOrder allButLast do: [ >> :s | >> s version load ]. >> >> >> >> >> On 3 Aug 2017, at 14:15, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Tim, >> >> On Thu, Aug 03, 2017 at 10:55:09AM +0100, Tim Mackinnon wrote: >> >> It might be something in this area - I will have to study. I am using >> gitlab and have done a clone - so the packages are on my disk, but it >> did look like it wasn???t properly finding them due to the naming of >> the local git url (so not quite your issue, but in a similar space I >> think). >> >> I???m just surprised no-one else is mentioning this which makes me >> wonder if its my setup (although this is a vanilla zeroconf with >> nothing strange). >> >> I think you are supposed to be able to clone, then click on a >> baselineOf package and pick install - and this should get all your >> code into the image (that???s why there is an install menu item just >> on baselineOF packages?) >> >> >> I don't know the original intent, but I've never thought about Iceberg >> this way. >> >> My understanding is that baselineOf: is intended for use by metacello. >> Iceberg allows you to load individual packages, but it's focus area is >> code development, not package loading. >> >> I use Iceberg to load the baseline package, edit it, then save it back >> to the git repository, then load the entire project through metacello >> (usually in separate images so I'm testing in a clean environment). >> >> HTH, >> Alistair >> >> >> >> >> Tim >> >> >> On 3 Aug 2017, at 09:09, Herby Voj????k <herby(a)mailbox.sk> wrote: >> >> This works for me (to load BaselineOfTowergame from src/ relative >> to image location): >> >> | hereRef | >> hereRef := Smalltalk imageDirectory asFileReference. >> >> "Work around scp url hardwired 'git@'" >> IceScpRemote class compile: 'canHandleUrl: aRepositoryUrl >> "Very simplistic implementation that does not cover all cases" >> ^ aRepositoryUrl matchesRegex: ''([\w.-]+@|ssh\://).*'''. >> IceScpRemote compile: ((IceScpRemote >> #parseUrl) sourceCode >> copyReplaceAll: 'git@' with: '[\w.-]+@'). >> >> (IceRepositoryCreator new location: hereRef; subdirectory: 'src'; >> createRepository) register. >> >> IceGithubRepositoryType class compile: 'type ^ ''github+rw'''. >> "Work around github:// needing access" >> >> Iceberg enableMetacelloIntegration: true. >> Metacello new baseline: 'Towergame'; repository: 'gitlocal:///', >> (hereRef / 'src') fullName; load: 'development'. >> >> Towergame configure. >> >> Smalltalk snapshot: true andQuit: true. >> >> You may not need the workarounds (first is for non-"git@" remote, >> second is for github:// not working without a github.com ssh >> access). >> >> Tim Mackinnon wrote: >> >> I???m wondering if I???m missing a trick somewhere - but I have >> a simple >> project with 2 packages, one is a BaseLineOfMyPkg and the other >> is MyPkg >> (technically I don???t need the BaseLineOf, but I was learning >> how to use >> them and I simply added a postLoad hook to run some code in >> it). >> >> Anyway, If I clone my repo with Iceberg, I get 2 unloaded >> packages in >> the UI. If I right click on the BaseLine one, and click the ??? >> install >> baseline (default)??? option, I was expecting it to load both >> packages for >> me - however I get the talkback error ???#addTo: was sent to >> nil from the >> MCRepositoryGroup>>addRepository: method???. >> >> In trying to debug the code I can see its trying to find a >> handler for >> gitlocal:///, doesn???t find one and then tries to create a >> repo and >> bails??? this seems like a bug? I did notice in tracing the >> code that >> there is a reference to a Setting that I saw - ???Enable >> Metacello >> Integration??? - should I set that to true (its false by >> default)? >> >> I???m wondering how other people are loading their projects in >> Iceberg if >> this doesn???t work? >> >> Tim >

Aug. 3, 2017

Re: [Pharo-users] How to load a baseline in Iceberg? Get #addTo: sent to nil?

by Alistair Grant

On Thu, Aug 03, 2017 at 05:28:33PM +0100, Tim Mackinnon wrote: > Alistair - does that mean you?ve not tried using that menu item on a baseline > package? I think its there for this reason - but maybe Esteban will comment > when he?s back from holiday. OK, that's embarrassing... I didn't read your email properly, and no, I hadn't tried it. The error occurs when Iceberg's metacello integration is disabled. So if you execute: Iceberg enableMetacelloIntegration: true. And then load the baseline, it will work, although Iceberg doesn't refresh its display properly. Can you open a fogbugz issue on the error case? > So on a related front - do you go to a separate workspace and type in > > > Metacello new > baseline: ?MyBaseline'; > repository: 'filetree://./local-project/src'; > load. > > ? Yep, but normally in a completely separate image so that it is a clean environment. I normally have a script that loads all the required packages, so I can just: pharo-ui Pharo.image load_all.st In the development environment (where I'm using Iceberg) everything is loaded, so I'm just testing the package functionality, not loading the packages. Cheers, Alistair > I have tried loading all the packages in iceberg and then tried to load them > with a script like this (but its very awkward - and I hadn?t thought of just > using the Metacello variant) > > BaselineOfLambda project version spec packageSpecsInLoadOrder allButLast do: [ > :s | > s version load ]. > > > > > On 3 Aug 2017, at 14:15, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Tim, > > On Thu, Aug 03, 2017 at 10:55:09AM +0100, Tim Mackinnon wrote: > > It might be something in this area - I will have to study. I am using > gitlab and have done a clone - so the packages are on my disk, but it > did look like it wasn???t properly finding them due to the naming of > the local git url (so not quite your issue, but in a similar space I > think). > > I???m just surprised no-one else is mentioning this which makes me > wonder if its my setup (although this is a vanilla zeroconf with > nothing strange). > > I think you are supposed to be able to clone, then click on a > baselineOf package and pick install - and this should get all your > code into the image (that???s why there is an install menu item just > on baselineOF packages?) > > > I don't know the original intent, but I've never thought about Iceberg > this way. > > My understanding is that baselineOf: is intended for use by metacello. > Iceberg allows you to load individual packages, but it's focus area is > code development, not package loading. > > I use Iceberg to load the baseline package, edit it, then save it back > to the git repository, then load the entire project through metacello > (usually in separate images so I'm testing in a clean environment). > > HTH, > Alistair > > > > > Tim > > > On 3 Aug 2017, at 09:09, Herby Voj????k <herby(a)mailbox.sk> wrote: > > This works for me (to load BaselineOfTowergame from src/ relative > to image location): > > | hereRef | > hereRef := Smalltalk imageDirectory asFileReference. > > "Work around scp url hardwired 'git@'" > IceScpRemote class compile: 'canHandleUrl: aRepositoryUrl > "Very simplistic implementation that does not cover all cases" > ^ aRepositoryUrl matchesRegex: ''([\w.-]+@|ssh\://).*'''. > IceScpRemote compile: ((IceScpRemote >> #parseUrl) sourceCode > copyReplaceAll: 'git@' with: '[\w.-]+@'). > > (IceRepositoryCreator new location: hereRef; subdirectory: 'src'; > createRepository) register. > > IceGithubRepositoryType class compile: 'type ^ ''github+rw'''. > "Work around github:// needing access" > > Iceberg enableMetacelloIntegration: true. > Metacello new baseline: 'Towergame'; repository: 'gitlocal:///', > (hereRef / 'src') fullName; load: 'development'. > > Towergame configure. > > Smalltalk snapshot: true andQuit: true. > > You may not need the workarounds (first is for non-"git@" remote, > second is for github:// not working without a github.com ssh > access). > > Tim Mackinnon wrote: > > I???m wondering if I???m missing a trick somewhere - but I have > a simple > project with 2 packages, one is a BaseLineOfMyPkg and the other > is MyPkg > (technically I don???t need the BaseLineOf, but I was learning > how to use > them and I simply added a postLoad hook to run some code in > it). > > Anyway, If I clone my repo with Iceberg, I get 2 unloaded > packages in > the UI. If I right click on the BaseLine one, and click the ??? > install > baseline (default)??? option, I was expecting it to load both > packages for > me - however I get the talkback error ???#addTo: was sent to > nil from the > MCRepositoryGroup>>addRepository: method???. > > In trying to debug the code I can see its trying to find a > handler for > gitlocal:///, doesn???t find one and then tries to create a > repo and > bails??? this seems like a bug? I did notice in tracing the > code that > there is a reference to a Setting that I saw - ???Enable > Metacello > Integration??? - should I set that to true (its false by > default)? > > I???m wondering how other people are loading their projects in > Iceberg if > this doesn???t work? > > Tim

Aug. 3, 2017

Unknown variable warning with a method name when saving a method

by Myroslava Romaniuk

Hi, I'm trying to add the rewrite option to the Match Tool, and when I create a method and try to debug the code I get the following: So basically it tells me that the name of the method is an unknown variable which I don't get at all. And when I try to set it as a temporary variable just to see what I'll get, I actually get an error like this...Anyone has any idea what can be the problem? Thanks, Myroslava

Aug. 3, 2017

Re: [Pharo-users] Syntax Error: Message pattern expected

by Alistair Grant

On Thu, Aug 03, 2017 at 06:04:37PM +0000, Johannes Brauer wrote: > Hi Ben, hi Alistair! > > Thank for your adjustment. In the meantime I looked backward in the version > history and I found an older version which I can load without problems. Then I > looked at the changes of the next higher version (producing the syntax error) > and I found the following problem: > [cid] > Indeed, there is no message pattern, I have not a clue how something like that > can happen. The question is: Can the repository be repaired? I've never really become familiar with mcz packages as I much prefer git, so started using Iceberg as soon as possible, so someone else may have a much better answer, however... It may be easier to load the previous version and manually apply the changes in the latest version. If not... .mcz packages are just zip archives of a particular structure. You can unzip the archive, find the corrupted method definition, manually fix it, and re-zip the archive. It should then load. Cheers, Alistair > Johannes > > Am 03.08.2017 um 16:38 schrieb Ben Coman <btc(a)openinworld.com>: > > Hi Johannes, > > Is your Monticello repo public? Perhaps someone else could try to load the > package to check something in it is not corrupt? > > cheers -ben > > On Thu, Aug 3, 2017 at 9:00 PM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > > Hi Johannes, > > On Wed, Aug 02, 2017 at 08:59:33PM +0000, Johannes Brauer wrote: > > > > > Am 02.08.2017 um 21:44 schrieb Alistair Grant < > akgrant0710(a)gmail.com>: > > > > > > On Wed, Aug 02, 2017 at 12:22:38PM -0700, jb wrote: > > >> Hi everyone! > > >> > > >> I get this error when I try to load a package from my Monticello > rep. I have > > >> never seen this before and have not a clue where to look for the > mistake. > > >> > > >> The error message window show: > > >> Object <none> > > >> > > >> Any hints what to do? > > >> > > >> Johannes > > > > > > Someone may recognise this and be able to answer it straight off, > but > > > otherwise... > > > > > > Supply: > > > > > > - Pharo version and image number (World Menu -> System -> About) > > Pharo4.0 > > Latest update: #40626 > > > - OS > > macOs 10.12.6 > > > - PharoDebug.log (if possible delete the old version and recreate > the > > > error) > > PharoDebug.log is empty > > > > BTW, I tried to do the same with > > Pharo 6.0 > > Latest update: #60508 > > > > Same behavior > > One more piece of information I should have requested: > > Steps to reproduce (or even better, code that reproduces) the problem. > > Cheers, > Alistair

Aug. 3, 2017

Pharo and Docker

by Gmail

I'm trying to get pharo and teapot working with Docker. I've downloaded the command line image and I see a lot of Docker images but I'm not quite clear on how to connect the parts... Tony Giaccone

Aug. 3, 2017

Re: [Pharo-users] Syntax Error: Message pattern expected

by Johannes Brauer

Hi Ben, hi Alistair! Thank for your adjustment. In the meantime I looked backward in the version history and I found an older version which I can load without problems. Then I looked at the changes of the next higher version (producing the syntax error) and I found the following problem: [cid:54AA1677-A657-46E1-BAEF-E4AD0236C463@Speedport_W_503V_Typ_C] Indeed, there is no message pattern, I have not a clue how something like that can happen. The question is: Can the repository be repaired? Johannes Am 03.08.2017 um 16:38 schrieb Ben Coman <btc(a)openinworld.com<mailto:btc@openinworld.com>>: Hi Johannes, Is your Monticello repo public? Perhaps someone else could try to load the package to check something in it is not corrupt? cheers -ben On Thu, Aug 3, 2017 at 9:00 PM, Alistair Grant <akgrant0710(a)gmail.com<mailto:akgrant0710@gmail.com>> wrote: Hi Johannes, On Wed, Aug 02, 2017 at 08:59:33PM +0000, Johannes Brauer wrote: > > > Am 02.08.2017 um 21:44 schrieb Alistair Grant <akgrant0710(a)gmail.com<mailto:akgrant0710@gmail.com>>: > > > > On Wed, Aug 02, 2017 at 12:22:38PM -0700, jb wrote: > >> Hi everyone! > >> > >> I get this error when I try to load a package from my Monticello rep. I have > >> never seen this before and have not a clue where to look for the mistake. > >> > >> The error message window show: > >> Object <none> > >> > >> Any hints what to do? > >> > >> Johannes > > > > Someone may recognise this and be able to answer it straight off, but > > otherwise... > > > > Supply: > > > > - Pharo version and image number (World Menu -> System -> About) > Pharo4.0 > Latest update: #40626 > > - OS > macOs 10.12.6 > > - PharoDebug.log (if possible delete the old version and recreate the > > error) > PharoDebug.log is empty > > BTW, I tried to do the same with > Pharo 6.0 > Latest update: #60508 > > Same behavior One more piece of information I should have requested: Steps to reproduce (or even better, code that reproduces) the problem. Cheers, Alistair

Aug. 3, 2017

Re: [Pharo-users] Iceberg and removing packages

by Esteban A. Maringolo

How can I know which version it is loaded? My system version is: "Pharo6.0 of 13 May 2016 update 60508" Regards. Esteban A. Maringolo 2017-08-03 6:27 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > so, this is probably a bug. > are you using latest iceberg version? (it should be 0.5.5â¦ the one present > on P6.1) > > Esteban > > > > On 3 Aug 2017, at 00:32, Tim Mackinnon <tim(a)testit.works> wrote: > > > > I just hit the same problem - I wanted to remove a package that I no > longer wanted - I went to the iceberg packages tab for the project and > picked remove from disk and then I did a synchronise and commit. At the > time I did notice that it didnât show a package removal change (but I > assumed that as it was gone, maybe you donât show that?). > > > > Tim > > > >> On 31 Jul 2017, at 13:30, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> > >> Did you commit? > >> > >>> On 31 Jul 2017, at 14:06, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: > >>> > >>> That's exactly what I did. But after synchronizing the repo, the > >>> package wasn't listed on Iceberg but it still was in in the repo. > >>> It happened with another package in another repo as well. > >>> > >>> If it happens again I'll let you know. > >>> > >>> Regards! > >>> > >>> Esteban A. Maringolo > >>> > >>> > >>> 2017-07-31 7:03 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >>>> Hi, > >>>> > >>>> In iceberg, you have to go to package tab and say "remove package > from disk" > >>>> > >>>> Esteban > >>>> > >>>>> On 30 Jul 2017, at 17:01, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: > >>>>> > >>>>> I got into the pharo-local/iceberg/... and git rm'ed the directory, > >>>>> commited and synchronized the project in Iceberg. > >>>>> > >>>>> I hope it doesn't break anything since I don't know how much "magic" > >>>>> does Iceberg behind the scenes other than automating the git commands > >>>>> and providing a centralized UI. > >>>>> > >>>>> What is the "This is all you need to read to understand Iceberg?" > >>>>> document I should read? I read its wiki, but it seems there is more > to > >>>>> go. > >>>>> > >>>>> Regards! > >>>>> > >>>>> Esteban A. Maringolo > >>>>> > >>>>> > >>>>> 2017-07-30 11:28 GMT-03:00 Peter Uhnak <i.uhnak(a)gmail.com>: > >>>>>> This was supposedly fixed in April https://github.com/pharo-vcs/ > iceberg/issues/317 > >>>>>> > >>>>>> however I had the same issue ~two months ago, so I had to delete > the packages by hand. > >>>>>> > >>>>>> P > >>>>>> > >>>>>> > >>>>>>> On Sun, Jul 30, 2017 at 11:04:20AM -0300, Esteban A. Maringolo > wrote: > >>>>>>> Hi, > >>>>>>> > >>>>>>> I'm playing around with Iceberg in Pharo 6, and even when I find > the > >>>>>>> workflow streamlined, but since it doesn't map 1:1 with git > workflow > >>>>>>> from other IDEs or command line, I find myself not knowing how to > do > >>>>>>> certain tasks. > >>>>>>> > >>>>>>> One thing that happened is that I published a few packages to one > of > >>>>>>> my repos in Github, then I decided to remove one of the packages > from > >>>>>>> the repo, then I synchronized it but in the repo there is still is > the > >>>>>>> package folder for the package I removed. > >>>>>>> > >>>>>>> What should I do to definitely remove those files from the commit? > >>>>>>> > >>>>>>> Regards! > >>>>>>> > >>>>>>> Esteban A. Maringolo > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > > > > > >

Aug. 3, 2017

Re: [Pharo-users] How to load a baseline in Iceberg? Get #addTo: sent to nil?

by Tim Mackinnon

Alistair - does that mean youâve not tried using that menu item on a baseline package? I think its there for this reason - but maybe Esteban will comment when heâs back from holiday. So on a related front - do you go to a separate workspace and type in Metacello new baseline: âMyBaseline'; repository: 'filetree://./local-project/src'; load. ? I have tried loading all the packages in iceberg and then tried to load them with a script like this (but its very awkward - and I hadnât thought of just using the Metacello variant) BaselineOfLambda project version spec packageSpecsInLoadOrder allButLast do: [ :s | s version load ]. > On 3 Aug 2017, at 14:15, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Tim, > > On Thu, Aug 03, 2017 at 10:55:09AM +0100, Tim Mackinnon wrote: >> It might be something in this area - I will have to study. I am using >> gitlab and have done a clone - so the packages are on my disk, but it >> did look like it wasn???t properly finding them due to the naming of >> the local git url (so not quite your issue, but in a similar space I >> think). >> >> I???m just surprised no-one else is mentioning this which makes me >> wonder if its my setup (although this is a vanilla zeroconf with >> nothing strange). >> >> I think you are supposed to be able to clone, then click on a >> baselineOf package and pick install - and this should get all your >> code into the image (that???s why there is an install menu item just >> on baselineOF packages?) > > I don't know the original intent, but I've never thought about Iceberg > this way. > > My understanding is that baselineOf: is intended for use by metacello. > Iceberg allows you to load individual packages, but it's focus area is > code development, not package loading. > > I use Iceberg to load the baseline package, edit it, then save it back > to the git repository, then load the entire project through metacello > (usually in separate images so I'm testing in a clean environment). > > HTH, > Alistair > > > >> Tim >> >>> On 3 Aug 2017, at 09:09, Herby Voj????k <herby(a)mailbox.sk> wrote: >>> >>> This works for me (to load BaselineOfTowergame from src/ relative to image location): >>> >>> | hereRef | >>> hereRef := Smalltalk imageDirectory asFileReference. >>> >>> "Work around scp url hardwired 'git@'" >>> IceScpRemote class compile: 'canHandleUrl: aRepositoryUrl >>> "Very simplistic implementation that does not cover all cases" >>> ^ aRepositoryUrl matchesRegex: ''([\w.-]+@|ssh\://).*'''. >>> IceScpRemote compile: ((IceScpRemote >> #parseUrl) sourceCode copyReplaceAll: 'git@' with: '[\w.-]+@'). >>> >>> (IceRepositoryCreator new location: hereRef; subdirectory: 'src'; createRepository) register. >>> >>> IceGithubRepositoryType class compile: 'type ^ ''github+rw'''. "Work around github:// needing access" >>> >>> Iceberg enableMetacelloIntegration: true. >>> Metacello new baseline: 'Towergame'; repository: 'gitlocal:///', (hereRef / 'src') fullName; load: 'development'. >>> >>> Towergame configure. >>> >>> Smalltalk snapshot: true andQuit: true. >>> >>> You may not need the workarounds (first is for non-"git@" remote, second is for github:// not working without a github.com ssh access). >>> >>> Tim Mackinnon wrote: >>>> I???m wondering if I???m missing a trick somewhere - but I have a simple >>>> project with 2 packages, one is a BaseLineOfMyPkg and the other is MyPkg >>>> (technically I don???t need the BaseLineOf, but I was learning how to use >>>> them and I simply added a postLoad hook to run some code in it). >>>> >>>> Anyway, If I clone my repo with Iceberg, I get 2 unloaded packages in >>>> the UI. If I right click on the BaseLine one, and click the ???install >>>> baseline (default)??? option, I was expecting it to load both packages for >>>> me - however I get the talkback error ???#addTo: was sent to nil from the >>>> MCRepositoryGroup>>addRepository: method???. >>>> >>>> In trying to debug the code I can see its trying to find a handler for >>>> gitlocal:///, doesn???t find one and then tries to create a repo and >>>> bails??? this seems like a bug? I did notice in tracing the code that >>>> there is a reference to a Setting that I saw - ???Enable Metacello >>>> Integration??? - should I set that to true (its false by default)? >>>> >>>> I???m wondering how other people are loading their projects in Iceberg if >>>> this doesn???t work? >>>> >>>> Tim >>> >>> >> >> >

Aug. 3, 2017

Re: [Pharo-users] Syntax Error: Message pattern expected

by Ben Coman

Hi Johannes, Is your Monticello repo public? Perhaps someone else could try to load the package to check something in it is not corrupt? cheers -ben On Thu, Aug 3, 2017 at 9:00 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Johannes, > > On Wed, Aug 02, 2017 at 08:59:33PM +0000, Johannes Brauer wrote: > > > > > Am 02.08.2017 um 21:44 schrieb Alistair Grant <akgrant0710(a)gmail.com>: > > > > > > On Wed, Aug 02, 2017 at 12:22:38PM -0700, jb wrote: > > >> Hi everyone! > > >> > > >> I get this error when I try to load a package from my Monticello rep. > I have > > >> never seen this before and have not a clue where to look for the > mistake. > > >> > > >> The error message window show: > > >> Object <none> > > >> > > >> Any hints what to do? > > >> > > >> Johannes > > > > > > Someone may recognise this and be able to answer it straight off, but > > > otherwise... > > > > > > Supply: > > > > > > - Pharo version and image number (World Menu -> System -> About) > > Pharo4.0 > > Latest update: #40626 > > > - OS > > macOs 10.12.6 > > > - PharoDebug.log (if possible delete the old version and recreate the > > > error) > > PharoDebug.log is empty > > > > BTW, I tried to do the same with > > Pharo 6.0 > > Latest update: #60508 > > > > Same behavior > > One more piece of information I should have requested: > > Steps to reproduce (or even better, code that reproduces) the problem. > > Cheers, > Alistair > > >

Aug. 3, 2017