Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Dustin Bain <dustin.bain@garmin.com>
Subject: [master/thud][PATCH] busybox: update to 1.29.3
Date: Tue,  5 Feb 2019 09:31:44 -0600	[thread overview]
Message-ID: <20190205153144.26220-1-JPEWhacker@gmail.com> (raw)

From: Dustin Bain <dustin.bain@garmin.com>

Updates busybox to version 1.29.3 to fix a bug related to parsing of
config files: 2993551ef ("Revert "libbb: remove unnecessary variable in
xmalloc_fgets"")

Upgrading the recipe was chosen instead of backporting the fix as a
patch because the only difference between version 1.29.2 and 1.29.3 is
this revert.

Signed-off-by: Dustin Bain <dustin.bain@garmin.com>
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
 .../{busybox-inittab_1.29.2.bb => busybox-inittab_1.29.3.bb}  | 0
 .../busybox/{busybox_1.29.2.bb => busybox_1.29.3.bb}          | 4 ++--
 2 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-core/busybox/{busybox-inittab_1.29.2.bb => busybox-inittab_1.29.3.bb} (100%)
 rename meta/recipes-core/busybox/{busybox_1.29.2.bb => busybox_1.29.3.bb} (91%)

diff --git a/meta/recipes-core/busybox/busybox-inittab_1.29.2.bb b/meta/recipes-core/busybox/busybox-inittab_1.29.3.bb
similarity index 100%
rename from meta/recipes-core/busybox/busybox-inittab_1.29.2.bb
rename to meta/recipes-core/busybox/busybox-inittab_1.29.3.bb
diff --git a/meta/recipes-core/busybox/busybox_1.29.2.bb b/meta/recipes-core/busybox/busybox_1.29.3.bb
similarity index 91%
rename from meta/recipes-core/busybox/busybox_1.29.2.bb
rename to meta/recipes-core/busybox/busybox_1.29.3.bb
index df3ea5906b..6064e9fdc6 100644
--- a/meta/recipes-core/busybox/busybox_1.29.2.bb
+++ b/meta/recipes-core/busybox/busybox_1.29.3.bb
@@ -44,5 +44,5 @@ SRC_URI = "http://www.busybox.net/downloads/busybox-${PV}.tar.bz2;name=tarball \
 "
 SRC_URI_append_libc-musl = " file://musl.cfg "
 
-SRC_URI[tarball.md5sum] = "46617af37a39579711d8b36f189cdf1e"
-SRC_URI[tarball.sha256sum] = "67d2fa6e147a45875fe972de62d907ef866fe784c495c363bf34756c444a5d61"
+SRC_URI[tarball.md5sum] = "0a367e19cdfd157e8258d87f893ee516"
+SRC_URI[tarball.sha256sum] = "97648636e579462296478e0218e65e4bc1e9cd69089a3b1aeb810bff7621efb7"
-- 
2.20.1



                 reply	other threads:[~2019-02-05 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190205153144.26220-1-JPEWhacker@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=dustin.bain@garmin.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