Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/10] Recipe version updates
Date: Wed,  9 Dec 2015 16:40:20 +0200	[thread overview]
Message-ID: <cover.1449671297.git.alexander.kanavin@linux.intel.com> (raw)

This patchset contains various version updates and upstream check updates for
recipes with Unknown upstream status. I wanted to handle those before updating
out-of-date recipes where upstream version is known (which I'll be dong next).

The following changes since commit 7e8ff7b9d793b7be106415c3c80b687977217566:

  bitbake: toaster: toasterui Add ParseStarted/ParseProgress events to mask (2015-12-09 09:03:35 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib akanavin/package-version-updates
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/package-version-updates

Alexander Kanavin (10):
  openssl: update to 1.0.2e
  gnutls: update to 3.4.7
  python-setuptools: update to 18.7.1
  nspr: update to 4.11
  mobile-broadband-provider-info: update to current commit
  puzzles: update to current commit
  mirrors: replace references to archive.apache.org
  json-c: add manual upstream version check
  subversion: update to 1.9.2
  slang: update upstream URI to (official) jedsoft.org

 meta/classes/mirrors.bbclass                       |    2 +-
 meta/conf/bitbake.conf                             |    2 +-
 .../mobile-broadband-provider-info_git.bb          |    4 +-
 .../{openssl_1.0.2d.bb => openssl_1.0.2e.bb}       |    4 +-
 meta/recipes-devtools/json-c/json-c_0.12.bb        |    3 +
 ...uptools_18.2.bb => python-setuptools_18.7.1.bb} |    5 +-
 ...ptools_18.2.bb => python3-setuptools_18.7.1.bb} |    5 +-
 .../subversion/subversion-1.8.13/libtool2.patch    |   15 -
 .../subversion-CVE-2015-3184.patch                 | 2094 --------------------
 .../subversion-CVE-2015-3187.patch                 |  346 ----
 .../0001-Fix-libtool-name-in-configure.ac.patch    |   29 +
 .../disable_macos.patch                            |    0
 ...erf.m4-Regex-modified-to-allow-D-in-paths.patch |   14 +-
 .../{subversion_1.8.13.bb => subversion_1.9.2.bb}  |   12 +-
 meta/recipes-extended/slang/slang_2.2.4.bb         |    3 +-
 .../fix-compiling-failure-with-option-g-O.patch    |    9 -
 meta/recipes-sato/puzzles/puzzles_git.bb           |    6 +-
 meta/recipes-support/gnutls/gnutls.inc             |    3 +-
 ...tch => 0001-configure.ac-fix-sed-command.patch} |   29 +-
 .../gnutls/{gnutls_3.3.17.1.bb => gnutls_3.4.7.bb} |    6 +-
 .../nspr/{nspr_4.10.8.bb => nspr_4.11.bb}          |    9 +-
 21 files changed, 86 insertions(+), 2514 deletions(-)
 rename meta/recipes-connectivity/openssl/{openssl_1.0.2d.bb => openssl_1.0.2e.bb} (94%)
 rename meta/recipes-devtools/python/{python-setuptools_18.2.bb => python-setuptools_18.7.1.bb} (84%)
 rename meta/recipes-devtools/python/{python3-setuptools_18.2.bb => python3-setuptools_18.7.1.bb} (91%)
 delete mode 100644 meta/recipes-devtools/subversion/subversion-1.8.13/libtool2.patch
 delete mode 100644 meta/recipes-devtools/subversion/subversion-1.8.13/subversion-CVE-2015-3184.patch
 delete mode 100644 meta/recipes-devtools/subversion/subversion-1.8.13/subversion-CVE-2015-3187.patch
 create mode 100644 meta/recipes-devtools/subversion/subversion/0001-Fix-libtool-name-in-configure.ac.patch
 rename meta/recipes-devtools/subversion/{subversion-1.8.13 => subversion}/disable_macos.patch (100%)
 rename meta/recipes-devtools/subversion/{subversion-1.8.13 => subversion}/serf.m4-Regex-modified-to-allow-D-in-paths.patch (59%)
 rename meta/recipes-devtools/subversion/{subversion_1.8.13.bb => subversion_1.9.2.bb} (90%)
 rename meta/recipes-support/gnutls/gnutls/{configure.ac-fix-sed-command.patch => 0001-configure.ac-fix-sed-command.patch} (40%)
 rename meta/recipes-support/gnutls/{gnutls_3.3.17.1.bb => gnutls_3.4.7.bb} (42%)
 rename meta/recipes-support/nspr/{nspr_4.10.8.bb => nspr_4.11.bb} (93%)

-- 
2.6.2



             reply	other threads:[~2015-12-09 14:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 14:40 Alexander Kanavin [this message]
2015-12-09 14:40 ` [PATCH 01/10] openssl: update to 1.0.2e Alexander Kanavin
2015-12-09 19:52   ` akuster808
2015-12-10 10:50     ` Alexander Kanavin
2015-12-10 23:13       ` Paul Eggleton
2015-12-11 12:18         ` Alexander Kanavin
2015-12-14 14:34   ` Otavio Salvador
2015-12-15  0:49     ` Khem Raj
2015-12-09 14:40 ` [PATCH 02/10] gnutls: update to 3.4.7 Alexander Kanavin
2015-12-10 22:27   ` Burton, Ross
2015-12-09 14:40 ` [PATCH 03/10] python-setuptools: update to 18.7.1 Alexander Kanavin
2015-12-09 14:40 ` [PATCH 04/10] nspr: update to 4.11 Alexander Kanavin
2015-12-09 14:40 ` [PATCH 05/10] mobile-broadband-provider-info: update to current commit Alexander Kanavin
2015-12-09 14:40 ` [PATCH 06/10] puzzles: " Alexander Kanavin
2015-12-09 14:40 ` [PATCH 07/10] mirrors: replace references to archive.apache.org Alexander Kanavin
2015-12-21 22:21   ` Andre McCurdy
2015-12-22 13:22     ` Alexander Kanavin
2015-12-22 19:52       ` Andre McCurdy
2015-12-09 14:40 ` [PATCH 08/10] json-c: add manual upstream version check Alexander Kanavin
2015-12-09 14:40 ` [PATCH 09/10] subversion: update to 1.9.2 Alexander Kanavin
2015-12-09 14:40 ` [PATCH 10/10] slang: update upstream URI to (official) jedsoft.org 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=cover.1449671297.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