Gofer upgrade error
Locked
 
|
Hi Stephan I'm trying to have my image updated to the last version of each package that I'm using. I'm trying first: Gofer upgrade (to update Gofer) and then to update: Gofer gofer update (also have an error) Any advice to have all my third party packages updated? Thanks
|
|
|
Hi Leo,
I'm probably not the one able to provide a useful answer, but I'm curious which documentation describes that procedure :) ? It looks like something you might do in another different application. btw, which third party packages are you trying to update? cheers -ben P.S. Ideally all mail-list posts would be "plain text" (e.g. [1] for gmail), but please at least refrain from using garish fonts :) [1] https://mathiasbynens.be/notes/gmail-plain-text On Mon, May 25, 2015 at 9:54 PM, Leo Paniceres <[hidden email]> wrote: > > Hi Stephan > I'm trying to have my image updated to the last version of each package that I'm using. > I'm trying first: > Gofer upgrade (to update Gofer) > and then to update: > Gofer gofer update (also have an error) > > Any advice to have all my third party packages updated? > > Thanks > > >> >> ------------------------------ >> >> Message: 4 >> Date: Mon, 25 May 2015 08:53:26 +0200 >> From: stepharo <[hidden email]> >> To: Pharo Development List <[hidden email]> >> Subject: Re: [Pharo-dev] Gofer upgrade error >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=windows-1252; format=flowed >> >> Hello leo >> >> Thanks for your feedback. We will fix this >> >> unregisterPackageInfo: aWorkingCopy >> PackageOrganizer default >> unregisterPackage: aWorkingCopy packageInfo >> https://pharo.fogbugz.com/default.asp?15602 >> >> >> I do not think that anybody ever used upgrade. :) >> What do you want to do exactly? >> have a look at the deep into pharo book, there is a chapter on Gofer. >> >> >> >> >> >> Le 25/5/15 08:02, Leo a ?crit : >> > I have a fresh image of Pharo 4 -just downloaded-. >> > >> > When I try >> > Gofer upgrade >> > >> > I receive a MessageNotUnderstood: receiver of default is nil. >> > >> > What is happening? >> > >> > thanks >> > >> > >> >> |
|
|
In reply to this post by lpaniceres
Ben, the documentation for Gofer upgrade is and for Gofer gofer update afectuosamente Leo Message: 5 Date: Mon, 25 May 2015 23:59:38 +0800 From: Ben Coman <[hidden email]> To: Pharo Development List <[hidden email]> Subject: Re: [Pharo-dev] Gofer upgrade error Message-ID: <[hidden email]> Content-Type: text/plain; charset=UTF-8
|
|
|
In reply to this post by lpaniceres
Hi,
that will not work. and it will never work like that sadly. You are trying to use gofer as apt-get, and that’s not how it works… you cannot just update packages to have a working image with newer versions. The way pharo should work is: - there is the update process (world menu, system, update system) who will try to update the pharo system. That means not external project (like for instance seaside) will be updated. Please notice that this process is currently BROKEN, so you cannot try it now. We will restore it, but so far no time to work on it (also, is not top priority because is not of frequent use: most people needing to update just download an image and start over again, which is super easy to automatise using zeroconf and command line scripts). - you can update your installed projects by downloading newer configuration versions and applying them. But again, more frequent is to just doing it in a newer image. the reason why this is not really used is because pharo (smalltalk) extensibility is powerful but complicated to manage, due the amount of overriding methods, etc. cheers, Esteban
|
|
|
In reply to this post by lpaniceres
Thanks Leo. Indeed I see the commands you tried are suggested in those
references. On Tue, May 26, 2015 at 3:26 AM, Leo <[hidden email]> wrote: > Ben, > the documentation for "Gofer upgrade" is > http://file-pharo.inria.fr/doc/4.0/class/Gofer.html Doing this is 50064 I gives... 'MNU receiver of "default" is nil' in... GoferUnload>>unregisterPackageInfo: aWorkingCopy PackageOrganizer default unregisterPackage: aWorkingCopy packageInfo where PackageOrganizer is an unknown class. I've logged an issue... https://pharo.fogbugz.com/default.asp?15615 (whoops, I didn't notice Stef already created 15602) > and for "Gofer gofer update" > http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/Gofer.pdf Doing this gives... 'MNU: MCWorkingCopy>>packageInfo' in... GoferCleanup>>cleanupCategories: aWorkingCopy aWorkingCopy packageInfo systemCategories do: [ :category | (SystemOrganization goferClassesInCategory: category) isEmpty ifTrue: [ SystemOrganization removeSystemCategory: category ] ] Doing this again but in 20628 gives... "The method MCPackageManager>>packageInfo has been deprecated. Use #packageSet" So there remain 9 senders of packageInfo in 50064. I wasn't sure what issue to log here. But the bigger question is how might we guard against this sort of thing slipping through when we remove deprecations from the Image? cheers -ben > afectuosamente > Leo > > Message: 5 > Date: Mon, 25 May 2015 23:59:38 +0800 > From: Ben Coman <[hidden email]> > To: Pharo Development List <[hidden email]> > Subject: Re: [Pharo-dev] Gofer upgrade error > Message-ID: > <CAProBT=[hidden email]> > Content-Type: text/plain; charset=UTF-8 > > > > Hi Leo, > > I'm probably not the one able to provide a useful answer, but I'm > curious which documentation describes that procedure :) ? It looks > like something you might do in another different application. > > btw, which third party packages are you trying to update? > > cheers -ben > > > > P.S. Ideally all mail-list posts would be "plain text" (e.g. [1] for > gmail), but please at least refrain from using garish fonts :) > > [1] https://mathiasbynens.be/notes/gmail-plain-text > > > On Mon, May 25, 2015 at 9:54 PM, Leo Paniceres <[hidden email]> wrote: > > > Hi Stephan > I'm trying to have my image updated to the last version of each package > that I'm using. > I'm trying first: > Gofer upgrade (to update Gofer) > and then to update: > Gofer gofer update (also have an error) > > Any advice to have all my third party packages updated? > > Thanks > > > > ------------------------------ > > Message: 4 > Date: Mon, 25 May 2015 08:53:26 +0200 > From: stepharo <[hidden email]> > To: Pharo Development List <[hidden email]> > Subject: Re: [Pharo-dev] Gofer upgrade error > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=windows-1252; format=flowed > > Hello leo > > Thanks for your feedback. We will fix this > > unregisterPackageInfo: aWorkingCopy > PackageOrganizer default > unregisterPackage: aWorkingCopy packageInfo > https://pharo.fogbugz.com/default.asp?15602 > > > I do not think that anybody ever used upgrade. :) > What do you want to do exactly? > have a look at the deep into pharo book, there is a chapter on Gofer. > > > Le 25/5/15 08:02, Leo a ?crit : > > I have a fresh image of Pharo 4 -just downloaded-. > > When I try > Gofer upgrade > > I receive a MessageNotUnderstood: receiver of default is nil. > > What is happening? > > thanks |
|
|
> On 26 May 2015, at 17:30, Ben Coman <[hidden email]> wrote: > > Thanks Leo. Indeed I see the commands you tried are suggested in those > references. > > On Tue, May 26, 2015 at 3:26 AM, Leo <[hidden email]> wrote: >> Ben, >> the documentation for "Gofer upgrade" is >> http://file-pharo.inria.fr/doc/4.0/class/Gofer.html > > Doing this is 50064 I gives... 'MNU receiver of "default" is nil' in... > GoferUnload>>unregisterPackageInfo: aWorkingCopy > PackageOrganizer default > unregisterPackage: aWorkingCopy packageInfo The problem is that it loads a very old version of Gofer… one that e.g. uses the old filesystem, Packageinfo instead of RPackage and things like that. We should just remove the update method and solve update systemwide better. Marcus |
|
|
On Wed, May 27, 2015 at 1:49 PM, Marcus Denker <[hidden email]> wrote:
> >> On 26 May 2015, at 17:30, Ben Coman <[hidden email]> wrote: >> >> Thanks Leo. Indeed I see the commands you tried are suggested in those >> references. >> >> On Tue, May 26, 2015 at 3:26 AM, Leo <[hidden email]> wrote: >>> Ben, >>> the documentation for "Gofer upgrade" is >>> http://file-pharo.inria.fr/doc/4.0/class/Gofer.html >> >> Doing this is 50064 I gives... 'MNU receiver of "default" is nil' in... >> GoferUnload>>unregisterPackageInfo: aWorkingCopy >> PackageOrganizer default >> unregisterPackage: aWorkingCopy packageInfo > > > The problem is that it loads a very old version of Gofer… one that > e.g. uses the old filesystem, Packageinfo instead of RPackage > and things like that. > > We should just remove the update method and solve update systemwide > better. > > Marcus "Gofer upgrade" currently loads latest packages from repository 'http://source.lukas-renggli.ch/gofer' being... Name: Gofer-lr.113 Time: 11 January 2010 Name: Gofer-Core-lr.128 Time: 4 June 2010 Name: Gofer-Tests-lr.121 Time: 29 May 2010 Since our Gofer has been updated to use FileSystem & RPackage, we have effectively forked. I can't find another repository and can't see Gofer in Squeak 4.5, so what path do we want going forward. Maybe... 1. Create a ConfigurationOfGofer 2a. Change "Gofer upgrade" to load the Configuration - which would minimise issues with existing documentation. or... 2b. Remove "Gofer upgrade" - maybe leaving a notice to use the Configuration. I've opened case https://pharo.fogbugz.com/default.asp?15651 cheers -ben |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |