From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 15/17] libdumpvalue-perl: Update to 1.17
Date: Sun, 18 Nov 2012 21:54:48 -0800 [thread overview]
Message-ID: <e58135a86e675c2ed3ab072febca45752efaa45e.1353304234.git.sgw@linux.intel.com> (raw)
In-Reply-To: <cover.1353304234.git.sgw@linux.intel.com>
In-Reply-To: <cover.1353304234.git.sgw@linux.intel.com>
LICENSE file updated Copyright year to 2012, no other change
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
...alue-perl_1.16.bb => libdumpvalue-perl_1.17.bb} | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-lsb4/perl/{libdumpvalue-perl_1.16.bb => libdumpvalue-perl_1.17.bb} (65%)
diff --git a/meta/recipes-lsb4/perl/libdumpvalue-perl_1.16.bb b/meta/recipes-lsb4/perl/libdumpvalue-perl_1.17.bb
similarity index 65%
rename from meta/recipes-lsb4/perl/libdumpvalue-perl_1.16.bb
rename to meta/recipes-lsb4/perl/libdumpvalue-perl_1.17.bb
index 8476b94..148950f 100644
--- a/meta/recipes-lsb4/perl/libdumpvalue-perl_1.16.bb
+++ b/meta/recipes-lsb4/perl/libdumpvalue-perl_1.17.bb
@@ -6,12 +6,12 @@ SECTION = "libs"
LICENSE = "Artistic-1.0 | GPL-1.0+"
PR = "r0"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=31013c0a67276e1ca20f358868cf99ab"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=f736bec5ada1fc5e39b2a8e7e06bbcbb"
SRC_URI = "http://search.cpan.org/CPAN/authors/id/F/FL/FLORA/Dumpvalue-${PV}.tar.gz"
-SRC_URI[md5sum] = "bef29bf25717db250929bf2b065c4183"
-SRC_URI[sha256sum] = "8204ea8f95dc6b137e225702e9bacaa23646ffa8c1c9eef45fa06a7f19f338f2"
+SRC_URI[md5sum] = "6ede9f693d4a9c4555541cb1a1cc2006"
+SRC_URI[sha256sum] = "9ea74606b545f769a787ec2ae229549a2ad0a8e3cd4b14eff2ce3841836b3bdb"
S = "${WORKDIR}/Dumpvalue-${PV}"
--
1.7.7.6
next prev parent reply other threads:[~2012-11-19 6:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 5:54 [PATCH 00/17] Recipe Updates Saul Wold
2012-11-19 5:54 ` [PATCH 01/17] sysstat: Update to 10.1.2 Saul Wold
2012-11-19 5:54 ` [PATCH 02/17] libcheck: Update to 0.9.9 Saul Wold
2012-11-19 5:54 ` [PATCH 03/17] sqlite3: Update to 3.7.14.1 Saul Wold
2012-11-19 5:54 ` [PATCH 04/17] builder: Add password for user Saul Wold
2012-11-19 5:54 ` [PATCH 05/17] libtasn1: Update to 2.14 Saul Wold
2012-11-19 5:54 ` [PATCH 06/17] gnutls: Update to 2.12.21 Saul Wold
2012-11-19 5:54 ` [PATCH 07/17] libksba: Update to 1.3.0 Saul Wold
2012-11-19 5:54 ` [PATCH 08/17] dhcp: Update to 4.2.4-P2 Saul Wold
2012-11-19 5:54 ` [PATCH 09/17] libxml2: Update to 2.9.0 Saul Wold
2012-11-19 5:54 ` [PATCH 10/17] resolvconf: Update to 1.68 Saul Wold
2012-11-19 5:54 ` [PATCH 11/17] mc: Update to 4.8.6 Saul Wold
2012-11-19 5:54 ` [PATCH 12/17] man-pages: Update to 3.44 Saul Wold
2012-11-19 5:54 ` [PATCH 13/17] tiff: Update to 4.0.3 Saul Wold
2012-11-19 5:54 ` [PATCH 14/17] rt-tests/hwlatdetect: Update to 0.84 Saul Wold
2012-11-19 10:26 ` Otavio Salvador
2012-11-19 5:54 ` Saul Wold [this message]
2012-11-19 5:54 ` [PATCH 16/17] cmake: Update to 2.8.10.1 Saul Wold
2012-11-19 10:20 ` Otavio Salvador
2012-11-19 18:12 ` Saul Wold
2012-11-19 18:34 ` Otavio Salvador
2012-11-19 5:54 ` [PATCH 17/17] libproxy: set LIBEXEC_INSTALL_DIR Saul Wold
2012-11-19 10:29 ` Otavio Salvador
2012-11-19 10:31 ` [PATCH 00/17] Recipe Updates Otavio Salvador
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=e58135a86e675c2ed3ab072febca45752efaa45e.1353304234.git.sgw@linux.intel.com \
--to=sgw@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