From: skmpz <skmpz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] json-c: update to 0.16, adopt
Date: Tue, 28 Jun 2022 20:49:51 +0200 [thread overview]
Message-ID: <20220628184951.QKfzrjiLDmbOKpugzMmvD5U4OWjd6VY6fzhI1NBlk7E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37603@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
There is an updated pull request by skmpz against master on the void-packages repository
https://github.com/skmpz/void-packages json-c-0.16
https://github.com/void-linux/void-packages/pull/37603
json-c: update to 0.16, adopt
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/37603.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-json-c-0.16-37603.patch --]
[-- Type: text/x-diff, Size: 2740 bytes --]
From a83c456846bd07e8152c10f8212cbc9b906ebaef Mon Sep 17 00:00:00 2001
From: skmpz <dem.procopiou@gmail.com>
Date: Fri, 17 Jun 2022 22:04:39 +0400
Subject: [PATCH] json-c: update to 0.16, adopt
---
...1-4e9e44-Fix-read-past-end-of-buffer.patch | 24 -------------------
srcpkgs/json-c/template | 7 +++---
2 files changed, 4 insertions(+), 27 deletions(-)
delete mode 100644 srcpkgs/json-c/patches/0001-4e9e44-Fix-read-past-end-of-buffer.patch
diff --git a/srcpkgs/json-c/patches/0001-4e9e44-Fix-read-past-end-of-buffer.patch b/srcpkgs/json-c/patches/0001-4e9e44-Fix-read-past-end-of-buffer.patch
deleted file mode 100644
index bfbdce690950..000000000000
--- a/srcpkgs/json-c/patches/0001-4e9e44-Fix-read-past-end-of-buffer.patch
+++ /dev/null
@@ -1,24 +0,0 @@
-From 4e9e44e5258dee7654f74948b0dd5da39c28beec Mon Sep 17 00:00:00 2001
-From: Marc <34656315+MarcT512@users.noreply.github.com>
-Date: Fri, 7 Aug 2020 10:49:45 +0100
-Subject: [PATCH] Fix read past end of buffer
-
-Resolves https://github.com/json-c/json-c/issues/654
----
- apps/json_parse.c | 3 ++-
- 1 file changed, 2 insertions(+), 1 deletion(-)
-
-diff --git a/apps/json_parse.c b/apps/json_parse.c
-index bba4622183..72b31a860a 100644
---- a/apps/json_parse.c
-+++ b/apps/json_parse.c
-@@ -82,7 +82,8 @@ static int parseit(int fd, int (*callback)(struct json_object *))
- int parse_end = json_tokener_get_parse_end(tok);
- if (obj == NULL && jerr != json_tokener_continue)
- {
-- char *aterr = &buf[start_pos + parse_end];
-+ char *aterr = (start_pos + parse_end < sizeof(buf)) ?
-+ &buf[start_pos + parse_end] : "";
- fflush(stdout);
- int fail_offset = total_read - ret + start_pos + parse_end;
- fprintf(stderr, "Failed at offset %d: %s %c\n", fail_offset,
diff --git a/srcpkgs/json-c/template b/srcpkgs/json-c/template
index daafc44f97ac..dbbd2565a2a9 100644
--- a/srcpkgs/json-c/template
+++ b/srcpkgs/json-c/template
@@ -1,17 +1,18 @@
# Template file for 'json-c'
pkgname=json-c
-version=0.15
+version=0.16
revision=1
build_style=cmake
configure_args="-DENABLE_THREADING=ON -DBUILD_STATIC_LIBS=ON
-DENABLE_RDRAND=$(vopt_if rdrand ON OFF)"
hostmakedepends="doxygen"
short_desc="JSON implementation in C"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="skmpz <dem.procopiou@gmail.com>"
license="MIT"
homepage="https://json-c.github.io/json-c"
+changelog="https://raw.githubusercontent.com/json-c/json-c/master/ChangeLog"
distfiles="https://s3.amazonaws.com/json-c_releases/releases/${pkgname}-${version}.tar.gz"
-checksum=b8d80a1ddb718b3ba7492916237bbf86609e9709fb007e7f7d4322f02341a4c6
+checksum=8e45ac8f96ec7791eaf3bb7ee50e9c2100bbbc87b8d0f1d030c5ba8a0288d96b
CFLAGS="-Wno-error"
next prev parent reply other threads:[~2022-06-28 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 18:05 [PR PATCH] " skmpz
2022-06-28 18:26 ` [PR REVIEW] " classabbyamp
2022-06-28 18:49 ` skmpz [this message]
2022-06-28 18:52 ` [PR PATCH] [Updated] " skmpz
2022-06-30 15:11 ` [PR PATCH] [Merged]: " Duncaen
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=20220628184951.QKfzrjiLDmbOKpugzMmvD5U4OWjd6VY6fzhI1NBlk7E@z \
--to=skmpz@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).