From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 1256357967f54ea08ff01e846038cabf2a468008
Date: Sun, 03 Mar 2019 13:37:51 +0000 [thread overview]
Message-ID: <20190303133752.0382A84FDD4@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1731 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 1256357967f54ea08ff01e846038cabf2a468008 (commit)
from 2f6f3632bfe63cc283cb15feb4bae435a62b9410 (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 1256357967f54ea08ff01e846038cabf2a468008
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Sun Mar 3 10:47:17 2019 +0100
libcap-ng: Update to 0.7.9
* Re-enabled testsuite
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
libcap-ng/libcap-ng.nm | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/libcap-ng/libcap-ng.nm b/libcap-ng/libcap-ng.nm
index 54e0e20a9..ddc640d06 100644
--- a/libcap-ng/libcap-ng.nm
+++ b/libcap-ng/libcap-ng.nm
@@ -4,7 +4,7 @@
###############################################################################
name = libcap-ng
-version = 0.7.4
+version = 0.7.9
release = 1
groups = System/Libraries
@@ -25,7 +25,9 @@ build
python
end
- # The testsuite is broken by the package developers
+ test
+ make check
+ end
end
packages
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2019-03-03 13:37 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=20190303133752.0382A84FDD4@people01.i.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