Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] RPM changes
Date: Fri, 9 Aug 2013 17:51:28 -0500	[thread overview]
Message-ID: <1376088690-24013-1-git-send-email-mark.hatle@windriver.com> (raw)

We first to a long overdue cleanup and change the RPM_VENDOR_POKY to
RPM_VENDOR_OE.  Then we fix a bug with older RPM packages that has been
found when attempting to install some of the LSB test packages.

The change was verified by <corneliux.stoicescu@intel.com> who reported
the issue to me.

Mark Hatle (2):
  rpm: Change references from RPM_VENDOR_POKY to RPM_VENDOR_OE
  rpm: Enable compatibility with older RPM packages that have invalid
    platforms

 .../rpm/rpm/python-rpm-rpmsense.patch              |  4 ++--
 .../rpm/rpm/rpm-lsb-compatibility.patch            | 24 ++++++++++++++++++++++
 meta/recipes-devtools/rpm/rpm/rpm-no-loopmsg.patch |  2 +-
 .../rpm/rpm/rpm-platform-file-fix.patch            |  2 +-
 meta/recipes-devtools/rpm/rpm/rpm-platform.patch   |  8 ++++----
 meta/recipes-devtools/rpm/rpm/rpm-platform2.patch  |  6 +++---
 .../rpm/rpm/rpm-scriptletexechelper.patch          | 22 ++++++++++----------
 meta/recipes-devtools/rpm/rpm_5.4.9.bb             |  3 ++-
 8 files changed, 48 insertions(+), 23 deletions(-)
 create mode 100644 meta/recipes-devtools/rpm/rpm/rpm-lsb-compatibility.patch

-- 
1.8.3



             reply	other threads:[~2013-08-09 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 22:51 Mark Hatle [this message]
2013-08-09 22:51 ` [PATCH 1/2] rpm: Change references from RPM_VENDOR_POKY to RPM_VENDOR_OE Mark Hatle
2013-08-09 22:51 ` [PATCH 2/2] rpm: Enable compatibility with older RPM packages that have invalid platforms Mark Hatle

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=1376088690-24013-1-git-send-email-mark.hatle@windriver.com \
    --to=mark.hatle@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox