I’m not sure. Probably a concurrency issue (undetected so far) made a duplicate version of Pharo team. Then because of the duplicate Pharo team, a second Pharo40Inbox was created. Then some people committed slices to the new (and empty) Pharo40Inbox.
So, the solution was: - unify both projects (so all slices are in just one place) - detect and remove wrong Pharo40Inbox - detect and remove wrong Pharo team - review all structure so it has correct ids, etc. (viewed like this, looks easy, but it was a lot of tedious work :) ) On 25 Jul 2014, at 21:42, stepharo <[email protected]> wrote: > Thanks you both. > Could you explain a bit what was the problem? > Stef > > On 25/7/14 15:26, Esteban Lorenzano wrote: >> with the invaluable help of Nico, we managed to fixed it. >> (or at least we *think* we managed to fix it :D ) >> >> Esteban >> >> >> > >
