All of lore.kernel.org
 help / color / mirror / Atom feed
From: ankur.tyagi85@gmail.com
To: openembedded-devel@lists.openembedded.org
Cc: Ankur Tyagi <ankur.tyagi85@gmail.com>,
	Khem Raj <khem.raj@oss.qualcomm.com>
Subject: [oe][meta-gnome][wrynose][PATCH 11/20] gvfs: upgrade 1.60.1 -> 1.60.2
Date: Sun, 23 Aug 2026 23:51:49 +1200	[thread overview]
Message-ID: <20260823115158.1582363-11-ankur.tyagi85@gmail.com> (raw)
In-Reply-To: <20260823115158.1582363-1-ankur.tyagi85@gmail.com>

From: Ankur Tyagi <ankur.tyagi85@gmail.com>

Changelog:
https://gitlab.gnome.org/GNOME/gvfs/-/blob/1.60.2/NEWS?ref_type=tags

Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
(cherry picked from commit fde27648517c9754f6f56187e0139780e9324345)
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
---
 .../recipes-gnome/gvfs/{gvfs_1.60.1.bb => gvfs_1.60.2.bb}       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-gnome/recipes-gnome/gvfs/{gvfs_1.60.1.bb => gvfs_1.60.2.bb} (97%)

diff --git a/meta-gnome/recipes-gnome/gvfs/gvfs_1.60.1.bb b/meta-gnome/recipes-gnome/gvfs/gvfs_1.60.2.bb
similarity index 97%
rename from meta-gnome/recipes-gnome/gvfs/gvfs_1.60.1.bb
rename to meta-gnome/recipes-gnome/gvfs/gvfs_1.60.2.bb
index 7dca3cd3b9..bdcc331712 100644
--- a/meta-gnome/recipes-gnome/gvfs/gvfs_1.60.1.bb
+++ b/meta-gnome/recipes-gnome/gvfs/gvfs_1.60.2.bb
@@ -18,7 +18,7 @@ DEPENDS += "\
 RDEPENDS:${PN} += "gsettings-desktop-schemas"
 
 SRC_URI = "https://download.gnome.org/sources/${BPN}/${@gnome_verdir("${PV}")}/${BPN}-${PV}.tar.xz;name=archive"
-SRC_URI[archive.sha256sum] = "90eaba333ab7d31a7fdeade45954a513c3661ccebbd9a138aab3fb481dfb9e40"
+SRC_URI[archive.sha256sum] = "a8d7744615a488a559302fe0cc8f418d5b44aba3c2ba2163e5a9e6f607c1be9a"
 
 ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
 


  parent reply	other threads:[~2026-08-23 11:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 11:51 [oe][meta-oe][wrynose][PATCH 1/20] thin-provisioning-tools: upgrade 1.3.1 -> 1.3.3 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-oe][wrynose][PATCH 2/20] hiredis: upgrade 1.3.0 -> 1.3.1 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-oe][wrynose][PATCH 3/20] libsdl3-image: upgrade 3.4.2 -> 3.4.4 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-oe][wrynose][PATCH 4/20] libsdl3: upgrade 3.4.4 -> 3.4.8 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-networking][wrynose][PATCH 5/20] postfix: upgrade 3.10.12 -> 3.10.13 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-networking][wrynose][PATCH 6/20] firewalld: upgrade 2.2.1 -> 2.2.3 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-gnome][wrynose][PATCH 7/20] file-roller: upgrade 44.5 -> 44.7 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-gnome][wrynose][PATCH 8/20] gnome-software: upgrade 50.0 -> 50.3 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-gnome][wrynose][PATCH 9/20] gdm: upgrade 50.1 -> 50.2 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-gnome][wrynose][PATCH 10/20] gvfs: upgrade 1.60.0 -> 1.60.1 ankur.tyagi85
2026-08-23 11:51 ` ankur.tyagi85 [this message]
2026-08-23 11:51 ` [oe][meta-python][wrynose][PATCH 12/20] python3-filelock: set CVE_PRODUCT ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-python][wrynose][PATCH 13/20] python3-web3: add CVE_PRODUCT mapping ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-python][wrynose][PATCH 14/20] python3-httplib2: correct " ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-oe][wrynose][PATCH 15/20] python3-psycopg: upgrade 3.3.3 -> 3.3.4 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-oe][wrynose][PATCH 16/20] cjose: upgrade 0.6.2.7 -> 0.6.2.8 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-webserver][wrynose][PATCH 17/20] swagger-ui: upgrade 5.32.11 -> 5.32.12 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-webserver][wrynose][PATCH 18/20] swagger-ui: upgrade 5.32.12 -> 5.32.13 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-networking][wrynose][PATCH 19/20] samba: upgrade 4.23.8 -> 4.23.11 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-webserver][wrynose][PATCH 20/20] swagger-ui: upgrade 5.32.13 -> 5.32.14 ankur.tyagi85

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=20260823115158.1582363-11-ankur.tyagi85@gmail.com \
    --to=ankur.tyagi85@gmail.com \
    --cc=khem.raj@oss.qualcomm.com \
    --cc=openembedded-devel@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.