Thanks Leo. Indeed I see the commands you tried are suggested in those references. On Tue, May 26, 2015 at 3:26 AM, Leo <lpaniceres@gmail.com> 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 <btc@openinworld.com> To: Pharo Development List <pharo-dev@lists.pharo.org> Subject: Re: [Pharo-dev] Gofer upgrade error Message-ID: <CAProBT=B2yzdjUWveea8w2c4PY_NH2ZuGk-TW-ZWhHC3iv9KzA@mail.gmail.com> 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 <lpaniceres@gmail.com> 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 <stepharo@free.fr> To: Pharo Development List <pharo-dev@lists.pharo.org> Subject: Re: [Pharo-dev] Gofer upgrade error Message-ID: <5562C6E6.901@free.fr> 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