Bug#1114618: FTBFS against Octave 10

[Sébastien Villemot]

Le mardi 09 septembre 2025 à 11:25 +0200, Rafael Laboissière a écrit :
> * Sébastien Villemot <sebastien at debian.org> [2025-09-09 10:20]:
> 
> > Le mardi 09 septembre 2025 à 09:39 +0200, Rafael Laboissière a écrit :
> > > * Sébastien Villemot <sebastien at debian.org> [2025-09-08 21:01]:
> > > 
> > > […]
> > > > Le lundi 08 septembre 2025 à 19:43 +0200, Sébastien Villemot a écrit :
> > > > 
> > > > Actually fixing #1061644 would fix the present FTBFS bug and all the 
> > > > similar ones.
> > > > 
> > > > Should I go ahead?
> > > 
> > > If the fix consists in adding a file to /etc/ld.so.conf.d/, like the 
> > > torsocks package does¹, I guess it will make Lintian unhappy.²
> > 
> > Yes, that would be the plan. And that would make dpkg-shlibdeps happy.
> 
> Lintian classifies the package-modifies-ld.so-search-path tag as 
> "type: error". Does this qualify the issue as release-critical?
> 
I see. So adding a drop-in file under /etc/ld.so.conf.d/ is considered
bad practice and is discouraged.

Actually there is no real need to tell the dynamic linker to look for
this additional directory, because as I said before, the .mex files are
being loaded from within Octave and liboctmex is already in memory.

So an alternative fix is just to tell dpkg-shlibdeps to stop
complaining, by passing it the -l option.

Ideally this would be done by dh-octave, so that we don’t have to
modify all individual packages, but I don’t know whether this is
possible.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  https://www.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20250909/46a04d97/attachment.sig>