Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Constantin Musca <constantinx.musca@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Package upgrades
Date: Fri, 24 Aug 2012 17:33:03 +0300	[thread overview]
Message-ID: <cover.1345818232.git.constantinx.musca@intel.com> (raw)

This is another set of package upgrades compiled on all architectures
and tested using core-image-sato.
The following changes since commit 054d95edad8d79ef1c6b30681395d50f3c6335b4:

  poky.conf: restore Ubuntu 12.04 LTS to tested distro list (2012-08-23 17:23:40 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib cmuscax/upgrades
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=cmuscax/upgrades

Constantin Musca (4):
  wget: upgrade to 1.14
  npth: upgrade to 0.91
  kconfig-frontends: upgrade to 3.5
  base-passwd: upgrade to 3.5.26

 .../nobash.patch                                   |    0
 .../root-home.patch                                |    0
 ...base-passwd_3.5.24.bb => base-passwd_3.5.26.bb} |    6 ++---
 ...g-frontends_3.4.bb => kconfig-frontends_3.5.bb} |    6 ++---
 .../wget/wget-1.13.4/remove-gets.patch             |   23 --------------------
 .../{wget-1.13.4 => wget-1.14}/fix_makefile.patch  |    0
 meta/recipes-extended/wget/wget_1.13.4.bb          |   10 ---------
 meta/recipes-extended/wget/wget_1.14.bb            |    9 ++++++++
 .../npth/{npth_0.90.bb => npth_0.91.bb}            |    4 ++--
 9 files changed, 16 insertions(+), 42 deletions(-)
 rename meta/recipes-core/base-passwd/{base-passwd-3.5.24 => base-passwd-3.5.26}/nobash.patch (100%)
 rename meta/recipes-core/base-passwd/{base-passwd-3.5.24 => base-passwd-3.5.26}/root-home.patch (100%)
 rename meta/recipes-core/base-passwd/{base-passwd_3.5.24.bb => base-passwd_3.5.26.bb} (94%)
 rename meta/recipes-devtools/kconfig-frontends/{kconfig-frontends_3.4.bb => kconfig-frontends_3.5.bb} (88%)
 delete mode 100644 meta/recipes-extended/wget/wget-1.13.4/remove-gets.patch
 rename meta/recipes-extended/wget/{wget-1.13.4 => wget-1.14}/fix_makefile.patch (100%)
 delete mode 100644 meta/recipes-extended/wget/wget_1.13.4.bb
 create mode 100644 meta/recipes-extended/wget/wget_1.14.bb
 rename meta/recipes-support/npth/{npth_0.90.bb => npth_0.91.bb} (76%)

-- 
1.7.9.5




             reply	other threads:[~2012-08-24 15:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 14:33 Constantin Musca [this message]
2012-08-24 14:33 ` [PATCH 1/4] wget: upgrade to 1.14 Constantin Musca
2012-08-24 14:33 ` [PATCH 2/4] npth: upgrade to 0.91 Constantin Musca
2012-08-24 14:33 ` [PATCH 3/4] kconfig-frontends: upgrade to 3.5 Constantin Musca
2012-08-24 14:33 ` [PATCH 4/4] base-passwd: upgrade to 3.5.26 Constantin Musca
2012-08-27 15:54 ` [PATCH 0/4] Package upgrades Saul Wold
  -- strict thread matches above, loose matches on Subject: below --
2013-03-11 16:27 Laurentiu Palcu
2013-07-24 12:42 Ionut Radu
2013-10-24  8:01 Cristiana Voicu
2014-05-08 15:05 Valentin Popa
2014-07-30 22:54 [PATCH 0/4] Package Upgrades Saul Wold
2016-07-04 13:02 [PATCH 0/4] package upgrades Maxin B. John
2018-05-21 23:17 [PATCH 0/4] Package upgrades Denys Dmytriyenko
2018-05-21 23:21 ` Denys Dmytriyenko

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.1345818232.git.constantinx.musca@intel.com \
    --to=constantinx.musca@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