<html><head></head><body><div>On Sun, 2023-12-31 at 10:31 +0100, Helmut Grohne wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>On Sun, Dec 31, 2023 at 09:08:31AM +0100, Abou Al Montacir wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>So the new changes triggered more than 2.5k lintian warning.<br></div><div><a href="https://udd.debian.org/lintian/?packages=lazarus">https://udd.debian.org/lintian/?packages=lazarus</a><br></div></blockquote><div><br></div><div>Are you referring to those<br></div><div>arch-dependent-file-not-in-arch-specific-directory only?<br></div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>The issue is that Lazarus does not use the same directory structure for foreign<br></div><div>files as expected by MA.<br></div></blockquote><div><br></div><div>I'm not sure what you mean with "foreign files".<br></div></blockquote><div>I meant files from other architectures like installing arm64 object files on amd64 machine for cross compilation.</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div>The lintian tag above complains about architecture-dependent files in<br></div><div>M-A:same packages not being on fully architecture-dependent paths. For<br></div><div>example, usr/lib/lazarus/3.0/units/arm-linux/gtk2/designer.o is<br></div><div>architecture-dependent. Say you would like to co-install<br></div><div>lcl-gtk2-3.0:armel and lcl-gtk2-3.0:armhf, then both would contain this<br></div><div>file, because pascal's structure does not differentiate these.<br></div><div>Attempting to co-install them would result in an unpack error and<br></div><div>release-critical bug.<br></div></blockquote><div>Yes that was exactly what I meant.</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>This may be very hard to change, at least at short term level.<br></div></blockquote><div><br></div><div>I agree, but if you want to add M-A:same, you must. Conversely, if you<br></div><div>cannot change this, you must not use M-A:same.<br></div></blockquote><div>Makes sense.</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>Not sure if it is better to override this error for now.<br></div></blockquote><div><br></div><div>Definitely not. I said that I was unsure about M-A:same and you should<br></div><div>watch out for the hinter. Hinter results are there:<br></div><div><br></div><div> lcl-gtk2-3.0 conflicts on 611 files starting with /usr/lib/lazarus/3.0/ on armel <-> armhf<br></div><div> lcl-nogui-3.0 conflicts on 403 files starting with /usr/lib/lazarus/3.0/ on armel <-> armhf<br></div><div> lcl-qt5-3.0 conflicts on 236 files starting with /usr/lib/lazarus/3.0/ on armel <-> armhf<br></div><div> lcl-units-3.0 conflicts on 1234 files starting with /usr/lib/lazarus/3.0/ on armel <-> armhf<br></div><div><br></div><div>Adding these up gives roughly 2.5k issues, right? The hinter fully<br></div><div>agrees with lintian. You must not mark these packages M-A:same as is.<br></div></blockquote><div>I agree with you here.</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div>While removing M-A:same sounds bad, it actually is not as bad as it<br></div><div>seems. The need to coinstall these packages arises rarely. The ability<br></div><div>to perform a foreign installation is the big step. That step is moving<br></div><div>from Arch:all to Arch:any. M-A:same merely is the icing on the cake.<br></div><div>Let's have cake without icing for now.</div></blockquote><div>Yes I'll do that.</div><div><span><pre>-- <br></pre><pre>Cheers,
Abou Al Montacir
</pre></span></div></body></html>