From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: CU168 updater list
Date: Sun, 01 May 2022 13:35:02 +0200 [thread overview]
Message-ID: <4e97f068-fd33-baba-35b3-3e9552708180@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
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.
next reply other threads:[~2022-05-01 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 11:35 Adolf Belka [this message]
2022-05-01 12:17 ` Adolf Belka
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=4e97f068-fd33-baba-35b3-3e9552708180@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