From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/9] Bunch of upgrades
Date: Thu, 14 Jan 2016 15:27:41 +0200 [thread overview]
Message-ID: <cover.1452777133.git.jussi.kukkonen@intel.com> (raw)
Fairly minor upgrades (maybe with the exception of gpgme).
FYI, all are based on AUH generated patches.
Cheers,
Jussi
The following changes since commit 96a34e7f847ad34deac520b78809e7dd82dbc59e:
conf/distro/poky-tiny: correctly disable python in opkg-utils (2016-01-12 15:35:27 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib jku/auh-upgrades
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jku/auh-upgrades
Jussi Kukkonen (9):
gpgme: upgrade to 1.6.0
gsettings-desktop-schemas: upgrade to 3.19.3
libcroco: upgrade to 0.6.11
libevdev: upgrade to 1.4.6
libgpg-error: upgrade to 1.21
librsvg: upgrade to 2.40.13
libxi: upgrade to 1.7.6
menu-cache: upgrade to 1.0.1
xf86-input-evdev: upgrade to 2.10.1
...chemas_3.18.1.bb => gsettings-desktop-schemas_3.19.3.bb} | 4 ++--
meta/recipes-gnome/librsvg/librsvg/gtk-option.patch | 13 +++++--------
.../librsvg/{librsvg_2.40.11.bb => librsvg_2.40.13.bb} | 4 ++--
.../menu-cache/{menu-cache_1.0.0.bb => menu-cache_1.0.1.bb} | 4 ++--
...f86-input-evdev_2.10.0.bb => xf86-input-evdev_2.10.1.bb} | 4 ++--
.../xorg-lib/{libxi_1.7.5.bb => libxi_1.7.6.bb} | 4 ++--
.../gpgme/{gpgme_1.5.4.bb => gpgme_1.6.0.bb} | 6 +++---
.../libcroco/{libcroco_0.6.9.bb => libcroco_0.6.11.bb} | 5 ++---
.../libevdev/{libevdev_1.4.2.bb => libevdev_1.4.6.bb} | 4 ++--
.../{libgpg-error_1.19.bb => libgpg-error_1.21.bb} | 6 +++---
10 files changed, 25 insertions(+), 29 deletions(-)
rename meta/recipes-gnome/gsettings-desktop-schemas/{gsettings-desktop-schemas_3.18.1.bb => gsettings-desktop-schemas_3.19.3.bb} (69%)
rename meta/recipes-gnome/librsvg/{librsvg_2.40.11.bb => librsvg_2.40.13.bb} (91%)
rename meta/recipes-graphics/menu-cache/{menu-cache_1.0.0.bb => menu-cache_1.0.1.bb} (79%)
rename meta/recipes-graphics/xorg-driver/{xf86-input-evdev_2.10.0.bb => xf86-input-evdev_2.10.1.bb} (83%)
rename meta/recipes-graphics/xorg-lib/{libxi_1.7.5.bb => libxi_1.7.6.bb} (81%)
rename meta/recipes-support/gpgme/{gpgme_1.5.4.bb => gpgme_1.6.0.bb} (85%)
rename meta/recipes-support/libcroco/{libcroco_0.6.9.bb => libcroco_0.6.11.bb} (80%)
rename meta/recipes-support/libevdev/{libevdev_1.4.2.bb => libevdev_1.4.6.bb} (74%)
rename meta/recipes-support/libgpg-error/{libgpg-error_1.19.bb => libgpg-error_1.21.bb} (86%)
--
2.1.4
next reply other threads:[~2016-01-14 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 13:27 Jussi Kukkonen [this message]
2016-01-14 13:27 ` [PATCH 1/9] gpgme: upgrade to 1.6.0 Jussi Kukkonen
2016-01-14 13:27 ` [PATCH 2/9] gsettings-desktop-schemas: upgrade to 3.19.3 Jussi Kukkonen
2016-01-14 13:27 ` [PATCH 3/9] libcroco: upgrade to 0.6.11 Jussi Kukkonen
2016-01-14 13:27 ` [PATCH 4/9] libevdev: upgrade to 1.4.6 Jussi Kukkonen
2016-01-14 13:27 ` [PATCH 5/9] libgpg-error: upgrade to 1.21 Jussi Kukkonen
2016-01-14 13:27 ` [PATCH 6/9] librsvg: upgrade to 2.40.13 Jussi Kukkonen
2016-01-14 13:27 ` [PATCH 7/9] libxi: upgrade to 1.7.6 Jussi Kukkonen
2016-01-14 13:27 ` [PATCH 8/9] menu-cache: upgrade to 1.0.1 Jussi Kukkonen
2016-01-14 13:27 ` [PATCH 9/9] xf86-input-evdev: upgrade to 2.10.1 Jussi Kukkonen
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.1452777133.git.jussi.kukkonen@intel.com \
--to=jussi.kukkonen@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