[Seaside] Re: Problem upgrading seaside from an existing image
(Pharo #14438 and Seaside 3.0)
lasmiste at gmail.com
Tue Sep 10 12:25:26 UTC 2013
Thanks for your analysis. So, I'm starting to evaluate to migrate my
projects to Pharo 2
> Hi Dave,
> I have found the root cause of your problem:
> - During the update prices it tries to load
> package: 'Refactoring-Spelling' with: [
> spec repository: 'http://www.squeaksource.com/PharoTaskForces'.
> spec requires: 'Refactoring-Critics'.
> spec postLoadDoIt: #postLoadRBSpelling ];
> from the ConfigurationOfRefactoringBrowser.
> Because in this folder (http://www.squeaksource.com/PharoTaskForces')
> there is a file called ".mcz" Gofer fails.
> So you can either circumvent this problem, by making this package not to
> be loaded (i.e. update this package by hand to version 29 (the version it
> tries to fetch when crashing)) or make a bug fix, that it should no longer
> crash on invalid named packages. When I look at the implementation in
> Pharo 2.0, this implementation is already fixed. The method
> | all cached new emptyFilenamelength |
> emptyFilenamelength := 'P-i.c.mcz' size.
> all := self allFileNames. "from repository"
> all := all reject: [ :each | each size < emptyFilenamelength].
> "first stupid way to filter first level broken files. Ideally we should
> remove any files not following the naming pattern:
> cached := self cachedFileNames. "in memory"
> new := all difference: cached.
> ^ (cached asArray, new)
> select: [:ea | self canReadFileNamed: ea]
> is the fixed version.
View this message in context: http://forum.world.st/Problem-upgrading-seaside-from-an-existing-image-Pharo-14438-and-Seaside-3-0-tp4706594p4707464.html
Sent from the Seaside General mailing list archive at Nabble.com.
More information about the seaside