release 3.2.1

[Jaroslav Hajek-2]

hello,

The Octave 3.2.1 semi-official tarballs are available at
http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/

We have 82 patches (mostly bug and doc fixes) since the 3.2.0 release.
I sincerely thank all contributors and testers for their valuable
work.
If your favorite bug was not fixed, don't give up hope; Octave is going on :)

John, please upload the tarballs to the GNU FTP site.

free computing, free society!

--
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

[Johannes Wolfgang Woger]

Jaroslav Hajek schrieb:

> hello,
>
> The Octave 3.2.1 semi-official tarballs are available at
> http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
>
> We have 82 patches (mostly bug and doc fixes) since the 3.2.0 release.
> I sincerely thank all contributors and testers for their valuable
> work.
> If your favorite bug was not fixed, don't give up hope; Octave is going on :)
>
> John, please upload the tarballs to the GNU FTP site.
>
> free computing, free society!
>
>  

hi,
Icould not compile octave 3.2
on opensuse 10.3, gcc 4.2.1

But it works with octave 3.2.1

Thanks
Wolfgang

 

_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

[Jaroslav Hajek-2]

On Fri, Jul 3, 2009 at 2:16 PM, Jaroslav Hajek<highegg@...> wrote:

> hello,
>
> The Octave 3.2.1 semi-official tarballs are available at
> http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
>
> We have 82 patches (mostly bug and doc fixes) since the 3.2.0 release.
> I sincerely thank all contributors and testers for their valuable
> work.
> If your favorite bug was not fixed, don't give up hope; Octave is going on :)
>
> John, please upload the tarballs to the GNU FTP site.
>
> free computing, free society!
>

OK, so hold up the fanfares; the release is flawed and should not be
used. I've removed the tarballs. See this thread:
http://www.nabble.com/Bug-in-octave-3.2.x-with-custom-atlas-multithread-td24319610.html
In short, any use of unwind_protect can cause a segfault (depending on
calling sequences).

The development version does not suffer from this problem; it's caused
by a special patch created (by me) for 3.2.x rather than transplanting
from the development version to avoid breaking ABI compatibility.

This is similar to the issue of 3.0.4 - a very serious bug was
reported very shortly after the release. Also, the bug was caused by a
patch specialized for the stable branch to avoid breaking the ABI.

Since this is the second time I've managed to produce a flawed
release, I think I'm doing a poor job as the stable branch manager,
and it's time for a change. Who wants to take on the role?

Forgive me my bitterness, but I'm really disappointed.

Sorry for all the noise. Please don't use the tarballs (if you already
downloaded them) for packages. Recent RCs also suffer from the bug;
right now I can't check which ones.

best regards

--
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

[Jaroslav Hajek-2]

On Fri, Jul 3, 2009 at 6:55 PM, Jaroslav Hajek<highegg@...> wrote:

> On Fri, Jul 3, 2009 at 2:16 PM, Jaroslav Hajek<highegg@...> wrote:
>> hello,
>>
>> The Octave 3.2.1 semi-official tarballs are available at
>> http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
>>
>> We have 82 patches (mostly bug and doc fixes) since the 3.2.0 release.
>> I sincerely thank all contributors and testers for their valuable
>> work.
>> If your favorite bug was not fixed, don't give up hope; Octave is going on :)
>>
>> John, please upload the tarballs to the GNU FTP site.
>>
>> free computing, free society!
>>
>
> OK, so hold up the fanfares; the release is flawed and should not be
> used. I've removed the tarballs. See this thread:
> http://www.nabble.com/Bug-in-octave-3.2.x-with-custom-atlas-multithread-td24319610.html
> In short, any use of unwind_protect can cause a segfault (depending on
> calling sequences).
>
> The development version does not suffer from this problem; it's caused
> by a special patch created (by me) for 3.2.x rather than transplanting
> from the development version to avoid breaking ABI compatibility.
>
> This is similar to the issue of 3.0.4 - a very serious bug was
> reported very shortly after the release. Also, the bug was caused by a
> patch specialized for the stable branch to avoid breaking the ABI.
>
> Since this is the second time I've managed to produce a flawed
> release, I think I'm doing a poor job as the stable branch manager,
> and it's time for a change. Who wants to take on the role?
>
> Forgive me my bitterness, but I'm really disappointed.
>
> Sorry for all the noise. Please don't use the tarballs (if you already
> downloaded them) for packages. Recent RCs also suffer from the bug;
> right now I can't check which ones.
>
> best regards
>

