From: Adrian Bunk <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: new meta-oe failures from master-next
Date: Thu, 24 Oct 2019 01:08:58 +0300 [thread overview]
Message-ID: <20191023220858.GB31488@localhost> (raw)
In-Reply-To: <f6b699e51c006c103b143b2f5eeddc8a34bf26fb.camel@linuxfoundation.org>
On Wed, Oct 23, 2019 at 10:20:29PM +0100, Richard Purdie wrote:
>
> Well, yes. The proposed policy is now that we should address these
> kinds of issues if they get reported. Whilst I understand why and that
> Khem doesn't get as much help as he needs with meta-oe, pushing the oe-
> core maintainers to fix things likely won't scale. I would like to see
> meta-oe quality/reliability improve though so I do understand the
> desire.
>...
What is the proposed process for oe-core changes that are likely to
break reverse dependencies in meta-oe?
Python 3.8 would be a good example for that - for astor your upgrade to
the latest upstream version already contains Python 3.8 fixes, but other
recipes in meta-oe might require fixing by someone.
> Cheers,
>
> Richard
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-10-23 22:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 13:03 new meta-oe failures from master-next Khem Raj
2019-10-23 13:05 ` Khem Raj
2019-10-23 15:58 ` akuster808
2019-10-23 15:29 ` Ross Burton
2019-10-23 19:23 ` Adrian Bunk
2019-10-23 21:20 ` Richard Purdie
2019-10-23 22:08 ` Adrian Bunk [this message]
2019-10-23 19:31 ` Richard Purdie
2019-10-23 22:52 ` Khem Raj
2019-10-24 6:37 ` Khem Raj
2019-10-24 8:15 ` richard.purdie
2019-10-24 8:20 ` Khem Raj
2019-10-24 8:25 ` richard.purdie
2019-10-24 8:34 ` Khem Raj
2019-10-24 9:34 ` richard.purdie
2019-10-24 9:34 ` Adrian Bunk
2019-10-24 9:43 ` richard.purdie
2019-10-23 16:22 ` richard.purdie
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=20191023220858.GB31488@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.