Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] update libsoup, remove gnome-keyring
Date: Wed,  1 May 2013 11:19:17 +0100	[thread overview]
Message-ID: <cover.1367403369.git.ross.burton@intel.com> (raw)

Hi,

This series upgrades libsoup to the latest stable release.  This release also
remoes the libgnome-keyring use, so delete libgnome-keyring and gnome-keyring
from oe-core (these have already been integrated into meta-gnome).

Ross

The following changes since commit c42cc8fb38aee46f4778b9c68412a47ae5919923:

  neard: add systemd unit file (2013-04-29 15:31:41 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ross/soup

for you to fetch changes up to 14c10a2894fd7e722a8443b03b12462ab8bdfdad:

  libgnome-keyring: remove, nothing in oe-core uses this anymore (2013-05-01 11:14:39 +0100)

----------------------------------------------------------------
Ross Burton (3):
      libsoup: upgrade to 2.42.1
      gnome-keyring: remove, nothing uses it in oe-core
      libgnome-keyring: remove, nothing in oe-core uses this anymore

 meta/conf/distro/include/seperatebuilddir.inc      |    2 -
 .../gnome/gnome-keyring/org.gnome.keyring.service  |    3 --
 meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb   |   44 --------------------
 .../recipes-gnome/gnome/libgnome-keyring_2.32.0.bb |   19 ---------
 ...libsoup-2.4_2.40.2.bb => libsoup-2.4_2.42.1.bb} |   14 +++----
 5 files changed, 7 insertions(+), 75 deletions(-)
 delete mode 100644 meta/recipes-gnome/gnome/gnome-keyring/org.gnome.keyring.service
 delete mode 100644 meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb
 delete mode 100644 meta/recipes-gnome/gnome/libgnome-keyring_2.32.0.bb
 rename meta/recipes-support/libsoup/{libsoup-2.4_2.40.2.bb => libsoup-2.4_2.42.1.bb} (59%)

Ross Burton (3):
  libsoup: upgrade to 2.42.1
  gnome-keyring: remove, nothing uses it in oe-core
  libgnome-keyring: remove, nothing in oe-core uses this anymore

 meta/conf/distro/include/seperatebuilddir.inc      |    2 -
 .../gnome/gnome-keyring/org.gnome.keyring.service  |    3 --
 meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb   |   44 --------------------
 .../recipes-gnome/gnome/libgnome-keyring_2.32.0.bb |   19 ---------
 ...libsoup-2.4_2.40.2.bb => libsoup-2.4_2.42.1.bb} |   14 +++----
 5 files changed, 7 insertions(+), 75 deletions(-)
 delete mode 100644 meta/recipes-gnome/gnome/gnome-keyring/org.gnome.keyring.service
 delete mode 100644 meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb
 delete mode 100644 meta/recipes-gnome/gnome/libgnome-keyring_2.32.0.bb
 rename meta/recipes-support/libsoup/{libsoup-2.4_2.40.2.bb => libsoup-2.4_2.42.1.bb} (59%)

-- 
1.7.10.4




             reply	other threads:[~2013-05-01 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 10:19 Ross Burton [this message]
2013-05-01 10:19 ` [PATCH 1/3] libsoup: upgrade to 2.42.1 Ross Burton
2013-05-01 11:38   ` Koen Kooi
2013-05-01 11:44     ` Burton, Ross
2013-05-01 10:19 ` [PATCH 2/3] gnome-keyring: remove, nothing uses it in oe-core Ross Burton
2013-05-01 10:19 ` [PATCH 3/3] libgnome-keyring: remove, nothing in oe-core uses this anymore Ross Burton

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.1367403369.git.ross.burton@intel.com \
    --to=ross.burton@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