[Seaside-dev] broken MC versions

[Lukas Renggli]

To me it looks like colliding UUIDs are only a problem if different
versions with the same filename (same package, branch, version number,
initials) are committed to different repositories. I am far from any
image to verify this, but if this is the case then it is fairly easy
to avoid further problems and unlikely to have caused many problems up
to now.

Lukas

On Wednesday, 20 July 2011, Lukas Renggli <renggli at gmail.com> wrote:
> What versions of Pharo are affected? Is this also a problem in the
> widely used Pharo 1.2.1?
>
> What is the exact problem we get?
>
> Finding: You could use Gofer to fetch all versions and extract the UUID.
>
> Fixing: Not really possible, because the ancestry of all existing
> verions would need to be rewritten.
>
> Lukas
>
> On Wednesday, 20 July 2011, Philippe Marschall
> <philippe.marschall at gmail.com> wrote:
>> Hi
>>
>> Due to a known, long standing bug with a trivial fix in Pharo there
>> are several versions in the Seaside WIP repository with the same UUID.
>> This obviously breaks MC. This is potentially not limited to the WIP
>> repository but could potentially also be the case for the main
>> repository. Doe anybody know a way of finding and fixing all these?
>>
>> Cheers
>> Philippe
>> _______________________________________________
>> seaside-dev mailing list
>> seaside-dev at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>

-- 
Lukas Renggli
www.lukas-renggli.ch