[Debian-med-packaging] Bug#1119520: parsinsert: please build using the default build flags

[Étienne Mollier]

Control: tags -1 wontfix

Hi Emanuele,

> parsinsert is not currently using the default build flags set by dpkg-buildflags(1).
> The default flags are chosen for multiple reasons including security,
> performance, reproducibility, adherence to standards, and error handling.
> 
> Please make sure that parsinsert builds using the default build flags. blhc(1p)
> and hardening-check(1) can be used to confirm that the issue is fixed.

Thanks for your work on the topic, I was in the room when you
presented your taxonomy of packages breaking dpkg-buildflags
during DebConf25, and I enjoyed the presentation.  :)

In the particular case of parsinsert, in the past few years, we
ran into a number of difficulties, as gcc evolved and the
various options revealed a number of problems in the rather old
codebase of the package.  Digging in my archives, I noted:

  * #964082 raised issues with hardening;
  * #973789 and #976929 raised issues with optimisation flags on
    riscv64 (and mips64el);
  * #1015577 raised issues with the LTO;
  * #1037816 raised further issues with the optimiser.

parsinsert is an old package that does not benefit much from any
upstream support for more than a decade now, but still has its
uses, as far as I can see.  I believe more prudent to leave this
particular package as-is.  I'm still happy to fix other targets.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier <emollier at debian.org>
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/1, please excuse my verbosity
   `-    on air: Saga - Follow Me
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20251114/d114a255/attachment.sig>