> I know now let me repeat the bug I see
>
> This is not a bug of Monticello.
It is or may be of the network because
tell me the difference between scenario 1 and scenario 2?
I think that you do not read what I'm writing. There is no difference except
that in the first scenario it barks and the second it works.
And I just merge the latest working copy (which means that I did nothing) in
between.
scenario1
working copy polymorphWiget.7.mcz
I click on polymorphWiget.24.mcz
merge
-> I get an error ancestor cannot be found
scenario1
working copy polymorphWiget.7.mcz
I click on polymorphWiget.7.mcz
merge
-> no changes (ok this is what I hope what arriving)
Then
I click on polymorphWiget.24.mcz
merge
-> I get no error.!!!! AND I CAN MERGE!!!!
None.
So may be the network was flaky and when I merged the second time the package
was loaded in my cache.
I try to understand what is the problem.
> This is because you move versions
> around and you don't tell Monticello where to find them.
But our process does not move them around since packages in the inbox are
systematically merged
and the merged versions are copied into pharo. Then the commited versions are
moved to treated.
So we have a merge barrier! to keep the ancestry.
So by process we should not get that. This is strange that only this one is a
problem (may be they are some others)
but really few compared to the large number of package versions we have.
So this is probably a glitch somewhere
Lukas: I ***KNOW*** how MC branching/merging works. I KNOW IT. Now I'm trying
to understand how the moved package
could be moved in treated while it should have been to pharo.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
