Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/8] package upgrades
Date: Mon,  9 Apr 2018 14:55:03 +0300	[thread overview]
Message-ID: <1523274911-20401-1-git-send-email-maxin.john@intel.com> (raw)

Package upgrades

Maxin B. John (8):
  libatomic-ops: upgrade to version 7.6.4
  bluez5: upgrade to version 5.49
  libsolv: upgrade to version 0.6.34
  ruby: upgrade to version 2.5.1
  gtk+3: upgrade to version 3.22.29
  gsettings-desktop-schemas: upgrade to version 3.28.0
  puzzles: upgrade to latest commit
  gtk-icon-utils-native: upgrade to version 3.22.29

 meta/recipes-connectivity/bluez5/bluez5.inc                          | 1 +
 meta/recipes-connectivity/bluez5/{bluez5_5.48.bb => bluez5_5.49.bb}  | 5 +++--
 meta/recipes-devtools/ruby/ruby.inc                                  | 2 +-
 meta/recipes-devtools/ruby/{ruby_2.5.0.bb => ruby_2.5.1.bb}          | 4 ++--
 .../libsolv/{libsolv_0.6.33.bb => libsolv_0.6.34.bb}                 | 2 +-
 ...desktop-schemas_3.24.1.bb => gsettings-desktop-schemas_3.28.0.bb} | 4 ++--
 meta/recipes-gnome/gtk+/{gtk+3_3.22.28.bb => gtk+3_3.22.29.bb}       | 4 ++--
 ...icon-utils-native_3.22.28.bb => gtk-icon-utils-native_3.22.29.bb} | 4 ++--
 meta/recipes-sato/puzzles/puzzles_git.bb                             | 2 +-
 .../libatomic-ops/{libatomic-ops_7.6.2.bb => libatomic-ops_7.6.4.bb} | 2 +-
 10 files changed, 16 insertions(+), 14 deletions(-)
 rename meta/recipes-connectivity/bluez5/{bluez5_5.48.bb => bluez5_5.49.bb} (87%)
 rename meta/recipes-devtools/ruby/{ruby_2.5.0.bb => ruby_2.5.1.bb} (90%)
 rename meta/recipes-extended/libsolv/{libsolv_0.6.33.bb => libsolv_0.6.34.bb} (94%)
 rename meta/recipes-gnome/gsettings-desktop-schemas/{gsettings-desktop-schemas_3.24.1.bb => gsettings-desktop-schemas_3.28.0.bb} (70%)
 rename meta/recipes-gnome/gtk+/{gtk+3_3.22.28.bb => gtk+3_3.22.29.bb} (83%)
 rename meta/recipes-gnome/gtk+/{gtk-icon-utils-native_3.22.28.bb => gtk-icon-utils-native_3.22.29.bb} (94%)
 rename meta/recipes-support/libatomic-ops/{libatomic-ops_7.6.2.bb => libatomic-ops_7.6.4.bb} (91%)

-- 
2.4.0



             reply	other threads:[~2018-04-09 11:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 11:55 Maxin B. John [this message]
2018-04-09 11:55 ` [PATCH 1/8] libatomic-ops: upgrade to version 7.6.4 Maxin B. John
2018-04-09 11:55 ` [PATCH 2/8] bluez5: upgrade to version 5.49 Maxin B. John
2018-04-09 11:55 ` [PATCH 3/8] libsolv: upgrade to version 0.6.34 Maxin B. John
2018-04-09 11:55 ` [PATCH 4/8] ruby: upgrade to version 2.5.1 Maxin B. John
2018-04-09 11:55 ` [PATCH 5/8] gtk+3: upgrade to version 3.22.29 Maxin B. John
2018-04-09 11:55 ` [PATCH 6/8] gsettings-desktop-schemas: upgrade to version 3.28.0 Maxin B. John
2018-04-09 11:55 ` [PATCH 7/8] puzzles: upgrade to latest commit Maxin B. John
2018-04-09 11:55 ` [PATCH 8/8] gtk-icon-utils-native: upgrade to version 3.22.29 Maxin B. John
  -- strict thread matches above, loose matches on Subject: below --
2015-04-20  8:09 [PATCH 0/8] Package Upgrades Robert Yang
2013-05-10 15:04 [PATCH 0/8] Package upgrades Laurentiu Palcu
2012-07-04 18:17 [PATCH 0/8] package upgrades Laurentiu Palcu
2012-07-09 17:32 ` Saul Wold

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=1523274911-20401-1-git-send-email-maxin.john@intel.com \
    --to=maxin.john@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