From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] rpm: Upgrade RPM to 5.4.8 (db to 5.3.15)
Date: Thu, 17 May 2012 13:49:43 -0500 [thread overview]
Message-ID: <4FB54847.5020102@windriver.com> (raw)
In-Reply-To: <CAMKF1sofgso3eS-AuwFMHh+DBhqgThi6PVDvepeyyaqQW_r7JA@mail.gmail.com>
On 5/17/12 1:27 PM, Khem Raj wrote:
> On Thu, May 17, 2012 at 11:25 AM, Mark Hatle<mark.hatle@windriver.com> wrote:
>> RPM 5.4.8 requires db 5.3.x, so both are upgraded together.
>
> is it also fine to upgrade this on existing devices ? or do databases have to be
> updated too ?
I did limited testing with this, and it was fine to upgrade on an existing
device. (I only checked on an IA32 qemux86-64 system.)
One thing I did forget to note in this message. If you are NOT using
OEBasicHash, then libzypp/zypper needs to be manually rerun. The underlying
interface for a few thing has changed and a recompile is necessary -- OE-core
doesn't realize it needs to rebuild. (OEBasicHash fixes that because it sees we
require RPM, and RPM changed, so we need to rebuild.)
--Mark
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-05-17 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 18:25 [PATCH 0/4] Uprev RPM to 5.4.9 Mark Hatle
2012-05-17 18:25 ` [PATCH 1/4] rpm: Upgrade RPM to 5.4.8 (db to 5.3.15) Mark Hatle
2012-05-17 18:27 ` Khem Raj
2012-05-17 18:49 ` Mark Hatle [this message]
2012-05-17 18:52 ` Khem Raj
2012-05-17 18:58 ` Mark Hatle
2012-05-17 18:25 ` [PATCH 2/4] rpm: Upgrade RPM to 5.4.9 Mark Hatle
2012-05-17 18:25 ` [PATCH 3/4] ossp-uuid: Add oss-uuid package and RPM 5.4.9 integration Mark Hatle
2012-05-17 18:25 ` [PATCH 4/4] package_rpm: Add capability to directly query packageorigin 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=4FB54847.5020102@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