Le mercredi 17 septembre 2014 à 23:11 +0200, Rafael Laboissiere a écrit : > I just noticed that, on i386, the canonical_host_type in Octave 3.8.2 has > changed: > > octave:1> octave_config_info ("canonical_host_type") > ans = i586-pc-linux-gnu > > This is preventing many OctaveForge packages that currently have *.oct > files installed under "i486" of working correctly, since the i486-named > directories do not get included in the path. For instance: > > $ ls -d /usr/lib/i386-linux-gnu/octave/packages/*/i486* > /usr/lib/i386-linux-gnu/octave/packages/control-2.6.5/i486-pc-linux-gnu-api-v49+ > /usr/lib/i386-linux-gnu/octave/packages/geometry-1.7.0/i486-pc-linux-gnu-api-v49+ > /usr/lib/i386-linux-gnu/octave/packages/general-1.3.4/i486-pc-linux-gnu-api-v49+ > /usr/lib/i386-linux-gnu/octave/packages/odepkg-0.8.4/i486-pc-linux-gnu-api-v49+ > /usr/lib/i386-linux-gnu/octave/packages/signal-1.3.0/i486-pc-linux-gnu-api-v49+ Thanks for noticing this. I think this is due to the following change: gcc-4.9 (4.9-20140411-1) unstable; urgency=medium * GCC 4.9.0 release candidate 1. * Configure for i586-linux-gnu on i386. -- Matthias Klose <doko@debian.org> Fri, 11 Apr 2014 19:57:07 +0200 The first version of octave that has been impacted by this change is 3.8.2-1, according to the build logs on i386. > Of course, those packages are now buggy on i386. What can be done in > order to fix this problem? I think we simply need to identify the packages that are buggy, and ask the Release Team for a binNMU of these (only on i386). -- .''`. Sébastien Villemot : :' : Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594
Attachment:
signature.asc
Description: This is a digitally signed message part