<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>On Thu, 2022-01-20 at 08:54 +0100, Paul Gevers wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>The FPC devs are unwilling to see the ISO-8859-xx files converted to</div></blockquote><div><br></div><div>Override it is in my opinion. It's not worth the effort.</div></blockquote><div>Noted.</div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Hardening is a problem with some of the binaries, </div></blockquote></blockquote><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div>Totally agree. But please don't jump through hoops here. It's good to </div><div>have hardening, but if unsupported upstream, it may also be an uphill </div><div>battle (I don't know).</div></blockquote><div>No, generally FPC supports hardening, there is an issue on PPC64el and I have logged a bug report and its agreed it "will be fixed". But the warnings under discussion are about amd64 and FPC does do hardening there. As long as its a dynamically linked binary and that is an issue sometimes. Some of those utility binaries may well be small static ones and they will not harden (because code is not relocatable). So, thats fixable at the Debian end IMHO.</div><div><br></div><div>Its likely a future release of FPC will again do hardening correctly on PPC64el too.</div><div><br></div><div><br></div><div><div>On Thu, 2022-01-20 at 21:16 +0100, Abou Al Montacir wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><br></blockquote></div><div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>......</div><div>Then there are the tedious issues of the spelling. I think these can be forwarded via the upstream gitlab tracking tool, maybe pull requests.</div></blockquote><br>OK, I will put together some pull requests addressing just the the spelling issues. One by one I am afraid. Will be a slow process but eventually it will work its way to you. So, don't bother overriding spelling.</div><div><br><br><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div>Finally national encoding we can just hide.</div></blockquote><br></div><div>I will try for a some of these too. Good chance they will fail so assume override for now. Might mean later we (ie you) need be removed it but so be it.</div><div><br></div><div>Davo</div><div><br></div><div><br></div></body></html>