As a follow-up, I've just committed a fix to the repo; so if anyone is
interested in making the release, feel free. I won't be able to do it
for the following two weeks.

--
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

[Sergei Steshenko-2]

--- On Fri, 7/3/09, Jaroslav Hajek <highegg@...> wrote:

> From: Jaroslav Hajek <highegg@...>
> Subject: Re: release 3.2.1
> To: "Octave users list" <help-octave@...>, "octave maintainers list" <maintainers@...>
> Date: Friday, July 3, 2009, 9:55 AM
> On Fri, Jul 3, 2009 at 2:16 PM,
> Jaroslav Hajek<highegg@...>
> wrote:
> > hello,
> >
> > The Octave 3.2.1 semi-official tarballs are available
> at
> > http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
> >
> > We have 82 patches (mostly bug and doc fixes) since
> the 3.2.0 release.
> > I sincerely thank all contributors and testers for
> their valuable
> > work.
> > If your favorite bug was not fixed, don't give up
> hope; Octave is going on :)
> >
> > John, please upload the tarballs to the GNU FTP site.
> >
> > free computing, free society!
> >
>
> OK, so hold up the fanfares; the release is flawed and
> should not be
> used. I've removed the tarballs. See this thread:
> http://www.nabble.com/Bug-in-octave-3.2.x-with-custom-atlas-multithread-td24319610.html
> In short, any use of unwind_protect can cause a segfault
> (depending on
> calling sequences).
>
> The development version does not suffer from this problem;
> it's caused
> by a special patch created (by me) for 3.2.x rather than
> transplanting
> from the development version to avoid breaking ABI
> compatibility.
>
> This is similar to the issue of 3.0.4 - a very serious bug
> was
> reported very shortly after the release. Also, the bug was
> caused by a
> patch specialized for the stable branch to avoid breaking
> the ABI.
>
> Since this is the second time I've managed to produce a
> flawed
> release, I think I'm doing a poor job as the stable branch
> manager,
> and it's time for a change. Who wants to take on the role?
>
> Forgive me my bitterness, but I'm really disappointed.
>
> Sorry for all the noise. Please don't use the tarballs (if
> you already
> downloaded them) for packages. Recent RCs also suffer from
> the bug;
> right now I can't check which ones.
>
> best regards
>
> --
> RNDr. Jaroslav Hajek
> computing expert & GNU Octave developer
> Aeronautical Research and Test Institute (VZLU)
> Prague, Czech Republic
> url: www.highegg.matfyz.cz
> _______________________________________________
> Help-octave mailing list
> Help-octave@...
> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
>

Maybe it's not 3.2 to blame.

I've tried to build both 3.0.3 and 3.0.5 with atlas-3.8.3 and both I have
the same failure as the one reported in the thread.

Please note that:

1) I intentionally built single-threaded ATLAS;
2) my system is 32 (not 64 bits).

I do have another 3.0.3 built with atlas-3.8.2 and it doesn't crash.

Regards,
  Sergei.


     
_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

[Daniel J Sebald]

Jaroslav Hajek wrote:

