From: "Otavio Salvador" <otavio.salvador@ossystems.com.br>
To: Georg Hartinger <Georg.Hartinger@congatec.com>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] gstreamer-plugins-bad build error in dunfell for SABRESD platform
Date: Mon, 5 Oct 2020 09:17:15 -0300 [thread overview]
Message-ID: <CAP9ODKr3T0_hqexJ3WPnwTBKmDiN490T6wO5Az2-OY4zbHX45Q@mail.gmail.com> (raw)
In-Reply-To: <27632.1601884296214908503@lists.yoctoproject.org>
Em seg., 5 de out. de 2020 às 04:51, Georg Hartinger
<Georg.Hartinger@congatec.com> escreveu:
> > Verify using Poky (dunfell-next) as there is a queued fix for it.
>
> Same issue there
>
> > You can open there and if it is not meta-freescale specific we try to
> address and reassign.
>
> Thanks for the info. Should I open a ticket for this too?
Yes, please open it.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2020-10-05 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 9:56 [meta-freescale] gstreamer-plugins-bad build error in dunfell for SABRESD platform Georg Hartinger
2020-09-29 11:36 ` Otavio Salvador
2020-09-29 16:29 ` Georg Hartinger
2020-09-29 16:43 ` Otavio Salvador
2020-09-29 19:24 ` Georg Hartinger
2020-09-29 19:31 ` Otavio Salvador
2020-09-30 8:18 ` Georg Hartinger
2020-09-30 11:44 ` Otavio Salvador
2020-09-30 17:51 ` Georg Hartinger
2020-09-30 18:18 ` Otavio Salvador
2020-10-02 13:14 ` Georg Hartinger
2020-10-02 13:23 ` [meta-freescale] " Otavio Salvador
2020-10-05 7:51 ` Georg Hartinger
2020-10-05 12:17 ` Otavio Salvador [this message]
2020-09-29 17:06 ` [meta-freescale] " Andrey Zhizhikin
2020-09-29 19:14 ` Georg Hartinger
2020-09-30 6:32 ` Andrey Zhizhikin
-- strict thread matches above, loose matches on Subject: below --
2020-09-28 21:24 Georg Hartinger
2020-09-28 16:17 Georg Hartinger
2020-09-28 17:26 ` [meta-freescale] " Otavio Salvador
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=CAP9ODKr3T0_hqexJ3WPnwTBKmDiN490T6wO5Az2-OY4zbHX45Q@mail.gmail.com \
--to=otavio.salvador@ossystems.com.br \
--cc=Georg.Hartinger@congatec.com \
--cc=meta-freescale@lists.yoctoproject.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).