public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: CU168 updater list
Date: Sun, 01 May 2022 14:17:38 +0200	[thread overview]
Message-ID: <2734ad1d-7f8b-f9a4-83e3-abdbd9a79114@ipfire.org> (raw)
In-Reply-To: <4e97f068-fd33-baba-35b3-3e9552708180@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]

Hi All,

I ran find-dependencies on libgd.so.3, the latest library to see what is linked 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 library will have problems with images. This I can confirm with my apcupsd setup which I had running. When you try and see the upsimage.cgi page then all the 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 and 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 some 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 the case.
>
>
> During CU167 Testing this was found with vnstat needed for the Net-Traffic 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.
>

  reply	other threads:[~2022-05-01 12:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 11:35 Adolf Belka
2022-05-01 12:17 ` Adolf Belka [this message]
2022-05-03 11:10   ` Michael Tremer
2022-05-03 21:14     ` Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2734ad1d-7f8b-f9a4-83e3-abdbd9a79114@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox