latest filesystem is unloadable

> Hi,
>
> The bleeding edge version of Filesystem is unloadable in Pharo 1.3 (see the attached debug log).
>
> To test it, try:
>
> Gofer new
> squeaksource: 'fs';
> package: 'ConfigurationOfFilesystem';
> load.
> (Smalltalk at: #ConfigurationOfFilesystem) loadBleedingEdge
>
> Cheers,
> Doru
>
> --
> www.tudorgirba.com
>
> "From an abstract enough point of view, any two things are similar."
>
>
> <PharoDebug.log.zip>

> Why do you want to load the bleeding edge since 2.2.1 is fully tagged for reproduceability. I never used loadBleedingEdge and I did not garantee that it would work.
>
> Stef
>
>
> On Aug 15, 2011, at 11:31 PM, Tudor Girba wrote:
>
>> Hi,
>>
>> The bleeding edge version of Filesystem is unloadable in Pharo 1.3 (see the attached debug log).
>>
>> To test it, try:
>>
>> Gofer new
>> squeaksource: 'fs';
>> package: 'ConfigurationOfFilesystem';
>> load.
>> (Smalltalk at: #ConfigurationOfFilesystem) loadBleedingEdge
>>
>> Cheers,
>> Doru
>>
>> --
>> www.tudorgirba.com
>>
>> "From an abstract enough point of view, any two things are similar."
>>
>>
>> <PharoDebug.log.zip>
>
>

> Hi,
>
> Continuous integration is there to test continuously. I was not complaining :). I just reported this issue, especially given that it is a critical one (not being able to load the code). The problem appeared today, because yesterday it worked fine.
>
> But, where is 2.2.1? I load the code from the Configuration from the official www.squeaksource.com/fs.html repository, and there the latest version is 2.0.2.
>
> Cheers,
> Doru
>
>
> On 15 Aug 2011, at 23:52, Stéphane Ducasse wrote:
>
>> Why do you want to load the bleeding edge since 2.2.1 is fully tagged for reproduceability. I never used loadBleedingEdge and I did not garantee that it would work.
>>
>> Stef
>>
>>
>> On Aug 15, 2011, at 11:31 PM, Tudor Girba wrote:
>>
>>> Hi,
>>>
>>> The bleeding edge version of Filesystem is unloadable in Pharo 1.3 (see the attached debug log).
>>>
>>> To test it, try:
>>>
>>> Gofer new
>>> squeaksource: 'fs';
>>> package: 'ConfigurationOfFilesystem';
>>> load.
>>> (Smalltalk at: #ConfigurationOfFilesystem) loadBleedingEdge
>>>
>>> Cheers,
>>> Doru
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "From an abstract enough point of view, any two things are similar."
>>>
>>>
>>> <PharoDebug.log.zip>
>>
>>
>
> --
> www.tudorgirba.com
>
> "Live like you mean it."
>
>

> Hi,
>
> Continuous integration is there to test continuously. I was not complaining :). I just reported this issue, especially given that it is a critical one (not being able to load the code). The problem appeared today, because yesterday it worked fine.
>
> But, where is 2.2.1? I load the code from the Configuration from the official www.squeaksource.com/fs.html repository, and there the latest version is 2.0.2.
>
> Cheers,
> Doru
>
>
> On 15 Aug 2011, at 23:52, Stéphane Ducasse wrote:
>
>> Why do you want to load the bleeding edge since 2.2.1 is fully tagged for reproduceability. I never used loadBleedingEdge and I did not garantee that it would work.
>>
>> Stef
>>
>>
>> On Aug 15, 2011, at 11:31 PM, Tudor Girba wrote:
>>
>>> Hi,
>>>
>>> The bleeding edge version of Filesystem is unloadable in Pharo 1.3 (see the attached debug log).
>>>
>>> To test it, try:
>>>
>>> Gofer new
>>> squeaksource: 'fs';
>>> package: 'ConfigurationOfFilesystem';
>>> load.
>>> (Smalltalk at: #ConfigurationOfFilesystem) loadBleedingEdge
>>>
>>> Cheers,
>>> Doru
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "From an abstract enough point of view, any two things are similar."
>>>
>>>
>>> <PharoDebug.log.zip>
>>
>>
>
> --
> www.tudorgirba.com
>
> "Live like you mean it."
>
>