2016-07-10 23:49 GMT+02:00 Yuriy Tymchuk <[email protected]>: > Settings should work now > > Yes! Thanks :-)
> On 26 Jun 2016, at 04:56, Juraj Kubelka <[email protected]> wrote: > > Thanks Yuriy! > > Last time, there was a problem on Jenkins. I do not have access to check > it or change it. > It is necessary that cleanUp process is called as a last command on > Jenkins. > > The other thing is to find out another solution. The current solution > expects that an instance variable is unset in a fresh (downloaded) image. > And this variable is set when the image is opened. > > Cheers, > Juraj > > On Jun 25, 2016, at 17:25, Yuriy Tymchuk <[email protected]> wrote: > > cc Juraj > > On 25 Jun 2016, at 22:28, Nicolai Hess <[email protected]> wrote: > > > > 2016-06-23 15:32 GMT+02:00 Esteban Lorenzano <[email protected]>: > >> >> > On 23 Jun 2016, at 15:29, Cyril Ferlicot Delbecque < >> [email protected]> wrote: >> > >> > >> > >> > On 23/06/2016 15:07, Christophe Demarey wrote: >> >> What happens if you execute >> >> 'SystemSettingsPersistence resumeSystemSettings’ in a 60103 image? >> >> If nothing happens, it could be that 'SystemSettingsPersistence >> >> instVarNamed: ‘alreadyResumed’’ is true >> >> >> >> I checked the startupList and PharoCommandLineHandler>>#runPreferences >> >> but nothing changed there. >> >> >> >> >> > >> > >> > I think I read something about a script esteban added to clear the >> > ever-growing stack. Couldn't it be that? Maybe it open the image and the >> >> > system setting think he already loaded the settings. >> >> no it shouldn’t… and *my* preferences are correctly loaded :) >> > > Can we please fix this. > I work a lot with fresh images, and now every time a start a new image and > trying to access a repository I have to remmember > to set the network proxy settings. > > >> >> > >> >> >> > >> > -- >> > Cyril Ferlicot >> > >> > http://www.synectique.eu >> > >> > 165 Avenue Bretagne >> > Lille 59000 France >> > >> > > > >
