[Seaside-dev] broken MC versions
Philippe Marschall
philippe.marschall at gmail.com
Wed Jul 20 10:12:39 UTC 2011
2011/7/20 Lukas Renggli <renggli at gmail.com>:
> What versions of Pharo are affected? Is this also a problem in the
> widely used Pharo 1.2.1?
It looks like a VM/plugin issue, you can check whether you're affected with:
((1 to: 100) collect: [ :i |
UUID new asString ]) asSet size
> What is the exact problem we get?
If you inspect the history of Seaside-Core-pmm.731 it gets cropped at
Seaside-Core-pmm.729 because the ancestor has the same UUID.
I don't know whether the merge code uses the same logic as the UI code.
> 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.
Assuming only WIP versions are affected, I though more of a way to
extract and replay a change set and then commit a new version with a
different version number and UUID.
Cheers
Philippe
More information about the seaside-dev
mailing list