From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/3] Remove RPM 4
Date: Mon, 14 Mar 2016 14:40:29 +0000 [thread overview]
Message-ID: <1457966429.3209.9.camel@linux.intel.com> (raw)
In-Reply-To: <1457718092.2804.258.camel@linuxfoundation.org>
On Fri, 2016-03-11 at 17:41 +0000, Richard Purdie wrote:
> On Fri, 2016-03-11 at 14:07 +0000, Joshua Lock wrote:
> >
> > This series removes RPM 4 and code to support it from OE Core.
> > There
> > are
> > several known issues with using RPM 4 and it seems better to
> > acknowledge it's
> > unsupported by removing it from OE-Core than to leave it in a non
> > -functional
> > state.
> >
> > Please review the following changes for suitability for inclusion.
> > If
> > you have
> > any objections or suggestions for improvement, please respond to
> > the
> > patches. If
> > you agree with the changes, please provide your Acked-by.
> I think I'm in favour of removing it at this point as its not getting
> much attention.
>
> I'd note that we need to remove the QA test for it:
>
> selftest/imagefeatures.py: def
> test_rpm_version_4_support_on_image(self):
Right, thanks for catching this. I've pushed a patch to remove this to
the same branch, I'll submit a v2 with this removal included once the
RFC has had another day or so to collect comments.
Regards,
Joshua
prev parent reply other threads:[~2016-03-14 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 14:07 [RFC PATCH 0/3] Remove RPM 4 Joshua Lock
2016-03-11 14:07 ` [RFC PATCH 1/3] rpm: remove " Joshua Lock
2016-03-11 14:07 ` [RFC PATCH 2/3] smartpm: remove rpm4 patch Joshua Lock
2016-03-11 14:07 ` [RFC PATCH 3/3] lib/package_manager: remove RPM4 support code Joshua Lock
2016-03-11 17:41 ` [RFC PATCH 0/3] Remove RPM 4 Richard Purdie
2016-03-14 14:40 ` Joshua G Lock [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=1457966429.3209.9.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.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 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.