All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Mingyu < wangmy@fujitsu.com>
To: openembedded-devel@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-filesystems] [PATCH 29/29] sshfs-fuse: upgrade 3.7.3 -> 3.7.5
Date: Tue, 18 Nov 2025 17:08:46 +0800	[thread overview]
Message-ID: <20251118090846.1484-29-wangmy@fujitsu.com> (raw)
In-Reply-To: <20251118090846.1484-1-wangmy@fujitsu.com>

From: Wang Mingyu <wangmy@fujitsu.com>

03ee1f8aa0899268ec02b2f54849352df92a3a1d.patch
a1d58ae1be99571a88b8439b027abe6349b74658.patch
removed since they're included in 3.7.5

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 ...1f8aa0899268ec02b2f54849352df92a3a1d.patch | 34 -------------------
 ...8ae1be99571a88b8439b027abe6349b74658.patch | 31 -----------------
 ...shfs-fuse_3.7.3.bb => sshfs-fuse_3.7.5.bb} |  7 ++--
 3 files changed, 2 insertions(+), 70 deletions(-)
 delete mode 100644 meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/03ee1f8aa0899268ec02b2f54849352df92a3a1d.patch
 delete mode 100644 meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/a1d58ae1be99571a88b8439b027abe6349b74658.patch
 rename meta-filesystems/recipes-filesystems/sshfs-fuse/{sshfs-fuse_3.7.3.bb => sshfs-fuse_3.7.5.bb} (79%)

