Please do. Let's finally get rid of octave < 3.2. Tests will probably fail (bug #304963), and we have not looked yet which ones are actually valid tests, it might take a while (help welcome). But octave-3.2.4-r1 is more stable than any previous ones, so please proceed. Thanks.
Actually removing the hdf5 bug dependency since octave-3.2.4-r1 does not depend on hdf5 anymore.
Stable for HPPA.
amd64/x86 stable
octave-3.2.4-r1 solely depends on graphicsmagick, isn't that conflicting with bug #314431 ? On my system this results in several blocks with packages depending on imagemagick: ('ebuild', '/', 'media-gfx/graphicsmagick-1.3.12', 'merge') pulled in by media-gfx/graphicsmagick[cxx] required by ('ebuild', '/', 'sci-mathematics/octave-3.2.4-r1', 'merge') ('installed', '/', 'media-gfx/imagemagick-6.5.8.8', 'nomerge') pulled in by media-gfx/imagemagick required by ('installed', '/', 'media-plugins/kipi-plugins-0.8.0', 'nomerge') media-gfx/imagemagick required by ('installed', '/', 'kde-base/kopete-4.4.3', 'nomerge') media-gfx/imagemagick[png] required by ('installed', '/', 'app-editors/kile-2.1_beta4', 'nomerge') (and 4 more)
(In reply to comment #4) > octave-3.2.4-r1 solely depends on graphicsmagick, isn't that conflicting with > bug #314431 ? No. octave can not be built with imagemagick. This actually was the reason why I pushed graphicsmagick back in the tree. > On my system this results in several blocks with packages depending on > imagemagick: If you want to avoid blocks, you can add USE=-imagemagick when you build graphicsmagick. Also I am not sure these questions deal with the stability of octave.
ppc stable
alpha/sparc stable
@ppc64 Please proceed as this would fix many open bugs.
ppc64 stable