> On Fri, Jul 3, 2009 at 2:16 PM, Jaroslav Hajek<highegg@...> wrote:
>
>>hello,
>>
>>The Octave 3.2.1 semi-official tarballs are available at
>>http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
>>
>>We have 82 patches (mostly bug and doc fixes) since the 3.2.0 release.
>>I sincerely thank all contributors and testers for their valuable
>>work.
>>If your favorite bug was not fixed, don't give up hope; Octave is going on :)
>>
>>John, please upload the tarballs to the GNU FTP site.
>>
>>free computing, free society!
>>
>
>
> OK, so hold up the fanfares; the release is flawed and should not be
> used. I've removed the tarballs. See this thread:
> http://www.nabble.com/Bug-in-octave-3.2.x-with-custom-atlas-multithread-td24319610.html
> In short, any use of unwind_protect can cause a segfault (depending on
> calling sequences).
>
> The development version does not suffer from this problem; it's caused
> by a special patch created (by me) for 3.2.x rather than transplanting
> from the development version to avoid breaking ABI compatibility.
>
> This is similar to the issue of 3.0.4 - a very serious bug was
> reported very shortly after the release. Also, the bug was caused by a
> patch specialized for the stable branch to avoid breaking the ABI.
>
> Since this is the second time I've managed to produce a flawed
> release, I think I'm doing a poor job as the stable branch manager,
> and it's time for a change. Who wants to take on the role?

