public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Question about suricata in CU185
Date: Wed, 28 Feb 2024 17:00:11 +0000	[thread overview]
Message-ID: <09EC8D14-58B8-42E9-8336-97D6C80D17F4@ipfire.org> (raw)
In-Reply-To: <dfed9360-a927-4a66-8397-6952901a17bf@ipfire.org>

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

Thank you. All merged :)

> On 26 Feb 2024, at 08:39, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi Bailey,
> 
> On 25/02/2024 13:28, Bailey Calder wrote:
>> IPFire 2.29 (x86_64) - Core-Update 185 Development Build: next/d2991613
>> Suricata fails to start from ssh and webgui
>> [root(a)Bailey-Firewall ~]# suricata
>> suricata: error while loading shared libraries: libelf.so.1: cannot open shared object file: No such file or directory
>> is this a bug on my side or everyone else?
> Looking through the git repo I have found that elfutils has not been shipped after being changed from an addon to a core package.
> 
> I have submitted a patch to ensure that the updated elfutils is shipped in CU185.
> 
> 
> Any evaluations I have done using CU185 for evaluating bug fixes, package updates etc have all been done via a fresh install of CU185 when the updated elfutils is properly included.
> 
> Thanks for the heads up.
> 
> Regards,
> Adolf.
>> Thanks
>> Bailey


      reply	other threads:[~2024-02-28 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  8:39 Adolf Belka
2024-02-28 17:00 ` Michael Tremer [this message]

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=09EC8D14-58B8-42E9-8336-97D6C80D17F4@ipfire.org \
    --to=michael.tremer@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