From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: CU168 updater list Date: Tue, 03 May 2022 23:14:16 +0200 Message-ID: In-Reply-To: <3C08B8DA-8D29-4DCE-B648-BE4DB9EC99D9@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5554453418379522768==" List-Id: --===============5554453418379522768== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 03/05/2022 13:10, Michael Tremer wrote: > Hello Adolf, >=20 > So when you run find-dependencies on a fresh build with the new version, yo= u are guaranteed to not find anything with the old version any more, because = it was not present at build time. The system has never seen it. >=20 > That means that everything that is now linked against the new version was p= robably linked against the old version and therefore needs to be shipped agai= n - i.e. PAK_VER needs to be incremented or it needs to be part of the core u= pdate. Then it looks likely that perl-GD should be shipped as part of the Core Updat= e 168 as GD.so is linked to libgd.so.3 so probably was linked to libgd.so.2 i= n the past.Looks safest to include this in the CU168 >=20 > It is very hard to find them all, and as much as we tried, there was occasi= onally something left which is kind of annoying, but there is no better way d= oing it than this. >=20 > -Michael >=20 >> On 1 May 2022, at 13:17, Adolf Belka wrote: >> >> Hi All, >> >> I ran find-dependencies on libgd.so.3, the latest library to see what is l= inked to it on my build system. >> >> sarg is highlighted and also icinga and apcupsd are linked to it so people= who had those addons already installed and linked with the old libgd.so.2 li= brary will have problems with images. This I can confirm with my apcupsd setu= p which I had running. When you try and see the upsimage.cgi page then all th= e coloured parts of the image that show varying amounts of charge etc are not= visible. >> >> As these are addons they need to have their PAK_VER numbers incremented to= get them to be updated. I will provide a patch to do this for sarg, icinga a= nd apcupsd >> >> >> Regards, >> >> Adolf. >> >> On 01/05/2022 13:35, Adolf Belka wrote: >>> Hi everyone, >>> >>> In CU167 the old libgd.so.2 library was removed but it turned out that so= me programs were still linked to it and not to the new libgd.so.3 library. My= bad last September when I updated gd. I mad an error with find-dependencies = and it said there was nothing still linked to the old library which was not t= he case. >>> >>> >>> During CU167 Testing this was found with vnstat needed for the Net-Traffi= c page. So vnstat was added to the updater list for CU167. >>> >>> >>> In the forum @hellfire has found that the same old library link is there = for sarg. So could sarg please be added to the CU168 updater list so that it = will update its link to the new library. >>> >>> I will try and find out if anything else is still linked to the old libgd= .so.2 library >>> >>> Sorry for the hassle. >>> >>> >>> Regards, >>> >>> Adolf. >>> >=20 --===============5554453418379522768==--