I think to support the branching paradigm we need a better organized team, possibly more bug reporting / tracking tools, and some type of beta schedule.  One has to resist the desire to get new features to market ASAP, and instead set versions aside so that the whole group can test-run the version over a month.  Just let the developers site know there is a new release candidate for beta testing.  Any bugs could then be entered into a bug tracker (which we don't have) for the particular version.  Without that, one or two release versions, a developer version...and soon it is too much for any one person to keep track of.  If it were a smaller project, perhaps, but not one this size.

Also, there are certain hunks of code that are "tricky programming" and should be modified only long before a release.  unwind_protect is one of those.  Stacks, recursions, interrupts, and such have a lot of paths and conditions that are easy to overlook.

Dan
_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

[Riccardo Corradini]

Dear stuff,
I may confirm that the bug doesn't persist on octave 3.2.x using lapack 3.1.1 and linking multithread ATLAS 3.8.2 and suitesparse 3.4.0 etc..with this version 3.1.1.

clear all;
k=70
rm = rand(k,k);
im = i*rand(k,k);
M =[rm+im];

eig(M)


octave:5> bug
k =  70
ans =

   34.595137 + 35.003166i
   -2.167966 -  2..730927i
    2.683064 -  1.900657i
    1.979373 -  2.472401i
    1.178912 -  2.827986i
   -2.860170 -  1.533597i
   -1.278215 -  2.763166i
   -0.491053 -  2.941520i
    0.520176 -  2.896501i
   -2.960968 +  1.551305i
    1.474251 +  2.878508i
   -0.985561 +  3.205582i
    0.949570 +  3.136731i
    1.736646 +  2.600285i
    2.177071 +  2.136767i
   -2.328299 -  1.938764i
   -0.593303 +  3.140876i
   -3.047102 -  0.601651i
   -1.476843 +  2.605897i
   -3.054729 +  0.344304i
    2.902470 -  1.091961i
   -2.945894 +  0.033653i
   -2.188876 -  1.253901i
    0.315834 -  2.573156i
   -2.664956 -  0.268846i
   -0.446686 -  2.320919i
   -1.341214 -  1.998793i
   -1.932610 +  1.934674i
   -1.615172 -  1.720390i
   -2.349678 +  1.321243i
    2.955040 -  0.005761i
    2..745320 -  0.583099i
    2.797037 +  0.080460i
    2.282558 -  1.250512i
    2.284922 +  1.334640i
    1.750200 -  1.592420i
   -0.608666 +  2.665563i
    0..494899 +  2.678137i
    1.238442 +  2.027985i
   -1.072397 +  2.093937i
    0.284871 +  2.394743i
    1.335571 +  1.608872i
    0.899077 -  1.904376i
    0.093908 +  2.294564i
    2.129679 +  0.812796i
    2.130816 +  0.462608i
   -1.986207 +  1.122237i
    1.958445 +  0.238566i
    1.069674 -  1.486838i
    1.729207 -  0.401135i
   -1.353499 +  1.208122i
   -1.996072 -  0.015079i
   -1.261178 -  1.259285i
   -1.691011 -  0.475858i
    0.195023 +  1.601117i
   -1.258667 +  0.915337i
   -1.348994 +  0.479200i
    1.155294 -  0.633605i
    0.347096 -  1.348782i
    1.305510 +  0.084355i
   -0.432691 -  1.156473i
    0.824667 +  0.675111i
   -0..118540 +  1.016295i
   -0.644870 -  0.623766i
   -0.964274 -  0.224641i
    0.379883 +  0.686498i
    0.532738 +  0.052474i
    0.022758 -  0.474934i
   -0.391990 +  0.071362i
   -0.105894 -  0.033903i






Bests
Riccardo Corradini

--- Lun 6/7/09, Daniel J Sebald <daniel.sebald@...> ha scritto:

Da: Daniel J Sebald <daniel.sebald@...>
Oggetto: Re: release 3.2.1
A: "Jaroslav Hajek" <highegg@...>
Cc: "Octave users list" <help-octave@...>, "octave maintainers list" <maintainers@...>
Data: Lunedì 6 luglio 2009, 08:21

Jaroslav Hajek wrote:

> On Fri, Jul 3, 2009 at 2:16 PM, Jaroslav Hajek<highegg@...> wrote:
>
>>hello,
>>
>>The Octave 3.2.1 semi-official tarballs are available at
>>http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
>>
>>We have 82 patches (mostly bug and doc fixes) since the 3.2.0 release.
>>I sincerely thank all contributors and testers for their valuable
>>work.
>>If your favorite bug was not fixed, don't give up hope; Octave is going on :)
>>
>>John, please upload the tarballs to the GNU FTP site.
>>
>>free computing, free society!
>>
>
>
> OK, so hold up the fanfares; the release is flawed and should not be
> used. I've removed the tarballs. See this thread:
> http://www.nabble.com/Bug-in-octave-3.2.x-with-custom-atlas-multithread-td24319610.html
> In short, any use of unwind_protect can cause a segfault (depending on
> calling sequences).
>
> The development version does not suffer from this problem; it's caused
> by a special patch created (by me) for 3.2.x rather than transplanting
> from the development version to avoid breaking ABI compatibility.
>
> This is similar to the issue of 3.0.4 - a very serious bug was
> reported very shortly after the release. Also, the bug was caused by a
> patch specialized for the stable branch to avoid breaking the ABI.
>
> Since this is the second time I've managed to produce a flawed
> release, I think I'm doing a poor job as the stable branch manager,
> and it's time for a change. Who wants to take on the role?

I think to support the branching paradigm we need a better organized team, possibly more bug reporting / tracking tools, and some type of beta schedule.  One has to resist the desire to get new features to market ASAP, and instead set versions aside so that the whole group can test-run the version over a month.  Just let the developers site know there is a new release candidate for beta testing.  Any bugs could then be entered into a bug tracker (which we don't have) for the particular version.  Without that, one or two release versions, a developer version...and soon it is too much for any one person to keep track of.  If it were a smaller project, perhaps, but not one this size.

Also, there are certain hunks of code that are "tricky programming" and should be modified only long before a release.  unwind_protect is one of those.  Stacks, recursions, interrupts, and such have a lot of paths and conditions that are easy to overlook.

Dan

_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

[Jaroslav Hajek-2]

On Fri, Jul 3, 2009 at 7:02 PM, Jaroslav Hajek<highegg@...> wrote:

> On Fri, Jul 3, 2009 at 6:55 PM, Jaroslav Hajek<highegg@...> wrote:
>> On Fri, Jul 3, 2009 at 2:16 PM, Jaroslav Hajek<highegg@...> wrote:
>>> hello,
>>>
>>> The Octave 3.2.1 semi-official tarballs are available at
>>> http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
>>>
>>> We have 82 patches (mostly bug and doc fixes) since the 3.2.0 release.
>>> I sincerely thank all contributors and testers for their valuable
>>> work.
>>> If your favorite bug was not fixed, don't give up hope; Octave is going on :)
>>>
>>> John, please upload the tarballs to the GNU FTP site.
>>>
>>> free computing, free society!
>>>
>>
>> OK, so hold up the fanfares; the release is flawed and should not be
>> used. I've removed the tarballs. See this thread:
>> http://www.nabble.com/Bug-in-octave-3.2.x-with-custom-atlas-multithread-td24319610.html
>> In short, any use of unwind_protect can cause a segfault (depending on
>> calling sequences).
>>
>> The development version does not suffer from this problem; it's caused
>> by a special patch created (by me) for 3.2.x rather than transplanting
>> from the development version to avoid breaking ABI compatibility.
>>
>> This is similar to the issue of 3.0.4 - a very serious bug was
>> reported very shortly after the release. Also, the bug was caused by a
>> patch specialized for the stable branch to avoid breaking the ABI.
>>
>> Since this is the second time I've managed to produce a flawed
>> release, I think I'm doing a poor job as the stable branch manager,
>> and it's time for a change. Who wants to take on the role?
>>
>> Forgive me my bitterness, but I'm really disappointed.
>>
>> Sorry for all the noise. Please don't use the tarballs (if you already
>> downloaded them) for packages. Recent RCs also suffer from the bug;
>> right now I can't check which ones.
>>
>> best regards
>>
>
> As a follow-up, I've just committed a fix to the repo; so if anyone is
> interested in making the release, feel free. I won't be able to do it
> for the following two weeks.
>

Back from vacation, I created the updated tarballs.
http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/

The only patch added is the following critical fix:
http://hg.tw-math.de/release-3-2-x/rev/bcb3e85add22

Unless there are more critical bugs (I hope not), the release is ready.
John, please upload the tarballs to the official places when you have time to.

--
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

[Dmitri A. Sergatskov]

On Mon, Jul 20, 2009 at 5:54 AM, Jaroslav Hajek<highegg@...> wrote:

>
> Back from vacation, I created the updated tarballs.
> http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
>

I think it should be 3.2.2, just to avoid any possible confusion.

Dmitri.
_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

[John W. Eaton-3]

On 20-Jul-2009, Dmitri A. Sergatskov wrote:

| On Mon, Jul 20, 2009 at 5:54 AM, Jaroslav Hajek<highegg@...> wrote:
|
| >
| > Back from vacation, I created the updated tarballs.
| > http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
| >
|
| I think it should be 3.2.2, just to avoid any possible confusion.

I agree.  Even though the risk of confusion is relatively low since
the earlier 3.2.1 was never placed on the Octave or GNU sites, it
would probably be best to make this one 3.2.2.

jwe

_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

[Jaroslav Hajek-2]

On Mon, Jul 20, 2009 at 9:20 PM, John W. Eaton<jwe@...> wrote:

> On 20-Jul-2009, Dmitri A. Sergatskov wrote:
>
> | On Mon, Jul 20, 2009 at 5:54 AM, Jaroslav Hajek<highegg@...> wrote:
> |
> | >
> | > Back from vacation, I created the updated tarballs.
> | > http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
> | >
> |
> | I think it should be 3.2.2, just to avoid any possible confusion.
>
> I agree.  Even though the risk of confusion is relatively low since
> the earlier 3.2.1 was never placed on the Octave or GNU sites, it
> would probably be best to make this one 3.2.2.
>
> jwe
>

OK, I made it 3.2.2. Sigh. Another eternal tribute to a withdrawn release.

--
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz

_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave