Re: scilab migration to testing (was: Unblocks for security fixes)
Le mercredi 17 novembre 2010 à 11:30 +0100, Julien Cristau a écrit :
> Helps if I actually add the cc...
> On Wed, Nov 17, 2010 at 11:27:28 +0100, Julien Cristau wrote:
> > On Tue, Nov 16, 2010 at 23:15:33 +0100, Moritz Muehlenhoff wrote:
> > > On 2010-11-15, Julien Cristau <email@example.com> wrote:
> > > >
> > > >> scilab: CVE-2010-3378, fixed in 5.2.2-8
> > > >
> > > > out of date on mips: libscilab-java, scilab, scilab-cli, scilab-data, s=
> > > > cilab-doc, scilab-doc-fr, scilab-doc-pt-br, scilab-full-bin, scilab-full-bi=
> > > > n-dbg, scilab-include, scilab-minimal-bin, scilab-minimal-bin-dbg, scilab-t=
> > > > est (from 5.2.2-2)
> > > > Updating libscilab-java fixes old bugs: #585679
> > > > scilab (source, i386, amd64, armel, ia64, kfreebsd-amd64, kfreebsd-i386=
> > > > , mips, mipsel, powerpc, s390, sparc, hppa) has new bugs!
> > > > Updating scilab introduces new bugs: #591541
> > >
> > > I suppose it should simply drop support for mips? It's not that anyone will
> > > be doing numbercrunching on mips..
> > >
> > scilab isn't getting built because libjogl-jni is missing on mips. I'm
> > guessing it's been removed when openjdk/mips was dropped, and hasn't
> > come back since it was restored? cc:ing the scilab maintainers, we need
> > some action there.
Does asking for a rebuild/reupload of libjogl-jni under mips would be
enough ? or do I need to upload a new version of jogl ?