Is there any update on this? Thanks, Peter
On Mon, Jul 20, 2015 at 10:26 PM, Dale Henrichs < [email protected]> wrote: > Wait, the "fix" was on the pharo5.0_dev branch (not clear to me whether > this was even run against pharo5.0[1]) so it looks like Metacello is > stalled by FileTree issues at the moment and it looks like Thierry is > tackling the issues .... > > Dale > > [1] https://travis-ci.org/dalehenrich/filetree/builds/71656767 > > On 07/20/2015 01:13 PM, Dale Henrichs wrote: > > Okay ... apparently it isn't enough to fix the FileTree for Pharo 5.0, > because that nets you a MNU with FileReference>>closed[1]. > > This issue looks to have been fixed a day ago[3], so I will see if I can > kick off a rebuild of PR #351[2] and see where the port stands ... > > Dale > > [1] > https://github.com/dalehenrich/metacello-work/pull/351#issuecomment-122550670 > [2] https://github.com/dalehenrich/metacello-work/pull/351 > [3] https://travis-ci.org/dalehenrich/filetree/builds/71656767 > > On 07/20/2015 12:35 PM, Peter Uhnák wrote: > > Hmm, #onWarningLog doesn't exist either. > > I'm assuming this is the issue > https://pharo.fogbugz.com/f/cases/15456/Load-latest-version-of-metacello > > There's linked github issue > https://github.com/dalehenrich/metacello-work/issues/354 > > But running the script (in the github issue) fails, because there's no > defined spec for FileTree for Pharo 5.0 > > I'm not knowledgeable in Monticello so I don't know if I can do anything > to help besides user testing. > > Peter > > On Mon, Jul 20, 2015 at 9:22 PM, Marcus Denker <[email protected]> > wrote: > >> No. There is an issue on the issue tracker. >> >> If nobody pushes, nothing will happen. >> >> Marcus >> >> On 20 Jul 2015, at 21:04, Peter Uhnák <[email protected]> wrote: >> >> Hi, >> >> I was playing around with metacello because I wanted to ignore warnings >> with locks... >> >> currently I am doing something like >> >> ~~~~~~~~ >> Metacello new >> baseline: 'ProjectAAA'; >> repository: 'gitfiletree:///path/to/projectAAA'; >> lock. >> >> Metacello new >> baseline: 'ProjectBBB'; >> repository: 'gitfiletree:///projectBBB'; >> onConflict: [ :ex | ex allow ]; >> load. >> ~~~~~~~~~ >> >> This will load both projects via gitfiletree, however it will also >> generate a lots of lock warnings which I have to manually confirm - this is >> bad for scripts. >> >> So the docs ( >> https://github.com/dalehenrich/metacello-work/blob/master/docs/LockCommandReference.md >> ) >> >> mention onLock: [ :ex | ex honor ], however in Pharo 5.0 there is no >> such method "honor". >> >> Is this bug? >> Should Metacello be updated on Pharo 5.0? >> Will this even solve my problems? (Honoring locks while not throwing >> warnings). >> >> Thanks, >> Peter >> >> >> > > >
