All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: Fan Xin <fan.xin@jp.fujitsu.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: rpm: Recover RPM4 to OE-core
Date: Thu, 06 Oct 2016 13:42:47 +0100	[thread overview]
Message-ID: <1475757767.3146.12.camel@linux.intel.com> (raw)
In-Reply-To: <41bbea13-30ce-4d55-441c-ffdbb0f863f1@jp.fujitsu.com>

Hi Fan,

On Thu, 2016-10-06 at 20:18 +0900, Fan Xin wrote:
> By the way, could anyone give more detail info about the bugs in RPM

We removed rpm4 early this year[1] because rather than have people be
surprised that it didn't work we decided to drop support for rpm4 until
such time as the project had sufficient resources to properly maintain
it.

There were at least two issues[2][3] reported that indicated rpm4
support was incomplete, though I believe they were mostly related to
Smart's interactions with RPM 4 rather than any issue in RPM 4 itself.

It's also worth pointing out that we're strongly considering dropping
SMART in the next (2.3) development cycle[4].

Do you have a reason for wanting rpm4 beyond the proven Python3
support?

Regards,

Joshua

1. http://lists.openembedded.org/pipermail/openembedded-core/2016-March
/118849.html
2. https://bugzilla.yoctoproject.org/show_bug.cgi?id=8968
3. https://bugzilla.yoctoproject.org/show_bug.cgi?id=8969
4. https://bugzilla.yoctoproject.org/show_bug.cgi?id=9675


  reply	other threads:[~2016-10-06 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 11:18 rpm: Recover RPM4 to OE-core Fan Xin
2016-10-06 12:42 ` Joshua Lock [this message]
2016-10-07  3:19   ` Fan Xin
2016-10-07  7:20     ` Maciej Borzęcki
2016-10-07  9:52       ` Fan Xin
2016-10-07 10:39         ` Maciej Borzęcki
2016-10-07 15:52       ` Richard Purdie
2016-10-11 14:05     ` Joshua Lock

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=1475757767.3146.12.camel@linux.intel.com \
    --to=joshua.g.lock@linux.intel.com \
    --cc=fan.xin@jp.fujitsu.com \
    --cc=openembedded-core@lists.openembedded.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.