From: Julien Gueytat <contact@jgueytat.fr>
To: "Aníbal Limón" <anibal.limon@linux.intel.com>
Cc: 00moses.alexander00@gmail.com,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2] db: Upgrade to 6.0.35
Date: Wed, 28 Sep 2016 19:26:27 +0200 [thread overview]
Message-ID: <MADEUP.15FE20644916777A.13558@groups.io> (raw)
Alright! I'm giving you that quickly.
Sent from my WIKO RAINBOW LITE 4GLe 28 sept. 2016 18:58, Aníbal Limón <anibal.limon@linux.intel.com> a écrit :
>
>
>
> On 09/28/2016 11:30 AM, Julien Gueytat wrote:
> > Related to the db recipe. There are also the patches that needs to be
> > regenerated as the same patches are applied for the two current versions.
> > At least on Ubuntu 16.06 the same patch can't be applied anymore on the
> > two versions as the lines where to apply the patches differs too much.
>
> This is a quite strange, i'm wondering why can't be applied, i expect if
> a patch fails in configure/compile stages not at patch apply.
>
> Could you put here the error log please?
>
> alimon
>
> >
> >
> > Le 28/09/2016 18:24, Burton, Ross a écrit :
> >>
> >> On 28 September 2016 at 17:06, Aníbal Limón
> >> <anibal.limon@linux.intel.com <mailto:anibal.limon@linux.intel.com>>
> >> wrote:
> >>
> >> @@ -18,16 +18,15 @@ RCONFLICTS_${PN} = "db3"
> >> PR = "r1"
> >>
> >>
> >> Remove this PR please.
> >>
> >> # Note, when upgraded to 6.1.x, a patch in RPM will need to be
> >> removed to activate db 6.1 support.
> >> -
> >> -SRC_URI = "http://download.oracle.com/berkeley-db/db-${PV}.tar.gz
> >> <http://download.oracle.com/berkeley-db/db-$%7BPV%7D.tar.gz> \
> >> +SRC_URI = "http://distfiles.gentoo.org/distfiles/db-${PV}.tar.gz
> >> <http://distfiles.gentoo.org/distfiles/db-$%7BPV%7D.tar.gz> \
> >>
> >>
> >> What is distfiles.gentoo.org <http://distfiles.gentoo.org>'s policy
> >> when db-6.0.36 is released? Could the tarball be deleted the day
> >> after we release? In general we've been either using
> >> snapshot.debian.org <http://snapshot.debian.org> or pointing directly
> >> at the yoctoproject.org <http://yoctoproject.org> source mirror for
> >> tarballs we can't rely upon over time.
> >>
> >> Ross
> >>
> >>
> >
> >
>
next reply other threads:[~2016-09-28 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 17:26 Julien Gueytat [this message]
[not found] <20160928172641.ABBC660017@mail.openembedded.org>
2016-09-28 22:55 ` [PATCHv2] db: Upgrade to 6.0.35 Julien Gueytat
-- strict thread matches above, loose matches on Subject: below --
2016-09-28 16:06 Aníbal Limón
2016-09-28 16:24 ` Burton, Ross
2016-09-28 16:30 ` Julien Gueytat
2016-09-28 16:58 ` Aníbal Limón
2016-09-28 17:19 ` Aníbal Limón
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=MADEUP.15FE20644916777A.13558@groups.io \
--to=contact@jgueytat.fr \
--cc=00moses.alexander00@gmail.com \
--cc=anibal.limon@linux.intel.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.