From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 20bbeabf9fee1213d36428358e455f6d31ae962f
Date: Tue, 15 Aug 2017 12:58:35 +0100 [thread overview]
Message-ID: <20170815115836.50D9C1081DE1@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3292 bytes --]
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 3.x development tree".
The branch, master has been updated
via 20bbeabf9fee1213d36428358e455f6d31ae962f (commit)
via a4f7c909d180589f0f49c6b434efc26ff6ce75f9 (commit)
from 19d051f7d8a1405e25ddee00f490b91d7b3b1b4f (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 20bbeabf9fee1213d36428358e455f6d31ae962f
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Fri Aug 11 19:51:08 2017 +0200
systemd: Update to 233
This is a major update for systemd to version 233.
* Drop support for the audit subsystem.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit a4f7c909d180589f0f49c6b434efc26ff6ce75f9
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Fri Aug 11 19:49:03 2017 +0200
glibc: Remove audit support
* Drop support for the audit subsystem.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
glibc/glibc.nm | 3 +--
systemd/systemd.nm | 11 ++++++++---
2 files changed, 9 insertions(+), 5 deletions(-)
Difference in files:
diff --git a/glibc/glibc.nm b/glibc/glibc.nm
index 5aa87d3..717c007 100644
--- a/glibc/glibc.nm
+++ b/glibc/glibc.nm
@@ -5,7 +5,7 @@
name = glibc
version = 2.26
-release = 1
+release = 2
maintainer = Michael Tremer <michael.tremer(a)ipfire.org>
groups = System/Base
@@ -31,7 +31,6 @@ build
OPTIMIZED_KERNEL = 3.2
requires
- audit-devel
autoconf
automake
binutils >= 2.27
diff --git a/systemd/systemd.nm b/systemd/systemd.nm
index 52137f9..037f783 100644
--- a/systemd/systemd.nm
+++ b/systemd/systemd.nm
@@ -4,8 +4,8 @@
###############################################################################
name = systemd
-version = 232
-release = 2
+version = 233
+release = 1
maintainer = Stefan Schantl <stefan.schantl(a)ipfire.org>
groups = System/Base
@@ -38,7 +38,6 @@ build
autoconf
automake
attr-devel
- audit-devel
cryptsetup-luks-devel >= 1.4.2
dbus-devel
docbook-utils
@@ -101,6 +100,9 @@ build
# Create dummy machine-id file, which is required for some tests.
touch %{sysconfdir}/machine-id
+ # Generate temporary machine-id, which is required at least by the id128 test.
+ systemd-machine-id-setup
+
# Run the testsuite.
make check || true
end
@@ -188,6 +190,9 @@ build
mkdir -pv %{BUILDROOT}/var/log/journal
chown root:systemd-journal %{BUILDROOT}/var/log/journal
+
+ # Create empty environment file.
+ touch %{BUILDROOT}%{sysconfdir}/environment
end
end
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2017-08-15 11:58 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=20170815115836.50D9C1081DE1@git01.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