diff --git a/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/03ee1f8aa0899268ec02b2f54849352df92a3a1d.patch b/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/03ee1f8aa0899268ec02b2f54849352df92a3a1d.patch
deleted file mode 100644
index 63cdc57b44..0000000000
--- a/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/03ee1f8aa0899268ec02b2f54849352df92a3a1d.patch
+++ /dev/null
@@ -1,34 +0,0 @@
-From 03ee1f8aa0899268ec02b2f54849352df92a3a1d Mon Sep 17 00:00:00 2001
-From: Gabriel Staples <ercaguy@gmail.com>
-Date: Tue, 22 Dec 2020 23:33:55 -0800
-Subject: [PATCH] pytest.ini: fix test warning
-
-Warning:
-
-```
-test/util.py:99
-  sshfs/build/test/util.py:99: PytestUnknownMarkWarning: Unknown pytest.mark.uses_fuse - is this a typo?
-  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/mark.html
-    return pytest.mark.uses_fuse()
-```
-
-References for the fix:
-
-1. https://stackoverflow.com/questions/60806473/pytestunknownmarkwarning-unknown-pytest-mark-xxx-is-this-a-typo/60813297#60813297
-1. https://docs.pytest.org/en/stable/mark.html
-
-Upstream-Status: Submitted [https://github.com/libfuse/sshfs/pull/238]
-Signed-off-by: Khem Raj <raj.khem@gmail.com>
----
- test/pytest.ini | 2 ++
- 1 file changed, 2 insertions(+)
-
-diff --git a/test/pytest.ini b/test/pytest.ini
-index 95161546..7a7efed4 100644
---- a/test/pytest.ini
-+++ b/test/pytest.ini
-@@ -1,2 +1,4 @@
- [pytest]
- addopts = --verbose --assert=rewrite --tb=native -x -r a
-+markers =
-+    uses_fuse
diff --git a/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/a1d58ae1be99571a88b8439b027abe6349b74658.patch b/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/a1d58ae1be99571a88b8439b027abe6349b74658.patch
deleted file mode 100644
index e76dbd5059..0000000000
--- a/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/a1d58ae1be99571a88b8439b027abe6349b74658.patch
+++ /dev/null
@@ -1,31 +0,0 @@
-From a1d58ae1be99571a88b8439b027abe6349b74658 Mon Sep 17 00:00:00 2001
-From: Gabriel Staples <ercaguy@gmail.com>
-Date: Tue, 22 Dec 2020 23:26:40 -0800
-Subject: [PATCH] Fix deprecated warning in conftest.py
-
-```
-test/conftest.py:66
-  sshfs/build/test/conftest.py:66: PytestDeprecationWarning: @pytest.yield_fixture is deprecated.
-  Use @pytest.fixture instead; they are the same.
-    @pytest.yield_fixture(autouse=True)
-```
-
-Upstream-Status: Submitted [https://github.com/libfuse/sshfs/pull/238]
-Signed-off-by: Khem Raj <raj.khem@gmail.com>
----
- test/conftest.py | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/test/conftest.py b/test/conftest.py
-index 70cd0c62..d58d45b2 100644
---- a/test/conftest.py
-+++ b/test/conftest.py
-@@ -63,7 +63,7 @@ def register_output(self, pattern, count=1, flags=re.MULTILINE):
- # relies on tests running sequential (i.e., don't dare to use e.g. the xdist
- # plugin)
- current_capfd = None
--@pytest.yield_fixture(autouse=True)
-+@pytest.fixture(autouse=True)
- def save_cap_fixtures(request, capfd):
-     global current_capfd
-     capfd.false_positives = []
diff --git a/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse_3.7.3.bb b/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse_3.7.5.bb
similarity index 79%
rename from meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse_3.7.3.bb
rename to meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse_3.7.5.bb
index c3a00566ab..ba27bc6312 100644
--- a/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse_3.7.3.bb
+++ b/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse_3.7.5.bb
@@ -5,11 +5,8 @@ LICENSE = "GPL-2.0-only"
 DEPENDS = "glib-2.0 fuse3"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
-SRC_URI = "git://github.com/libfuse/sshfs;branch=master;protocol=https \
-           file://03ee1f8aa0899268ec02b2f54849352df92a3a1d.patch \
-           file://a1d58ae1be99571a88b8439b027abe6349b74658.patch \
-"
-SRCREV = "c91eb9a9a992f1a36c49a8e6f1146e45b5e1c8e7"
+SRC_URI = "git://github.com/libfuse/sshfs;branch=master;protocol=https;tag=sshfs-${PV}"
+SRCREV = "9e35c39ba83f54a49a9df4bf0a629f26c60cc38c"
 
 inherit meson pkgconfig ptest
 
-- 
2.43.0



      parent reply	other threads:[~2025-11-18  9:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  9:08 [oe] [meta-networking] [PATCH 01/29] corosync: upgrade 3.1.9 -> 3.1.10 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-oe] [PATCH 02/29] ctags: upgrade 6.2.20251109.0 -> 6.2.20251116.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-oe] [PATCH 03/29] drm-info: upgrade 2.8.0 -> 2.9.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-oe] [PATCH 04/29] freerdp3: upgrade 3.17.2 -> 3.18.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-oe] [PATCH 05/29] graphviz: upgrade 14.0.2 -> 14.0.4 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-networking] [PATCH 06/29] libcpr: upgrade 1.12.0 -> 1.13.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-oe] [PATCH 07/29] lprng: upgrade 3.8.C -> 3.9.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-oe] [PATCH 08/29] nano: upgrade 8.6 -> 8.7 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-networking] [PATCH 09/29] nbdkit: upgrade 1.45.12 -> 1.45.14 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-networking] [PATCH 10/29] openipmi: upgrade 2.0.36 -> 2.0.37 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-oe] [PATCH 11/29] pkcs11-helper: upgrade 1.30.0 -> 1.31.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-oe] [PATCH 12/29] pv: upgrade 1.10.0 -> 1.10.1 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 13/29] python3-alembic: upgrade 1.17.1 -> 1.17.2 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 14/29] python3-apiflask: upgrade 2.4.0 -> 3.0.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 15/29] python3-asttokens: upgrade 3.0.0 -> 3.0.1 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 16/29] python3-black: upgrade 25.9.0 -> 25.11.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 17/29] python3-cachetools: upgrade 6.2.1 -> 6.2.2 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 18/29] python3-cantools: upgrade 40.7.1 -> 41.0.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 19/29] python3-execnet: upgrade 2.1.1 -> 2.1.2 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 20/29] python3-parsimonious: upgrade 0.10.0 -> 0.11.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 21/29] python3-prettytable: upgrade 3.16.0 -> 3.17.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 22/29] python3-protobuf: upgrade 6.33.0 -> 6.33.1 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 23/29] python3-pyais: upgrade 2.13.2 -> 2.13.3 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 24/29] python3-pymongo: upgrade 4.15.3 -> 4.15.4 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 25/29] python3-snagboot: upgrade 2.4 -> 2.5 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-python] [PATCH 26/29] python3-yamlloader: upgrade 1.5.2 -> 1.6.0 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-oe] [PATCH 27/29] qcbor: upgrade 1.5.3 -> 1.6 Wang Mingyu
2025-11-18  9:08 ` [oe] [meta-oe] [PATCH 28/29] ser2net: upgrade 4.6.5 -> 4.6.6 Wang Mingyu
2025-11-18  9:08 ` Wang Mingyu [this message]

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=20251118090846.1484-29-wangmy@fujitsu.com \
    --to=wangmy@fujitsu.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.