<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>Hi Abou, this is the Lazarus Version number problem in Bullseye.</div><div><br></div><div>On Tue, 2021-11-30 at 09:02 +0100, Abou Al Montacir wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Hi David,</div><div><br></div><div>On Tue, 2021-11-30 at 10:42 +1100, David Bannon wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>In bullseye, the source has a different version number than the package and those version numbers are checked as Lazarus starts up and looks in its config files. It sees a different number and issues some warnings because thats normally a bad situation.</div></blockquote><div>Do you mean that supplied lazarus-src-2.0 provides a wrong version.inc?</div></blockquote><div><br></div><div>You change the version.inc version number during the packaging process. The issue is that it you have rev'ed the package number for extra builds at some stage without also rev'ing the number in version.inc.</div><div><br></div><div>To be specific, version.inc now has "2.0.10_dfsg-4" and the package gets an additional "+b2". These version numbers are embedded in Lazarus config files at startup. Lazarus IDE checks that its version agrees with what it finds in the config files. If they don't match, you get warnings of impending doom. Every time you start the IDE.</div><div><br></div><div>Further, if you install a package, perhaps as a tool to use in the ide or a "library" to use in your application, Lazarus always rebuilds itself. That triggers rounds of 'upgrade' and 'downgrade' warnings and changes to the config files. And then more warnings ...</div><div><br></div><div>Lazarus users are always rebuilding the IDE.</div><div><br></div><div>These issues do not stop you from using the product but they sure do not inspire you to trust it ! The only way to stop the cycle is to manually edit the version.inc file, adding the "+b2" so it matches the package version. Experienced users will do so without hesitation, beginners will panic. Frankly, I cannot workout how the IDE gets to know the package version !</div><div><br></div><div>You have fixed this IIRC in Testing so you must understand the process far better than I ?</div><div><br></div><div>Davo </div><pre><br></pre></body></html>