<html><head></head><body><div>Hi David and Paul,</div><div><br></div><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>Hi David,<br></div><div><br></div><div>On 20-01-2022 03:15, David Bannon wrote:<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>I don't think it's good to do these changes in Debian<br></div></blockquote><div><br></div><div>I definitely agree but evidence is that quite a lot of them are "will<br></div><div>not be fixed" upstream. I am pretty sure I can fix the real spelling<br></div><div>issues. Tedious but necessary. The "national-encoding" are much harder.<br></div><div>A small number can be fixed (IMHO) but most are use of accented<br></div><div>characters, mostly in contributor's names.<br></div></blockquote><div><br></div><div>Ack. But ironically these names will also show wrong on systems where <br></div><div>the there's skew between what the codepoint the character was entered in <br></div><div>and with which it's displayed. But I'm not going to fight this point.<br></div></blockquote><div>I personally don't care about this code page issue, as long as the file compiles.</div><div>So let's override.</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<br></div><div>UTF8 because FPC still supports many Operating Systems that does not<br></div><div>know about UTF8. And there is no appetite for munging people's names.<br></div><div>So, there is no upstream solution and, I suggest, a debian patch<br></div><div>approach may just compromise cross compilers built from the Debian<br></div><div>source so, its override or nothing !<br></div></blockquote><div><br></div><div>Override it is in my opinion. It's not worth the effort.<br></div></blockquote><div>+1</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>Hardening is a problem with some of the binaries, FPC does not ship<br></div><div>hardened binaries, if Debian wants hardening, thats a debian fix I am<br></div><div>afraid.<br></div></blockquote><div><br></div><div>Totally agree. But please don't jump through hoops here. It's good to <br></div><div>have hardening, but if unsupported upstream, it may also be an uphill <br></div><div>battle (I don't know).<br></div></blockquote><div>I think upstream would accept patches on this. I can lobby for it on the FPC developers mailing list.</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>I will pursue the things I can change upstream and perhaps start on a<br></div><div>lintian override file. I note fpc source does not include a debian<br></div><div>directory, guessing the Lazarus people (who make the FPC debs) have<br></div><div>their own process to build.<br></div></blockquote><div><br></div><div>Even if it's there, the upstream debian folder is of no relevance to us. <br></div><div>It's 100% deleted and replaced by what we have. And indeed Lazarus <br></div><div>people have a different view on how a deb should be shipped (we've had <br></div><div>some discussions/clashes in the past), so they make quite different <br></div><div>choices. Let's fix our own packaging (at least initially).</div></blockquote><div>I used to be the owner of Debian folder on FPC reposiotry.</div><div>However, since I became DD, I decided to not maintain FPC debs upstream anymore and I argued on upstream side that I can ensure Debian official packages are ready a few days after the sources are released. I think this is better as it help me focus on only one packaging.</div><div style="caret-color: rgb(46, 52, 54); color: rgb(46, 52, 54); font-family: Cantarell; font-size: 14.666666984558105px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0.4); -webkit-text-stroke-width: 0px; text-decoration: none;"><span><pre>-- <br></pre><pre>Cheers,
Abou Al Montacir</pre></span></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"></blockquote></body></html>