From: Max Krummenacher <max.oss.09@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Max Krummenacher <max.krummenacher@toradex.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] libsolv: don't pick up bundled db from host rpm
Date: Fri, 19 May 2017 18:08:52 +0200 [thread overview]
Message-ID: <1495210132.3247.7.camel@gmail.com> (raw)
In-Reply-To: <CAJTo0Lbf1u7b+X6JTH-S+n+N80OSkFGcZnvoRnAKBgcqQ2q6xg@mail.gmail.com>
Am Freitag, den 19.05.2017, 16:51 +0100 schrieb Burton, Ross:
> On 19 May 2017 at 16:48, Max Krummenacher <max.oss.09@gmail.com> wrote:
>
> > +Upstream-Status: Inappropriate [oe build specific]
> >
>
> Is this really inappropriate? We're finding a bug in the build system but
> that doesn't mean we're the cause of the breakage.
Yes, I think so.
In the OE setup we have our own sysroot with a variant of rpm-devel and the build host has one in
/usr/...
I think that upstream need not assume that it is configured on a build host where it sees two
differently configured rpm development packages.
For my approach to work the bundled Berkely db must provide the function db_create_rpmdb which is
more likely to change than the filename db.h.
Max
>
> Ross
next prev parent reply other threads:[~2017-05-19 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 15:48 [PATCH v2] libsolv: don't pick up bundled db from host rpm Max Krummenacher
2017-05-19 15:51 ` Burton, Ross
2017-05-19 16:08 ` Max Krummenacher [this message]
2017-05-22 13:08 ` Alexander Kanavin
2017-05-22 21:32 ` Max Krummenacher
2017-05-23 13:10 ` Alexander Kanavin
-- strict thread matches above, loose matches on Subject: below --
2017-05-26 20:35 Max Krummenacher
2017-05-29 10:50 ` Alexander Kanavin
2017-05-29 13:00 ` Max Krummenacher
2017-05-29 13:06 ` Max Krummenacher
2017-05-29 15:54 ` Alexander Kanavin
2017-05-29 23:11 ` Richard Purdie
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=1495210132.3247.7.camel@gmail.com \
--to=max.oss.09@gmail.com \
--cc=max.krummenacher@toradex.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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