From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f759f35ce1256d146a868609c8bea80e0ef99474
Date: Tue, 11 Mar 2025 14:08:20 +0000 (UTC) [thread overview]
Message-ID: <4ZBwb82Mq0z2xh9@people01.haj.ipfire.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via f759f35ce1256d146a868609c8bea80e0ef99474 (commit)
from e18bef46ff6888caa7a7ef52cda032ec2464f8ae (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit f759f35ce1256d146a868609c8bea80e0ef99474
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Tue Mar 11 14:04:48 2025 +0000
sqlite: Ship /usr/lib/libsqlite3.so
Some binaries seem to be linking against libsqlite3.so (i.e. vnstatd).
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/sqlite | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/sqlite b/config/rootfiles/common/sqlite
index 074e1f685..9e28c2d2b 100644
--- a/config/rootfiles/common/sqlite
+++ b/config/rootfiles/common/sqlite
@@ -1,7 +1,7 @@
usr/bin/sqlite3
#usr/include/sqlite3.h
#usr/include/sqlite3ext.h
-#usr/lib/libsqlite3.so
+usr/lib/libsqlite3.so
usr/lib/libsqlite3.so.0
usr/lib/libsqlite3.so.3.49.1
#usr/lib/pkgconfig/sqlite3.pc
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-03-11 14:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4ZBwb82Mq0z2xh9@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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