From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: tarun@centricular.com, openembedded-core@lists.openembedded.org
Cc: sebastian@centricular.com, nirbheek@centricular.com
Subject: Re: [OE-core] [PATCH v4] gstreamer1.0-plugins-rs: add new package
Date: Wed, 08 Jul 2026 07:24:52 +0100 [thread overview]
Message-ID: <05b306c913f651de16530f8a745e7ea4ba48c2f2.camel@linuxfoundation.org> (raw)
In-Reply-To: <18C03C30DCBC1651.550146@lists.openembedded.org>
On Wed, 2026-07-08 at 07:20 +0100, Richard Purdie via lists.openembedded.org wrote:
> On Tue, 2026-07-07 at 13:47 +0530, Taruntej Kanakamalla via lists.openembedded.org wrote:
> > Adapted from an existing patch:
> > https://patchwork.yoctoproject.org/project/oe-core/patch/20220606132653.60232-5-brgl@bgdev.pl
> >
> > Update the recipe to track the latest upstream release of the official
> > GStreamer Rust plugins.
> >
> > Remove the `flavors` and `ffv1` plugins from local manifest file because
> > they depend on packages that are not published on crates.io and also they
> > are not actively maintained in the gst-plugins-rs upstream anyway.
> >
> > Unlike the other GStreamer submodules, the Rust plugins follow a
> > separate release cycle and versioning scheme. These plugins are fully
> > stable and required for a fully-featured GStreamer installation, as most
> > new features and plugins are being written in Rust. They are also shipped
> > by multiple Linux distributions such as Fedora.
>
> I put this into testing and it showed there was no maintainer entry for the new recipe:
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/111/builds/2830
>
> WARNING: gstreamer1.0-plugins-rs-0.15.3-r0 do_recipe_qa: QA Issue:
> Recipe gstreamer1.0-plugins-rs in /srv/pokybuild/yocto-worker/musl-
> qemuarm64/build/layers/openembedded-core/meta/recipes-
> multimedia/gstreamer/gstreamer1.0-plugins-rs_0.15.3.bb does not have an
> assigned maintainer. Please add an entry into
> meta/conf/distro/include/maintainers.inc. [missing-maintainer]
Sorry I missed this initially, there was also:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/4122
https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/3940
which has two failures, one with 32 bit x86 multilib failing (missing
sse?) and secondly, a packaging issue.
(as well as the maintainer issue above triggering selftest failures
too).
Cheers,
Richard
next prev parent reply other threads:[~2026-07-08 6:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 13:34 [PATCH] gstreamer1.0-plugins-rs: add new package Taruntej Kanakamalla
2026-05-12 10:30 ` [OE-core] " Mathieu Dubois-Briand
2026-05-13 7:14 ` Taruntej Kanakamalla
2026-05-12 19:28 ` Peter Kjellerstedt
2026-05-13 7:25 ` Taruntej Kanakamalla
2026-05-13 7:56 ` Peter Kjellerstedt
2026-05-24 2:02 ` Taruntej Kanakamalla
2026-05-13 7:11 ` [PATCH v2] " Taruntej Kanakamalla
2026-05-13 10:19 ` [OE-core] " Alexander Kanavin
2026-05-13 11:23 ` Nirbheek Chauhan
2026-05-13 11:45 ` Alexander Kanavin
2026-05-13 12:02 ` Nirbheek Chauhan
2026-05-13 12:15 ` Alexander Kanavin
2026-05-13 13:10 ` Nirbheek Chauhan
2026-05-24 1:51 ` Taruntej Kanakamalla
2026-05-24 1:23 ` [PATCH v3] " Taruntej Kanakamalla
2026-05-24 10:12 ` [OE-core] " Alexander Kanavin
2026-05-25 17:06 ` Peter Kjellerstedt
2026-07-07 8:21 ` Taruntej Kanakamalla
2026-05-29 13:57 ` Taruntej Kanakamalla
2026-07-07 8:17 ` [PATCH v4] " Taruntej Kanakamalla
2026-07-08 6:20 ` [OE-core] " Richard Purdie
[not found] ` <18C03C30DCBC1651.550146@lists.openembedded.org>
2026-07-08 6:24 ` Richard Purdie [this message]
2026-07-14 10:55 ` [PATCH v5 1/2] cargo_c.bbclass: pass --libdir to cargo cinstall Taruntej Kanakamalla
2026-07-14 10:55 ` [PATCH v5 2/2] gstreamer1.0-plugins-rs: add new package Taruntej Kanakamalla
2026-07-15 11:37 ` [OE-core] " Mathieu Dubois-Briand
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=05b306c913f651de16530f8a745e7ea4ba48c2f2.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=nirbheek@centricular.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sebastian@centricular.com \
--cc=tarun@centricular.com \
/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