----- Original Message ----- > From: Marco Atzeri > To: cygwin@cygwin.com > Cc: > Date: 2016/7/17, Sun 13:25 > Subject: Re: [ANNOUNCEMENT] Re: Updated: octave-4.0.3-1 > > On 17/07/2016 04:23, Tatsuro MATSUOKA wrote: >>> From: Marco Atzeri >>> To: cygwin@cygwin.com >>> Cc: >>> Date: 2016/7/14, Thu 04:35 >>> Subject: [ANNOUNCEMENT] Re: Updated: octave-4.0.3-1 >>> >>> I just found a serious bug on 4.0.3. >>> >>> The forge package previously built with 4.0.1 don't >>> load with 4.0.3-1. >>> >>> I am investigating, but likely I will retire the current >>> 4.0.3-1 in short term. >>> >>> Sorry for the inconvenience, never happened before. >>> One thing more to test the next time. >>> >>> Regards >>> Marco >>> > >> On my cywin setup setup-x86_64.exe (downloaded today), I can only select > octave-4.0.1. >> I changed the download site but no success. >> Tatsuro >> > > Hi Tatsuro, > I retired it. > > The bug is too serious to leave the 4.0.3-1 build with > all the forge packages built before with 4.0.0 and 4.0.1 unusable. > > Have you checked if your windows build suffer the same problem ? > > http://lists.gnu.org/archive/html/octave-maintainers/2016-07/msg00246.html > > I received no feedback on the development list. > > Regards > Marco I understand the situation. Thanks! For octave-4.0.3 on native windows, I have built octave-forge packages for 64 windows binary using build_package.m script on octave 4.0.3 for windows. I do not know whether I can use packages that are built agaist the previous version. Tatsuro
-- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
