Re: [Pharo-project] 1.3 core and full image
On Jun 29, 2011, at 11:19 AM, Norbert Hartl wrote:
Finally I decided to switch my working environment from 1.2 to 1.3. And I like to it from pharo core because I want to learn how can produce my own image. But I struggle right at the beginning. I could load ocompletion and shout. Loading anything that has a dependency on omnibrowser fails. Doing it by loading
ConfigurationOfPharo project latestVersion load
it cannot resolve OB-Standard-lr.541
After that I looked on ci.pharo-project.org because there it works. But if I look at Pharo-1.3.st it loads it this way
"Dev image" Deprecation raiseWarning: false. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load.
((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load.
I don't know how this can work. In my image there is no lastVersion in metacello only latestVersion.
It works on the test server. I never tried it else
The presence of a thread about "not using pharo full" should show that it is rather easy to build up your own image. Unfortunately I'm too stupid to do it. How is it supposed to work?
No pharo full means retiring ConfigurationOfPharo... at least, I can not gurantuee that it works, I tried, I failed. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Am 29.06.2011 um 12:19 schrieb Marcus Denker:
On Jun 29, 2011, at 11:19 AM, Norbert Hartl wrote:
Finally I decided to switch my working environment from 1.2 to 1.3. And I like to it from pharo core because I want to learn how can produce my own image. But I struggle right at the beginning. I could load ocompletion and shout. Loading anything that has a dependency on omnibrowser fails. Doing it by loading
ConfigurationOfPharo project latestVersion load
it cannot resolve OB-Standard-lr.541
After that I looked on ci.pharo-project.org because there it works. But if I look at Pharo-1.3.st it loads it this way
"Dev image" Deprecation raiseWarning: false. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load.
((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load.
I don't know how this can work. In my image there is no lastVersion in metacello only latestVersion.
It works on the test server. I never tried it else
The presence of a thread about "not using pharo full" should show that it is rather easy to build up your own image. Unfortunately I'm too stupid to do it. How is it supposed to work?
No pharo full means retiring ConfigurationOfPharo... at least, I can not gurantuee that it works, I tried, I failed.
Yes, but what is the plan after retiring ConfigurationOfPharo? I cannot get behind the first step using 1.3. There is a version in the ConfigurationOfOmnibrowser that does not exist or probably got lost in one of the many breadowns of squeaksource. Who is able to recover the file or upload it again? Eeverything I need to load depends somehow on omnibrowser. Probably you have a package cache on the ci server containing the package in request. Good for the test server. And finally everyone else does not seem to have a problem here. The best thing I can do is print myself a t-shirt "Too dumb for 1.3? stay happy with 1.2!" Norbert
On Wed, Jun 29, 2011 at 3:01 PM, Norbert Hartl <norbert@hartl.name> wrote:
Am 29.06.2011 um 12:19 schrieb Marcus Denker:
On Jun 29, 2011, at 11:19 AM, Norbert Hartl wrote:
Finally I decided to switch my working environment from 1.2 to 1.3. And
I like to it from pharo core because I want to learn how can produce my own image. But I struggle right at the beginning. I could load ocompletion and shout. Loading anything that has a dependency on omnibrowser fails.
Doing it by loading
ConfigurationOfPharo project latestVersion load
it cannot resolve OB-Standard-lr.541
After that I looked on ci.pharo-project.org because there it works. But if I look at Pharo-1.3.st it loads it this way
"Dev image" Deprecation raiseWarning: false. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load.
((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load.
I don't know how this can work. In my image there is no lastVersion in metacello only latestVersion.
It works on the test server. I never tried it else
The presence of a thread about "not using pharo full" should show that it is rather easy to build up your own image. Unfortunately I'm too stupid to do it. How is it supposed to work?
No pharo full means retiring ConfigurationOfPharo... at least, I can not gurantuee that it works, I tried, I failed.
Yes, but what is the plan after retiring ConfigurationOfPharo? I cannot get behind the first step using 1.3. There is a version in the ConfigurationOfOmnibrowser that does not exist or probably got lost in one of the many breadowns of squeaksource. Who is able to recover the file or upload it again? Eeverything I need to load depends somehow on omnibrowser. Probably you have a package cache on the ci server containing the package in request. Good for the test server. And finally everyone else does not seem to have a problem here.
Hi Norbert. #lastVersion MUST exist when loading Metacello. If it doesn't exist after loading it, then there is a problem. In such case, please report it. ConfigurationOfOmnibrowse DOES exist and has existed since more than one year already. If you need an specific version, tell us which one exactly.
The best thing I can do is print myself a t-shirt "Too dumb for 1.3? stay happy with 1.2!"
No. The best thing you can do is to help the process. Nothing happens with magic. Just keep asking and try to make it work. Report problems. And try to test it before the release. -- Mariano http://marianopeck.wordpress.com
Am 29.06.2011 um 15:28 schrieb Mariano Martinez Peck:
On Wed, Jun 29, 2011 at 3:01 PM, Norbert Hartl <norbert@hartl.name> wrote:
Am 29.06.2011 um 12:19 schrieb Marcus Denker:
On Jun 29, 2011, at 11:19 AM, Norbert Hartl wrote:
Finally I decided to switch my working environment from 1.2 to 1.3. And I like to it from pharo core because I want to learn how can produce my own image. But I struggle right at the beginning. I could load ocompletion and shout. Loading anything that has a dependency on omnibrowser fails. Doing it by loading
ConfigurationOfPharo project latestVersion load
it cannot resolve OB-Standard-lr.541
After that I looked on ci.pharo-project.org because there it works. But if I look at Pharo-1.3.st it loads it this way
"Dev image" Deprecation raiseWarning: false. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load.
((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load.
I don't know how this can work. In my image there is no lastVersion in metacello only latestVersion.
It works on the test server. I never tried it else
The presence of a thread about "not using pharo full" should show that it is rather easy to build up your own image. Unfortunately I'm too stupid to do it. How is it supposed to work?
No pharo full means retiring ConfigurationOfPharo... at least, I can not gurantuee that it works, I tried, I failed.
Yes, but what is the plan after retiring ConfigurationOfPharo? I cannot get behind the first step using 1.3. There is a version in the ConfigurationOfOmnibrowser that does not exist or probably got lost in one of the many breadowns of squeaksource. Who is able to recover the file or upload it again? Eeverything I need to load depends somehow on omnibrowser. Probably you have a package cache on the ci server containing the package in request. Good for the test server. And finally everyone else does not seem to have a problem here.
Hi Norbert. #lastVersion MUST exist when loading Metacello. If it doesn't exist after loading it, then there is a problem. In such case, please report it.
I don't know it very well. I only know latestVersion to be present for sure.
ConfigurationOfOmnibrowse DOES exist and has existed since more than one year already. If you need an specific version, tell us which one exactly.
I didn't tell the ConfigurationOf is missing. It is the file OB-Standard-lr.541 that is in the ConfigurationOf
The best thing I can do is print myself a t-shirt "Too dumb for 1.3? stay happy with 1.2!"
No. The best thing you can do is to help the process. Nothing happens with magic. Just keep asking and try to make it work. Report problems. And try to test it before the release.
Yep, that is true if I would try an esoteric use case. But I don't. Taking a pharo 1.3 core from the CI server and doing Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMetacello'; load ConfigurationOfMetacello project updateProject Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load ConfigurationOfSeaside30 project lastVersion load isn't that strange, right? ConfigurationOfSeaside30 references OmniBrowser stable. OmniBrowser stable is 1.3 which references the file OmniBrowser-Standard-lr.541 which can not be found in the repository specified for omnibrowser. So I'm trying to understand this. Either I'm doing something wrong or the CI stuff is broken. And I don't have a glue how others solve this. Norbert
ConfigurationOfOmnibrowse DOES exist and has existed since more than one year already. If you need an specific version, tell us which one exactly.
I didn't tell the ConfigurationOf is missing. It is the file OB-Standard-lr.541 that is in the ConfigurationOf
I guess squeaksource lost again that verison. I have just publish it again.
The best thing I can do is print myself a t-shirt "Too dumb for 1.3? stay happy with 1.2!"
No. The best thing you can do is to help the process. Nothing happens with magic. Just keep asking and try to make it work. Report problems. And try to test it before the release.
Yep, that is true if I would try an esoteric use case. But I don't. Taking a pharo 1.3 core from the CI server and doing
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMetacello'; load ConfigurationOfMetacello project updateProject
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load
ConfigurationOfSeaside30 project lastVersion load
isn't that strange, right? ConfigurationOfSeaside30 references OmniBrowser stable. OmniBrowser stable is 1.3 which references the file OmniBrowser-Standard-lr.541 which can not be found in the repository specified for omnibrowser.
So I'm trying to understand this. Either I'm doing something wrong or the CI stuff is broken. And I don't have a glue how others solve this.
Norbert
-- Mariano http://marianopeck.wordpress.com
Am 29.06.2011 um 16:47 schrieb Mariano Martinez Peck:
ConfigurationOfOmnibrowse DOES exist and has existed since more than one year already. If you need an specific version, tell us which one exactly.
I didn't tell the ConfigurationOf is missing. It is the file OB-Standard-lr.541 that is in the ConfigurationOf
I guess squeaksource lost again that verison. I have just publish it again.
Thanks, now it is working. Norbert
The best thing I can do is print myself a t-shirt "Too dumb for 1.3? stay happy with 1.2!"
No. The best thing you can do is to help the process. Nothing happens with magic. Just keep asking and try to make it work. Report problems. And try to test it before the release.
Yep, that is true if I would try an esoteric use case. But I don't. Taking a pharo 1.3 core from the CI server and doing
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMetacello'; load
ConfigurationOfMetacello project updateProject
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load
ConfigurationOfSeaside30 project lastVersion load
isn't that strange, right? ConfigurationOfSeaside30 references OmniBrowser stable. OmniBrowser stable is 1.3 which references the file OmniBrowser-Standard-lr.541 which can not be found in the repository specified for omnibrowser.
So I'm trying to understand this. Either I'm doing something wrong or the CI stuff is broken. And I don't have a glue how others solve this.
Norbert
-- Mariano http://marianopeck.wordpress.com
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMetacello'; load
ConfigurationOfMetacello project updateProject
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load
ConfigurationOfSeaside30 project lastVersion load
isn't that strange, right? ConfigurationOfSeaside30 references OmniBrowser stable. OmniBrowser stable is 1.3 which references the file OmniBrowser-Standard-lr.541 which can not be found in the repository specified for omnibrowser.
So I'm trying to understand this. Either I'm doing something wrong or the CI stuff is broken. And I don't have a glue how others solve this.
Ok this looks strange. Indeed may be the file got lost somewhere. Stef
I see that you've got your build going now. Anyhow, here's the reply that I started before lunch... On 29/06/11 9:50 AM, Norbert Hartl wrote:
ConfigurationOfSeaside30 project lastVersion load
isn't that strange, right? ConfigurationOfSeaside30 references OmniBrowser stable. OmniBrowser stable is 1.3 which references the file OmniBrowser-Standard-lr.541 which can not be found in the repository specified for omnibrowser.
So I'm trying to understand this. Either I'm doing something wrong or the CI stuff is broken. And I don't have a glue how others solve this.
My build script is at: http://hudson.jooshr.org/view/Pharo1.3/job/Pharo1.3-Seaside3.0/ws/p13-seasid... I've not looked at it in a while. It seems that I load Seaside using Gofer, without going through Metacello. It's done this way, because the ConfigurationOfSeaside30 did not exist, when this build was set up. I also do not load Omnibrowser because it was not loading properly, at the time I was setting up my build. I had to adjust the Seaside packages that were loaded, to avoid the need for Omnibrowser. In some downstream jobs, I do use Monticello configs, because they were available, when I was setting up those build jobs. Your guess that the missing package is in the build cache is likely correct. That missing package is available at: http://source.lukas-renggli.ch/omnibrowser.html That should get you past that hurdle in your build, so you can start to customize it.
Am 29.06.2011 um 20:34 schrieb Yanni Chiu:
I see that you've got your build going now. Anyhow, here's the reply that I started before lunch...
On 29/06/11 9:50 AM, Norbert Hartl wrote:
ConfigurationOfSeaside30 project lastVersion load
isn't that strange, right? ConfigurationOfSeaside30 references OmniBrowser stable. OmniBrowser stable is 1.3 which references the file OmniBrowser-Standard-lr.541 which can not be found in the repository specified for omnibrowser.
So I'm trying to understand this. Either I'm doing something wrong or the CI stuff is broken. And I don't have a glue how others solve this.
My build script is at: http://hudson.jooshr.org/view/Pharo1.3/job/Pharo1.3-Seaside3.0/ws/p13-seasid...
I'll take a look.
I've not looked at it in a while. It seems that I load Seaside using Gofer, without going through Metacello. It's done this way, because the ConfigurationOfSeaside30 did not exist, when this build was set up.
I don't use Metacello for most of the stuff in jenkins, too. I thought it might be a good idea to test this in my development image.
I also do not load Omnibrowser because it was not loading properly, at the time I was setting up my build. I had to adjust the Seaside packages that were loaded, to avoid the need for Omnibrowser.
I figured out the problem but didn't find the file. So this was a dead end.
In some downstream jobs, I do use Monticello configs, because they were available, when I was setting up those build jobs.
Your guess that the missing package is in the build cache is likely correct. That missing package is available at: http://source.lukas-renggli.ch/omnibrowser.html That should get you past that hurdle in your build, so you can start to customize it.
Hmmm, I though I looked at this location but couldn't find the particular file. The package in the package-cache is a two fold thing. I understand it is a big hussle for developers if they have problems because loading of a package fails. With the package-cache you lose to test a setup that is reproducible by others. That's not good but then it is a rare case (or should be) that might not need to be covered. thanks for your help, Norbert
The best thing I can do is print myself a t-shirt "Too dumb for 1.3? stay happy with 1.2!"
No. The best thing you can do is to help the process. Nothing happens with magic. Just keep asking and try to make it work. Report problems. And try to test it before the release.
+ 1 We are not magician just boring hard workers and sometimes we also get tired. Stef
participants (5)
-
Marcus Denker -
Mariano Martinez Peck -
Norbert Hartl -
Stéphane Ducasse -
Yanni Chiu