Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Aníbal Limón" <anibal.limon@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Cc: jagadeesh.krishnanjanappa@caviumnetworks.com
Subject: Re: [PATCH 1/2] apt: Upgrade to 1.2.24
Date: Tue, 22 Aug 2017 11:37:03 +0100	[thread overview]
Message-ID: <1503398223.32591.81.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170821213116.26081-1-anibal.limon@linux.intel.com>

On Mon, 2017-08-21 at 16:31 -0500, Aníbal Limón wrote:
> The LIC_FILES_CHKSUM changed because the license file now has
> style changes in the text remains GPLv2+.
> 
> The patch Revert-always-run-dpkg-configure-a-at-the-end-of-our
> was updated because now the precision fields use floating
> point numbers.
> 
> Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
> ---
>  .../{apt-native_1.2.12.bb => apt-native_1.2.24.bb} |  0
>  meta/recipes-devtools/apt/apt.inc                  |  8 ++++----
>  ...ys-run-dpkg-configure-a-at-the-end-of-our.patch | 24 +++++++++++-
> ----------
>  .../apt/{apt_1.2.12.bb => apt_1.2.24.bb}           |  0
>  4 files changed, 16 insertions(+), 16 deletions(-)
>  rename meta/recipes-devtools/apt/{apt-native_1.2.12.bb => apt-
> native_1.2.24.bb} (100%)
>  rename meta/recipes-devtools/apt/{apt_1.2.12.bb => apt_1.2.24.bb}
> (100%)

https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/80/steps/BuildImages_2/logs/stdio

Cheers,

Richard



      parent reply	other threads:[~2017-08-22 10:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 21:31 [PATCH 1/2] apt: Upgrade to 1.2.24 Aníbal Limón
2017-08-21 21:31 ` [PATCH 2/2] dpkg: Upgrade to 1.18.24 Aníbal Limón
2017-08-21 21:32 ` [PATCH 1/2] apt: Upgrade to 1.2.24 Aníbal Limón
2017-08-22 10:37 ` 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=1503398223.32591.81.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=anibal.limon@linux.intel.com \
    --cc=jagadeesh.krishnanjanappa@caviumnetworks.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