Re: [Pharo-dev] issue validation needed
Tested in 30 and 40 with normal configurations. Somebody who is using FileTree should test Git configurations. Max On 07.06.2014, at 15:50, Esteban Lorenzano wrote: > Hi, > > this is a problem that arises with the ConfigurationOfCog (changed to use > VMMaker.oscog, instead VMMaker-oscog). > is hard to reproduce because I spotted it in a weird combination: is a > configuration that uses just the baseline and files are in filetree format. > > to reproduce it, save a package as a branch (for example, save package A as > A.branch-YourName.1) > then change a configuration: > > package: ‘A.branch’ > > then you will see an error. > but most important to me is to check that this change does not forbids other > configurations to load. > also I will need to backport it to 3.0 because this is needed for building > the vm :( > > yes, I could rename the package again and use it like before, but I wanted to > align as close as possible to current Eliot sources. > > cheers, > Esteban > > On 05 Jun 2014, at 14:49, Max Leske wrote: > >> Is there an easy way to reproduce this? I don’t quite see what I have to do >> to verify the fix. >> >> >>> On 05.06.2014, at 14:30, Damien Cassou wrote: >>> >>> On Wed, Jun 4, 2014 at 9:12 PM, Esteban Lorenzano >>> wrote: can someone check this metacello issue? https://pharo.fogbugz.com/f/cases/13305/ I really need it for continue with VM work. >>> >>> >>> for the laziest among you: >>> >>> Problem resolving branches with Metacello >>> The fix is in the Inbox >>> >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." >>> Winston Churchill >>> >> >> > >
Re: [Pharo-dev] issue validation needed
Hi, this is a problem that arises with the ConfigurationOfCog (changed to use VMMaker.oscog, instead VMMaker-oscog). is hard to reproduce because I spotted it in a weird combination: is a configuration that uses just the baseline and files are in filetree format. to reproduce it, save a package as a branch (for example, save package A as A.branch-YourName.1) then change a configuration: package: ‘A.branch’ then you will see an error. but most important to me is to check that this change does not forbids other configurations to load. also I will need to backport it to 3.0 because this is needed for building the vm :( yes, I could rename the package again and use it like before, but I wanted to align as close as possible to current Eliot sources. cheers, Esteban On 05 Jun 2014, at 14:49, Max Leske wrote: > Is there an easy way to reproduce this? I don’t quite see what I have to do > to verify the fix. > > >> On 05.06.2014, at 14:30, Damien Cassou wrote: >> >> On Wed, Jun 4, 2014 at 9:12 PM, Esteban Lorenzano >> wrote: >>> can someone check this metacello issue? >>> >>> https://pharo.fogbugz.com/f/cases/13305/ >>> >>> I really need it for continue with VM work. >> >> >> for the laziest among you: >> >> Problem resolving branches with Metacello >> The fix is in the Inbox >> >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> > >
Re: [Pharo-dev] issue validation needed
Hi esteban My brain is not working anymore. I'm totally exhausted. I hope tomorrow will be better :). Stef On 4/6/14 21:12, Esteban Lorenzano wrote: Hi, can someone check this metacello issue? https://pharo.fogbugz.com/f/cases/13305/ I really need it for continue with VM work. thanks, Esteban
Re: [Pharo-dev] issue validation needed
Is there an easy way to reproduce this? I don’t quite see what I have to do to verify the fix. > On 05.06.2014, at 14:30, Damien Cassou wrote: > > On Wed, Jun 4, 2014 at 9:12 PM, Esteban Lorenzano wrote: >> can someone check this metacello issue? >> >> https://pharo.fogbugz.com/f/cases/13305/ >> >> I really need it for continue with VM work. > > > for the laziest among you: > > Problem resolving branches with Metacello > The fix is in the Inbox > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >
Re: [Pharo-dev] issue validation needed
On Wed, Jun 4, 2014 at 9:12 PM, Esteban Lorenzano wrote: > can someone check this metacello issue? > > https://pharo.fogbugz.com/f/cases/13305/ > > I really need it for continue with VM work. for the laziest among you: Problem resolving branches with Metacello The fix is in the Inbox -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
[Pharo-dev] issue validation needed
Hi, can someone check this metacello issue? https://pharo.fogbugz.com/f/cases/13305/ I really need it for continue with VM work. thanks, Esteban
