From: "Kienker, Fred" <fkienker@at4b.com>
To: development@lists.ipfire.org
Subject: RE: Suggestion: add 'jannson'-libraries
Date: Sat, 15 Jun 2019 12:07:43 -0400 [thread overview]
Message-ID: <H000006e004f5153.1560614863.mail.at4b.net@MHS> (raw)
In-Reply-To: <ba1d8dd0-f861-938a-ba03-7be8847a9893@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
These libraries are NOT optional with the current 133 build!
Upgrading an running C132 firewall system, I can duplicate this error.
Once again, commenting the 2> /dev/null saves the day. With the comment
removed, this message appears when trying to start Suricata:
/usr/bin/suricata: error while loading shared libraries:
libjansson.so.4: cannot open shared object file: No such file or
directory [ FAIL ]
Running:
find / -iname "libjansson*"
returns nothing.
Looks like a missing lib file.
Trying the suggested fix:
pakfire install jansson
PAKFIRE WARN: The pak "jansson" is not known. Please try running
"pakfire update".
PAKFIRE ERROR: No packages to install. Exiting...
Updating mine back to 132 and re-running the update did not help.
Best regards,
Fred
-----Original Message-----
From: Matthias Fischer <matthias.fischer(a)ipfire.org>
Sent: 15 June, 2019 10:20
To: IPFire: Development-List <development(a)lists.ipfire.org>
Subject: Suggestion: add 'jannson'-libraries
Hi,
did someone notice this?
=> https://forum.ipfire.org/viewtopic.php?f=5&t=22967#p125518
IMHO we should add these libraries to the Core 133 upgrade.
Opinions?
Best,
Matthias
next prev parent reply other threads:[~2019-06-15 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 14:19 Matthias Fischer
2019-06-15 16:07 ` Kienker, Fred [this message]
2019-06-15 17:00 ` Matthias Fischer
2019-06-17 7:23 ` Arne Fitzenreiter
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=H000006e004f5153.1560614863.mail.at4b.net@MHS \
--to=fkienker@at4b.com \
--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