From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 5ef1ee8e8a1472ad83f5c29c3aa9d8df0b22e648
Date: Sat, 24 Sep 2016 12:18:47 +0100 [thread overview]
Message-ID: <20160924111847.978211078E81@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3262 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 5ef1ee8e8a1472ad83f5c29c3aa9d8df0b22e648 (commit)
via 81b21dc0352bb05f010de1a635a1461fe9244ac6 (commit)
via 95600b77574524c3f2c788a32b128cfe68099869 (commit)
from 4eec3d94d92ca122553c5ef77797227aa56ef128 (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 5ef1ee8e8a1472ad83f5c29c3aa9d8df0b22e648
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Sep 23 23:22:13 2016 +0100
autoconf: Fix FTBFS
Requires perl Data::Dumper for build and runtime
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit 81b21dc0352bb05f010de1a635a1461fe9244ac6
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Sep 23 23:12:18 2016 +0100
autogen: Update to 5.18.12
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit 95600b77574524c3f2c788a32b128cfe68099869
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Sep 23 22:48:03 2016 +0100
beecrypt: Fix build
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
autoconf/autoconf.nm | 3 ++-
autogen/autogen.nm | 4 +++-
beecrypt/beecrypt.nm | 4 ++--
3 files changed, 7 insertions(+), 4 deletions(-)
Difference in files:
diff --git a/autoconf/autoconf.nm b/autoconf/autoconf.nm
index cb08c29..a411bf9 100644
--- a/autoconf/autoconf.nm
+++ b/autoconf/autoconf.nm
@@ -5,7 +5,7 @@
name = autoconf
version = 2.69
-release = 1
+release = 2
arch = noarch
groups = Development/Tools
@@ -27,6 +27,7 @@ build
requires
m4
perl
+ perl(Data::Dumper)
end
end
diff --git a/autogen/autogen.nm b/autogen/autogen.nm
index 90d9a32..a8d83ab 100644
--- a/autogen/autogen.nm
+++ b/autogen/autogen.nm
@@ -4,7 +4,7 @@
###############################################################################
name = autogen
-version = 5.18.1
+version = 5.18.12
release = 1
groups = Development/Tools
@@ -28,6 +28,8 @@ build
libxml2-devel
end
+ export LD_LIBRARY_PATH = %{DIR_APP}/autoopts/.libs
+
prepare_cmds
# Fix Libtool to remove rpaths.
rm -vf libtool
diff --git a/beecrypt/beecrypt.nm b/beecrypt/beecrypt.nm
index 8f3aa15..6d53a1e 100644
--- a/beecrypt/beecrypt.nm
+++ b/beecrypt/beecrypt.nm
@@ -5,7 +5,7 @@
name = beecrypt
version = 4.2.1
-release = 2
+release = 3
groups = System/Libraries
url = http://beecrypt.sourceforge.net/
@@ -31,7 +31,7 @@ build
prepare_cmds
libtoolize
- autoreconf
+ autoreconf -vfi
end
# Getting weird linking errors without --disable-threads.
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2016-09-24 11:18 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=20160924111847.978211078E81@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