All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex.kanavin@gmail.com>
Subject: [PATCH 03/16] glib-2.0: upgrade 2.68.3 -> 2.68.4
Date: Wed, 25 Aug 2021 13:37:51 +0200	[thread overview]
Message-ID: <20210825113804.779395-3-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20210825113804.779395-1-alex.kanavin@gmail.com>

Drop merged 0001-correctly-use-3-parameters-for-close_range.patch

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
 ...tly-use-3-parameters-for-close_range.patch | 29 -------------------
 .../glib-2.0/glib-2.0/relocate-modules.patch  |  2 +-
 ...{glib-2.0_2.68.3.bb => glib-2.0_2.68.4.bb} |  3 +-
 3 files changed, 2 insertions(+), 32 deletions(-)
 delete mode 100644 meta/recipes-core/glib-2.0/glib-2.0/0001-correctly-use-3-parameters-for-close_range.patch
 rename meta/recipes-core/glib-2.0/{glib-2.0_2.68.3.bb => glib-2.0_2.68.4.bb} (93%)

diff --git a/meta/recipes-core/glib-2.0/glib-2.0/0001-correctly-use-3-parameters-for-close_range.patch b/meta/recipes-core/glib-2.0/glib-2.0/0001-correctly-use-3-parameters-for-close_range.patch
deleted file mode 100644
index 6ff25fc535..0000000000
--- a/meta/recipes-core/glib-2.0/glib-2.0/0001-correctly-use-3-parameters-for-close_range.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-From b71117d89434db83d34bc1b981ca03d4be299576 Mon Sep 17 00:00:00 2001
-From: Khem Raj <raj.khem@gmail.com>
-Date: Thu, 8 Jul 2021 17:26:43 -0700
-Subject: [PATCH] correctly use 3 parameters for close_range
-
-libc implementation has 3 parameter e.g.
-https://www.freebsd.org/cgi/man.cgi?query=close_range&sektion=2&format=html
-
-Upstream-Status: Submitted [https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2180]
-Signed-off-by: Khem Raj <raj.khem@gmail.com>
----
- glib/gspawn.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/glib/gspawn.c b/glib/gspawn.c
-index 899647c2f..3073a10a4 100644
---- a/glib/gspawn.c
-+++ b/glib/gspawn.c
-@@ -1520,7 +1520,7 @@ safe_closefrom (int lowfd)
-    *
-    * Handle ENOSYS in case it’s supported in libc but not the kernel; if so,
-    * fall back to safe_fdwalk(). */
--  if (close_range (lowfd, G_MAXUINT) != 0 && errno == ENOSYS)
-+  if (close_range (lowfd, G_MAXUINT, 0) != 0 && errno == ENOSYS)
- #endif  /* HAVE_CLOSE_RANGE */
-   (void) safe_fdwalk (close_func, GINT_TO_POINTER (lowfd));
- #endif
---
-2.32.0
diff --git a/meta/recipes-core/glib-2.0/glib-2.0/relocate-modules.patch b/meta/recipes-core/glib-2.0/glib-2.0/relocate-modules.patch
index f34f30bb3c..846c8d62b6 100644
--- a/meta/recipes-core/glib-2.0/glib-2.0/relocate-modules.patch
+++ b/meta/recipes-core/glib-2.0/glib-2.0/relocate-modules.patch
@@ -1,4 +1,4 @@
-From e56cdb8c343dd6a6ed3b10bd54e353d633ad6158 Mon Sep 17 00:00:00 2001
+From dac2bdeea38388e069412aa27eff8f1eff0440e5 Mon Sep 17 00:00:00 2001
 From: Ross Burton <ross.burton@intel.com>
 Date: Fri, 11 Mar 2016 15:35:55 +0000
 Subject: [PATCH] glib-2.0: relocate the GIO module directory for native builds
diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.68.3.bb b/meta/recipes-core/glib-2.0/glib-2.0_2.68.4.bb
similarity index 93%
rename from meta/recipes-core/glib-2.0/glib-2.0_2.68.3.bb
rename to meta/recipes-core/glib-2.0/glib-2.0_2.68.4.bb
index c71dc81202..cd789de3c0 100644
--- a/meta/recipes-core/glib-2.0/glib-2.0_2.68.3.bb
+++ b/meta/recipes-core/glib-2.0/glib-2.0_2.68.4.bb
@@ -18,11 +18,10 @@ SRC_URI = "${GNOME_MIRROR}/glib/${SHRT_VER}/glib-${PV}.tar.xz \
            file://0001-gio-tests-resources.c-comment-out-a-build-host-only-.patch \
            file://0001-gio-tests-codegen.py-bump-timeout-to-100-seconds.patch \
            file://time-test.patch \
-           file://0001-correctly-use-3-parameters-for-close_range.patch \
            "
 SRC_URI:append:class-native = " file://relocate-modules.patch"
 
-SRC_URI[sha256sum] = "e7e1a3c20c026109c45c9ec4a31d8dcebc22e86c69486993e565817d64be3138"
+SRC_URI[sha256sum] = "62fd061d08a75492617e625a73e2c05e259f831acbb8e1f8b9c81f23f7993a3b"
 
 # Find any meson cross files in FILESPATH that are relevant for the current
 # build (using siteinfo) and add them to EXTRA_OEMESON.
-- 
2.31.1


  parent reply	other threads:[~2021-08-25 11:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 11:37 [PATCH 01/16] binutils: drop target flex/bison from build dependencies Alexander Kanavin
2021-08-25 11:37 ` [PATCH 02/16] gnu-efi: update 3.0.13 -> 3.0.14 Alexander Kanavin
2021-08-25 11:37 ` Alexander Kanavin [this message]
2021-08-25 11:37 ` [PATCH 04/16] util-linux: upgrade 2.37.1 -> 2.37.2 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 05/16] ccache: upgrade 4.3 -> 4.4 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 06/16] git: upgrade 2.32.0 -> 2.33.0 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 07/16] bind: upgrade 9.16.19 -> 9.16.20 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 08/16] bluez5: upgrade 5.60 -> 5.61 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 09/16] openssh: upgrade 8.6p1 -> 8.7p1 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 10/16] ell: upgrade 0.42 -> 0.43 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 11/16] python3-mako: upgrade 1.1.4 -> 1.1.5 Alexander Kanavin
2021-08-25 11:38 ` [PATCH 12/16] vala: upgrade 0.52.4 -> 0.52.5 Alexander Kanavin
2021-08-25 11:38 ` [PATCH 13/16] libnsl2: upgrade 1.3.0 -> 2.0.0 Alexander Kanavin
2021-08-26 17:22   ` [OE-core] " Khem Raj
2021-08-26 18:10     ` Alexander Kanavin
2021-08-25 11:38 ` [PATCH 14/16] gi-docgen: upgrade 2021.6 -> 2021.7 Alexander Kanavin
2021-08-25 11:38 ` [PATCH 15/16] json-glib: upgrade 1.6.2 -> 1.6.4 Alexander Kanavin
2021-08-25 11:38 ` [PATCH 16/16] harfbuzz: upgrade 2.8.2 -> 2.9.0 Alexander Kanavin

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=20210825113804.779395-3-alex.kanavin@gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.