From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 1b177c3e714ca5c66f90b6bf6c45aa2cea6598d3
Date: Wed, 19 Dec 2012 23:14:34 +0100 [thread overview]
Message-ID: <20121219221449.B0AD9200CF@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2541 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 1b177c3e714ca5c66f90b6bf6c45aa2cea6598d3 (commit)
via c8a7200ecc13669424880ebbbf8c30875c91f86e (commit)
from fc1c8b957e8f9e5d5330867c328e07fe6cbb8640 (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 1b177c3e714ca5c66f90b6bf6c45aa2cea6598d3
Merge: c8a7200 fc1c8b9
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Dec 19 23:14:28 2012 +0100
Merge branch 'master' of ssh://git.ipfire.org/pub/git/ipfire-3.x
commit c8a7200ecc13669424880ebbbf8c30875c91f86e
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Dec 19 23:14:01 2012 +0100
tar: Fix gets build problem.
-----------------------------------------------------------------------
Summary of changes:
.../patches/tar-1.26-stdio.in.patch | 8 ++++----
tar/tar.nm | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
copy m4/patches/m4-1.4.16-gnulib-gets.patch => tar/patches/tar-1.26-stdio.in.patch (52%)
Difference in files:
diff --git a/tar/patches/tar-1.26-stdio.in.patch b/tar/patches/tar-1.26-stdio.in.patch
new file mode 100644
index 0000000..a687592
--- /dev/null
+++ b/tar/patches/tar-1.26-stdio.in.patch
@@ -0,0 +1,13 @@
+diff -urNp tar-1.26-orig/gnu/stdio.in.h tar-1.26/gnu/stdio.in.h
+--- tar-1.26-orig/gnu/stdio.in.h
++++ tar-1.26/gnu/stdio.in.h
+@@ -139,7 +139,9 @@ _GL_WARN_ON_USE (fflush, "fflush is not
+ so any use of gets warrants an unconditional warning. Assume it is
+ always declared, since it is required by C89. */
+ #undef gets
++#if HAVE_RAW_DECL_GETS
+ _GL_WARN_ON_USE (gets, "gets is a security hole - use fgets instead");
++#endif
+
+ #if @GNULIB_FOPEN@
+ # if @REPLACE_FOPEN@
diff --git a/tar/tar.nm b/tar/tar.nm
index b582477..b260e7e 100644
--- a/tar/tar.nm
+++ b/tar/tar.nm
@@ -5,7 +5,7 @@
name = tar
version = 1.26
-release = 4
+release = 5
groups = System/Packaging
url = http://www.gnu.org/software/tar/
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-12-19 22:14 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=20121219221449.B0AD9200CF@argus.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