[Pkg-octave-devel] Problem with

[Mike Miller]

On Wed, Sep 17, 2014 at 23:11:53 +0200, Rafael Laboissiere wrote:
> 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

Ouch, thanks for catching that. For the record, I think this is dpkg
1.17.11 changing from i486 to i586 [1]:

 dpkg (1.17.11) unstable; urgency=low
 [...]
   * Bump the i386 architecture GNU triplet to i586-linux-gnu to match the
     change in gcc. Somewhat reluctantly, as i386 wants to be its unique
     snowflake and use a GNU triplet not matching its baseline. This will
     cause problems when cross-building and using unmatched combinations of
     dpkg-dev and gcc. Closes: #751363

> 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+
>
> Of course, those packages are now buggy on i386.  What can be done in order
> to fix this problem?

Short term, a binnmu of affected packages should resolve this, right?

Long term, I'm not sure if there's a way to detect or trigger on this
to handle it automatically. Report a bug upstream so the path used in
packages is always i386 corresponding to the multiarch triplet?

[1] https://tracker.debian.org/news/562962

-- 
mike