public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 11/15] mpg123: update to 1.23.6
Date: Mon, 29 Aug 2016 17:30:18 +0300	[thread overview]
Message-ID: <02c110b33ac689aba599c5f7ab726ac633c69d80.1472480768.git.alexander.kanavin@linux.intel.com> (raw)
In-Reply-To: <cover.1472480768.git.alexander.kanavin@linux.intel.com>
In-Reply-To: <cover.1472480768.git.alexander.kanavin@linux.intel.com>

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/recipes-multimedia/mpg123/{mpg123_1.23.5.bb => mpg123_1.23.6.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-multimedia/mpg123/{mpg123_1.23.5.bb => mpg123_1.23.6.bb} (95%)

diff --git a/meta/recipes-multimedia/mpg123/mpg123_1.23.5.bb b/meta/recipes-multimedia/mpg123/mpg123_1.23.6.bb
similarity index 95%
rename from meta/recipes-multimedia/mpg123/mpg123_1.23.5.bb
rename to meta/recipes-multimedia/mpg123/mpg123_1.23.6.bb
index dd510c0..6ee457d 100644
--- a/meta/recipes-multimedia/mpg123/mpg123_1.23.5.bb
+++ b/meta/recipes-multimedia/mpg123/mpg123_1.23.6.bb
@@ -12,8 +12,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=1e86753638d3cf2512528b99079bc4f3"
 
 SRC_URI = "https://www.mpg123.de/download/${BP}.tar.bz2"
 
-SRC_URI[md5sum] = "6a318579dd7b52c5851bb7950af969ac"
-SRC_URI[sha256sum] = "b658df672813511ff9b68a1553917220b675067204cdb58dbb59a2b8179350b2"
+SRC_URI[md5sum] = "ed22a3e664f076fa05131a3454ef8166"
+SRC_URI[sha256sum] = "4073d9c60a43872f6f5a3a322f5ea21ab7f0869d2ed25e79c3eb8521fa3c32d4"
 
 inherit autotools pkgconfig
 
-- 
2.9.3



  parent reply	other threads:[~2016-08-29 14:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 14:30 [PATCH 00/15] Version updates and webkitgtk build race fix Alexander Kanavin
2016-08-29 14:30 ` [PATCH 01/15] libwebp: upgrade to 0.5.1 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 02/15] btrfs-tools: update to 4.7.1 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 03/15] iso-codes: upgrade to 3.69 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 04/15] bash-completion: update to 2.4 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 05/15] bdwgc: update to 7.6.0 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 06/15] ffmpeg: update to 3.1.2 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 07/15] gobject-introspection: odd versions are development snapshots Alexander Kanavin
2016-08-29 14:30 ` [PATCH 08/15] gnutls: update to 3.5.3 Alexander Kanavin
2016-08-30 22:43   ` Richard Purdie
2016-08-31  8:50   ` [PATCHv2 " Jussi Kukkonen
2016-08-29 14:30 ` [PATCH 09/15] kexec-tools: update to 2.0.13 Alexander Kanavin
2016-08-31  6:57   ` Robert Yang
2016-08-29 14:30 ` [PATCH 10/15] lighttpd: update to 1.4.41 Alexander Kanavin
2016-08-29 14:30 ` Alexander Kanavin [this message]
2016-08-29 14:30 ` [PATCH 12/15] nss: update to 3.25 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 13/15] asciidoc: fix upstream version check Alexander Kanavin
2016-08-29 14:30 ` [PATCH 14/15] webkitgtk: upgrade to 2.12.4 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 15/15] webkitgtk: fix racy double build of WebKit2-4.0.gir Alexander Kanavin

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=02c110b33ac689aba599c5f7ab726ac633c69d80.1472480768.git.alexander.kanavin@linux.intel.com \
    --to=alexander.kanavin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox