connman: bump to version 1.35
PATCH 1/1 connman: bump to version 1.35
Two patches are no longer needed, remove them.
---
...ll-nftables-fix-build-with-libnftnl-1.0.7.patch | 72 ------------------
.../connman/connman/CVE-2017-12865.patch | 87 ----------------------
.../connman/{connman_1.34.bb => connman_1.35.bb} | 6 +-
3 files changed, 2 insertions(+), 163 deletions(-)
delete mode 100644 meta/recipes-connectivity/connman/connman/0001-firewall-nftables-fix-build-with-libnftnl-1.0.7.patch
delete mode 100644 meta/recipes-connectivity/connman/connman/CVE-2017-12865.patch
rename meta/recipes-connectivity/connman/{connman_1.34.bb => connman_1.35.bb} (67%)meta/recipes-connectivity/connman/connman/0001-firewall-nftables-fix-build-with-libnftnl-1.0.7.patch deleted +0 -72
@@ -1,72 +0,0 @@ -From 4058ce3186a99fd5f03350fc11a7fc8d38b6a381 Mon Sep 17 00:00:00 2001 -From: "Maxin B. John" <[email protected]> -Date: Mon, 8 May 2017 10:53:18 +0300 -Subject: [PATCH] firewall-nftables: fix build with libnftnl-1.0.7 - -We need these updates to accommodate the changes caused by the following -commit in libnftnl-1.0.7 - -commit 907a9f8e5a93f5bcd449643eb3916a656d634758 -Author: Pablo Neira Ayuso <[email protected]> -Date: Tue Dec 20 13:47:11 2016 +0100 - -src: get rid of aliases and compat - -This machinery was introduced to avoid sudden compilation breakage of -old nftables releases. With the upcoming release of 0.7 (and 0.6 which -is now 6 months old) this is not required anymore. - -Moreover, users gain nothing from older releases since they are -half-boiled and buggy. - -So let's get rid of aliases now. Bump LIBVERSION and update map file. - -Upstream-Status: Submitted - -Signed-off-by: Maxin B. John <[email protected]> ---- - src/firewall-nftables.c | 14 +++++++------- - 1 file changed, 7 insertions(+), 7 deletions(-) - -diff --git a/src/firewall-nftables.c b/src/firewall-nftables.c -index 583d1c4..83b137b 100644 ---- a/src/firewall-nftables.c -+++ b/src/firewall-nftables.c -@@ -387,9 +387,9 @@ static int add_cmp(struct nftnl_rule *rule, uint32_t sreg, uint32_t op, - if (!expr) - return -ENOMEM; - -- nftnl_expr_set_u32(expr, NFT_EXPR_CMP_SREG, sreg); -- nftnl_expr_set_u32(expr, NFT_EXPR_CMP_OP, op); -- nftnl_expr_set(expr, NFT_EXPR_CMP_DATA, data, data_len); -+ nftnl_expr_set_u32(expr, NFTNL_EXPR_CMP_SREG, sreg); -+ nftnl_expr_set_u32(expr, NFTNL_EXPR_CMP_OP, op); -+ nftnl_expr_set(expr, NFTNL_EXPR_CMP_DATA, data, data_len); - - nftnl_rule_add_expr(rule, expr); - -@@ -575,8 +575,8 @@ static int build_rule_nat(const char *address, unsigned char prefixlen, - expr = nftnl_expr_alloc("meta"); - if (!expr) - goto err; -- nftnl_expr_set_u32(expr, NFT_EXPR_META_KEY, NFT_META_OIFNAME); -- nftnl_expr_set_u32(expr, NFT_EXPR_META_DREG, NFT_REG_1); -+ nftnl_expr_set_u32(expr, NFTNL_EXPR_META_KEY, NFT_META_OIFNAME); -+ nftnl_expr_set_u32(expr, NFTNL_EXPR_META_DREG, NFT_REG_1); - nftnl_rule_add_expr(rule, expr); - err = add_cmp(rule, NFT_REG_1, NFT_CMP_EQ, interface, - strlen(interface) + 1); -@@ -677,8 +677,8 @@ static int build_rule_snat(int index, const char *address, - expr = nftnl_expr_alloc("meta"); - if (!expr) - goto err; -- nftnl_expr_set_u32(expr, NFT_EXPR_META_KEY, NFT_META_OIF); -- nftnl_expr_set_u32(expr, NFT_EXPR_META_DREG, NFT_REG_1); -+ nftnl_expr_set_u32(expr, NFTNL_EXPR_META_KEY, NFT_META_OIF); -+ nftnl_expr_set_u32(expr, NFTNL_EXPR_META_DREG, NFT_REG_1); - nftnl_rule_add_expr(rule, expr); - err = add_cmp(rule, NFT_REG_1, NFT_CMP_EQ, &index, sizeof(index)); - if (err < 0) --- -2.4.0 -
meta/recipes-connectivity/connman/connman/CVE-2017-12865.patch deleted +0 -87
87 lines not on this page · raw message
meta/recipes-connectivity/connman/connman_1.35.bb renamed from meta/recipes-connectivity/connman/connman_1.34.bb +2 -4
@@ -2,17 +2,15 @@ require connman.inc SRC_URI = "${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \ file://0001-plugin.h-Change-visibility-to-default-for-debug-symb.patch \ - file://0001-firewall-nftables-fix-build-with-libnftnl-1.0.7.patch \ file://0001-connman.service-stop-systemd-resolved-when-we-use-co.patch \ file://connman \ file://no-version-scripts.patch \ file://includes.patch \ - file://CVE-2017-12865.patch \ " SRC_URI_append_libc-musl = " file://0002-resolve-musl-does-not-implement-res_ninit.patch \ " -SRC_URI[md5sum] = "e200028702c831d5f535d20d61e608ef" -SRC_URI[sha256sum] = "a9a0808c729c1f348fc36d8cecb52d19b72bc34cb411c502608cb0e0190fc71e" +SRC_URI[md5sum] = "bae37b45ee9b3db5ec8115188f8a7652" +SRC_URI[sha256sum] = "66d7deb98371545c6e417239a9b3b3e3201c1529d08eedf40afbc859842cf2aa" RRECOMMENDS_${PN} = "connman-conf"
Signature · 1 line
2.13.6
✗ patchtest: failure for connman: bump to version 1.35
== Series Details ==
Series: connman: bump to version 1.35
Revision: 1
URL : https://patchwork.openembedded.org/series/9769/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at a17f3ec910)
If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).
---
Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
Re: ✗ patchtest: failure for connman: bump to version 1.35
Ha, this exact same patch is already in master-next. I must have missed that.
Sorry for the noise!
Daniel
Quoted 34 lines · Patchwork
== Series Details ==
Series: connman: bump to version 1.35
Revision: 1
URL : https://patchwork.openembedded.org/series/9769/
State : failure== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue Series does not apply on top of target branch [
test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently ata17f3ec910)If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).
---
Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
Re: ✗ patchtest: failure for connman: bump to version 1.35
Quoted 4 lines · On Tue, 14 Nov 2017 15:18:40 +0100 Daniel Mack <[email protected]> wrote:
Ha, this exact same patch is already in master-next. I must have missed that.
Sorry for the noise!
'patchtest' checks only stable branches, and what I can see is that this patch is already on master (From OE-Core rev: f4b9c5dba4ca0c0242284eb8148e25e89f02d988)
Quoted 46 lines
Daniel
Quoted 34 lines · Patchwork
== Series Details ==
Series: connman: bump to version 1.35
Revision: 1
URL : https://patchwork.openembedded.org/series/9769/
State : failure== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue Series does not apply on top of target branch [
test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently ata17f3ec910)If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).
---
Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oeSignature · 4 lines
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core