From: "Thomas Beierlein" <tomjbe@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/hamlib/, media-libs/hamlib/files/
Date: Wed, 25 Mar 2020 14:15:23 +0000 (UTC) [thread overview]
Message-ID: <1585145710.c206ece2b4cc4b081a32850bb50af6c5ec3d73bd.tomjbe@gentoo> (raw)
commit: c206ece2b4cc4b081a32850bb50af6c5ec3d73bd
Author: Thomas Beierlein <tomjbe <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 25 14:14:44 2020 +0000
Commit: Thomas Beierlein <tomjbe <AT> gentoo <DOT> org>
CommitDate: Wed Mar 25 14:15:10 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c206ece2
media-libs/hamlib: Fix build error with -Werror=format-security
Closes: https://bugs.gentoo.org/714682
Package-Manager: Portage-2.3.94, Repoman-2.3.21
Signed-off-by: Thomas Beierlein <tomjbe <AT> gentoo.org>
media-libs/hamlib/files/hamlib-3.3-format-security.patch | 14 ++++++++++++++
media-libs/hamlib/hamlib-3.3.ebuild | 4 ++++
2 files changed, 18 insertions(+)
diff --git a/media-libs/hamlib/files/hamlib-3.3-format-security.patch b/media-libs/hamlib/files/hamlib-3.3-format-security.patch
new file mode 100644
index 00000000000..bbf2de1d17d
--- /dev/null
+++ b/media-libs/hamlib/files/hamlib-3.3-format-security.patch
@@ -0,0 +1,14 @@
+# Fixes build error with format-securety (bug #714682)
+diff --git a/tests/rotctl_parse.c b/tests/rotctl_parse.c
+index 44308cc..aab1300 100644
+--- a/tests/rotctl_parse.c
++++ b/tests/rotctl_parse.c
+@@ -1009,7 +1009,7 @@ int rotctl_parse(ROT *my_rot, FILE *fin, FILE *fout, char *argv[], int argc)
+ /* The starting position of the source string is the first
+ * character past the initial '\'.
+ */
+- snprintf(cmd_name, sizeof(cmd_name), parsed_input[0] + 1);
++ snprintf(cmd_name, sizeof(cmd_name), "%s", parsed_input[0] + 1);
+
+ /* Sanity check as valid multiple character commands consist of
+ * alpha-numeric characters and the underscore ('_') character.
diff --git a/media-libs/hamlib/hamlib-3.3.ebuild b/media-libs/hamlib/hamlib-3.3.ebuild
index 7a23ca37f1b..2cde4b103be 100644
--- a/media-libs/hamlib/hamlib-3.3.ebuild
+++ b/media-libs/hamlib/hamlib-3.3.ebuild
@@ -34,6 +34,8 @@ DEPEND=" ${RDEPEND}
REQUIRED_USE="${PYTHON_REQUIRED_USE}"
+PATCHES=( "${FILESDIR}"/hamlib-3.3-format-security.patch )
+
DOCS=(AUTHORS NEWS PLAN README README.betatester README.developer TODO)
pkg_setup() {
@@ -57,6 +59,8 @@ src_prepare() {
eautoreconf
+ eapply "${PATCHES}"
+
eapply_user
}
next reply other threads:[~2020-03-25 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 14:15 Thomas Beierlein [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-08 10:04 [gentoo-commits] repo/gentoo:master commit in: media-libs/hamlib/, media-libs/hamlib/files/ Thomas Beierlein
2025-03-23 8:44 Thomas Beierlein
2025-07-20 7:33 Thomas Beierlein
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=1585145710.c206ece2b4cc4b081a32850bb50af6c5ec3d73bd.tomjbe@gentoo \
--to=tomjbe@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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