From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
akuster808 <akuster808@gmail.com>,
Mark Hatle <mark.hatle@windriver.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro
Date: Wed, 16 Aug 2017 20:43:28 +0000 [thread overview]
Message-ID: <a1f52142b9d047cfb6bb85d02dec3b47@XBOX02.axis.com> (raw)
In-Reply-To: <1502891035.13978.130.camel@linuxfoundation.org>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Richard Purdie
> Sent: den 16 augusti 2017 15:44
> To: akuster808 <akuster808@gmail.com>; Mark Hatle
> <mark.hatle@windriver.com>; openembedded-core@lists.openembedded.org
> Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Subject: Re: [OE-core] [PATCH 0/6 v2] Fix RPM4 regressions based on
> Pyro
>
> On Tue, 2017-08-15 at 22:19 -0700, akuster808 wrote:
> >
> > On 08/15/2017 02:41 PM, Mark Hatle wrote:
> >
> > Are these meant for Pyro?
>
> Some of the initial pieces may be ok for pyro, the actual enablement of
> the rpm deps piece cannot be taken back though as the world will likely
> break.
>
> Cheers,
>
> Richard
Getting the fixes into Pyro has been my intention from the beginning,
as I otherwise need to carry a number of backported bbclasses and other
files in our layers, which is always a maintenance burden. The lack of
of these fixes in Pyro is the main reason we have not been able to
upgrade our distribution to Pyro yet.
I believe it will be possible to get all the changes into Pyro. The
only thing that cannot be done by default is to enable it. However,
it should be easy to make that conditional (basically the only thing
needed is to determine whether --alldeps is passed to rpmdeps or not).
Once all the changes have landed in master, I can prepare a version
for Pyro that does that.
//Peter
next prev parent reply other threads:[~2017-08-16 20:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 21:41 [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro Mark Hatle
2017-08-15 21:41 ` [PATCH 1/6 v2] rpm: Add dependencies on bash, perl and python3-core Mark Hatle
2017-08-15 21:41 ` [PATCH 2/6 v2] git: Do not install git cvsserver and git svn by default Mark Hatle
2017-08-15 21:41 ` [PATCH 3/6 v2] texinfo: Avoid a problem with a dependency on perl(Locale::gettext_xs) Mark Hatle
2017-08-15 21:41 ` [PATCH 4/6 v2] package_rpm.bbclass: Filter out unwanted file deps for nativesdk packages Mark Hatle
2017-08-15 21:41 ` [PATCH 5/6 v2] package.bbclass: Restore functionality to detect RPM dependencies Mark Hatle
2017-08-15 21:41 ` [PATCH 6/6 v2] rpm: Disable perl dependency generation Mark Hatle
2017-08-16 5:19 ` [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro akuster808
2017-08-16 13:43 ` Richard Purdie
2017-08-16 20:43 ` Peter Kjellerstedt [this message]
2017-08-16 13:34 ` Richard Purdie
2017-08-16 15:18 ` Mark Hatle
2017-08-16 15:37 ` Mark Hatle
2017-08-17 10:53 ` Alexander Kanavin
2017-08-17 13:01 ` Peter Kjellerstedt
2017-08-17 13:17 ` Alexander Kanavin
2017-08-17 14:41 ` Mark Hatle
2017-08-17 14:37 ` Mark Hatle
2017-08-16 15:32 ` ✗ patchtest: failure for Fix RPM4 regressions based on Pyro (rev2) Patchwork
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=a1f52142b9d047cfb6bb85d02dec3b47@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=akuster808@gmail.com \
--cc=mark.hatle@windriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox