From: Khem Raj <raj.khem@gmail.com>
To: f_l_k@t-online.de
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH 1/2] fuse3: move from meta-filesystems to meta-oe
Date: Sun, 12 May 2024 21:49:07 -0700 [thread overview]
Message-ID: <CAMKF1sqdW5a8qTQJRn+iOv1udRXNXFo1OiyTiAzisADu+8K0_g@mail.gmail.com> (raw)
In-Reply-To: <20240510054709.4044191-1-f_l_k@t-online.de>
This fails layer compatibility tests - see
https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/3853/steps/12/logs/errors
On Thu, May 9, 2024 at 10:46 PM Markus Volk via lists.openembedded.org
<f_l_k=t-online.de@lists.openembedded.org> wrote:
>
> Technically flatpak and xdg-desktop-portal have a runtime dependency on
> fuse3-utils. I was worried that adding it might cause problems with CI since fuse3
> is not included in meta-oe.
>
> Given that both packages also require fuse3 at buildtime it could be a good
> idea to move fuse3 to avoid a meta-filesystems dependency for meta-oe
>
> Signed-off-by: Markus Volk <f_l_k@t-online.de>
> ---
> .../recipes-support/fuse/fuse3/run-ptest | 0
> .../recipes-support/fuse/fuse3_3.16.2.bb | 3 +--
> 2 files changed, 1 insertion(+), 2 deletions(-)
> rename {meta-filesystems => meta-oe}/recipes-support/fuse/fuse3/run-ptest (100%)
> rename {meta-filesystems => meta-oe}/recipes-support/fuse/fuse3_3.16.2.bb (98%)
>
> diff --git a/meta-filesystems/recipes-support/fuse/fuse3/run-ptest b/meta-oe/recipes-support/fuse/fuse3/run-ptest
> similarity index 100%
> rename from meta-filesystems/recipes-support/fuse/fuse3/run-ptest
> rename to meta-oe/recipes-support/fuse/fuse3/run-ptest
> diff --git a/meta-filesystems/recipes-support/fuse/fuse3_3.16.2.bb b/meta-oe/recipes-support/fuse/fuse3_3.16.2.bb
> similarity index 98%
> rename from meta-filesystems/recipes-support/fuse/fuse3_3.16.2.bb
> rename to meta-oe/recipes-support/fuse/fuse3_3.16.2.bb
> index 2b0797a6f..307544bf3 100644
> --- a/meta-filesystems/recipes-support/fuse/fuse3_3.16.2.bb
> +++ b/meta-oe/recipes-support/fuse/fuse3_3.16.2.bb
> @@ -13,8 +13,7 @@ LIC_FILES_CHKSUM = " \
> file://LICENSE;md5=a55c12a2d7d742ecb41ca9ae0a6ddc66 \
> "
>
> -SRC_URI = "https://github.com/libfuse/libfuse/releases/download/fuse-${PV}/fuse-${PV}.tar.gz \
> -"
> +SRC_URI = "https://github.com/libfuse/libfuse/releases/download/fuse-${PV}/fuse-${PV}.tar.gz"
> SRC_URI[sha256sum] = "f797055d9296b275e981f5f62d4e32e089614fc253d1ef2985851025b8a0ce87"
>
> S = "${WORKDIR}/fuse-${PV}"
> --
> 2.44.0
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#110306): https://lists.openembedded.org/g/openembedded-devel/message/110306
> Mute This Topic: https://lists.openembedded.org/mt/106016169/1997914
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2024-05-13 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 5:47 [meta-oe][PATCH 1/2] fuse3: move from meta-filesystems to meta-oe Markus Volk
2024-05-10 5:47 ` [meta-oe][PATCH 2/2] flatpak;xdg-desktop-portal: add missing runtime dependency on fuse3-utils Markus Volk
2024-05-13 4:49 ` Khem Raj [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=CAMKF1sqdW5a8qTQJRn+iOv1udRXNXFo1OiyTiAzisADu+8K0_g@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=f_l_k@t-online.de \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).