From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] RPM/upgrade fixes
Date: Thu, 10 Nov 2011 12:25:46 +0000 [thread overview]
Message-ID: <1320927946.1165.14.camel@ted> (raw)
In-Reply-To: <cover.1320839130.git.paul.eggleton@linux.intel.com>
On Wed, 2011-11-09 at 12:05 +0000, Paul Eggleton wrote:
> This is the fix for the problem Anders reported on the Yocto mailing
> list (now filed as Yocto bug #1760). I've checked through usage of
> postrm/prerm in oe-core and meta-oe and it looks OK to me, but it
> would help for others to double-check it.
>
> I considered whether or not it would be worth bumping PR on every
> recipe that uses prerm/postrm, however this is a *lot* of recipes.
>
> Also included is another fix for a minor issue I discovered when
> uninstalling busybox.
>
> The following changes since commit 25fae81538a92e15eab3fc169ebce44505f67839:
>
> python: skip setup.py 'import check' when cross-compiling (2011-11-08 21:44:23 +0000)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib paule/rmscripts
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/rmscripts
>
> Paul Eggleton (2):
> classes/package_rpm: disable uninstall scripts for upgrades
> busybox: add grep to temporary links during uninstall
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-11-10 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 12:05 [PATCH 0/2] RPM/upgrade fixes Paul Eggleton
2011-11-09 12:05 ` [PATCH 1/2] classes/package_rpm: disable uninstall scripts for upgrades Paul Eggleton
2011-11-09 18:55 ` Mark Hatle
2023-11-02 10:20 ` vadym.yatsenko
2011-11-09 12:05 ` [PATCH 2/2] busybox: add grep to temporary links during uninstall Paul Eggleton
2011-11-09 19:28 ` Paul Menzel
2011-11-10 10:07 ` Paul Eggleton
2011-11-10 12:25 ` Richard Purdie [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=1320927946.1165.14.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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