Thanks to the effort of SeanDiNigris, we continue trying to find out the problem. Sean asked me if the package contained non-asci characters..and yes, it has widestrings directly in the literal of a method (this is on purpose). The method is #testWideString
Dale Henrichs told me there could be some problems with WideStrings and Gemstone in the ss3. So far I didn't find anyone...but now it seems we do? i think this problem was forever..and the unziping from the OS fails, but somehow the unziping from Monticello does work? Any ideas? Thanks! On Mon, Jun 25, 2012 at 9:17 AM, Pavel Krivanek <[email protected]>wrote: > Can you try to file-in the uncompressed file? Or at least look if the > file is complete. Because I discovered this issue when trying to load > Fuel tests into the Pharo Kernel (the download and unzip of the > package is done directly by Pharo) and I had no problem with unzip of > this file on Linux but the resultant file was not complete and the > loading finished with syntax error. > > -- Pavel > > On Sun, Jun 24, 2012 at 11:58 PM, [email protected] <[email protected]> > wrote: > > I downloaded it, renamed the .mcz as a .zip and used the unarchiver on > it. > > No issue. > > > > 3271 lines in source.st > > > > OSX Lion over here. > > > > Was able to get it back from my 1.4 on CogVM and browse the downloaded > > package. > > > > Seems to be a OS X related issue. Rebooting a Mac may be rare, but may > > help... Network problems? Sometimes my NAS needs a kick in the butt.. > > > > Phil > > > > 2012/6/24 Mariano Martinez Peck <[email protected]> > >> > >> Hi guys. I have a problem and I don't understand. If you download > >> FuelTests-MarianoMartinezPeck.269 from http://ss3.gemstone.com/ss/Fueland > >> try to unzip it, in my MacOSX I have an error saying the fie is > corrupted. > >> If I proceed anyway, and I open the .st it is CUT in the middle (it > does not > >> finish properly). I thought it was a problem with Traits (because > FuelTest > >> has traits), but I tried other packages even with traits and they are > fine. > >> Then I thought that that version of the package could be corrupted, but > I > >> went several versions ago in history and same problem. Then thoguht it > was > >> Monticello problem. I went to Pharo 2.0 20020 and again, same problem. > >> > >> So I am lost. I remember something about the zip compression problem in > >> Monticello.... could this be related? > >> > >> thanks > >> > >> -- > >> Mariano > >> http://marianopeck.wordpress.com > >> > > > > > > > > -- > > Philippe Back > > Dramatic Performance Improvements > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: > [email protected] | > > Web: http://philippeback.eu | Blog: http://philippeback.be > > > > High Octane SPRL > > rue cour Boisacq 101 > > 1301 Bierges > > Belgium > > -- Mariano http://marianopeck.wordpress.com
