[oe] [meta-python][PATCH] python-pytz: remove executable bit on the recipe files

2017-02-02 Thread Derek Straka
Signed-off-by: Derek Straka 
---
 meta-python/recipes-devtools/python/python-pytz_2016.10.bb  | 0
 meta-python/recipes-devtools/python/python3-pytz_2016.10.bb | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 mode change 100755 => 100644 
meta-python/recipes-devtools/python/python-pytz_2016.10.bb
 mode change 100755 => 100644 
meta-python/recipes-devtools/python/python3-pytz_2016.10.bb

diff --git a/meta-python/recipes-devtools/python/python-pytz_2016.10.bb 
b/meta-python/recipes-devtools/python/python-pytz_2016.10.bb
old mode 100755
new mode 100644
diff --git a/meta-python/recipes-devtools/python/python3-pytz_2016.10.bb 
b/meta-python/recipes-devtools/python/python3-pytz_2016.10.bb
old mode 100755
new mode 100644
-- 
2.7.4

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


[oe] [meta-oe]PATCH] openipmi: Add new package

2017-02-02 Thread Armin Kuster
From: Armin Kuster 

Intelligent Platform Management Interface (IPMI) is has become a standard hw 
interface in many X86 platforms.

Signed-off-by: Armin Kuster 
---
 .../openipmi-2.0.22/makefiles_remove_libdir.patch  |  71 +++
 .../openipmi/openipmi-2.0.22/openipmi.initscript   | 584 +
 .../openipmi/openipmi-2.0.22/openipmi.service  |  12 +
 meta-oe/recipes-bsp/openipmi/openipmi_2.0.22.bb|  45 ++
 4 files changed, 712 insertions(+)
 create mode 100644 
meta-oe/recipes-bsp/openipmi/openipmi-2.0.22/makefiles_remove_libdir.patch
 create mode 100644 
meta-oe/recipes-bsp/openipmi/openipmi-2.0.22/openipmi.initscript
 create mode 100644 
meta-oe/recipes-bsp/openipmi/openipmi-2.0.22/openipmi.service
 create mode 100644 meta-oe/recipes-bsp/openipmi/openipmi_2.0.22.bb

diff --git 
a/meta-oe/recipes-bsp/openipmi/openipmi-2.0.22/makefiles_remove_libdir.patch 
b/meta-oe/recipes-bsp/openipmi/openipmi-2.0.22/makefiles_remove_libdir.patch
new file mode 100644
index 000..ba6f222
--- /dev/null
+++ b/meta-oe/recipes-bsp/openipmi/openipmi-2.0.22/makefiles_remove_libdir.patch
@@ -0,0 +1,71 @@
+Upstream-Status: Inappropriate (OE specific)
+
+Signed-off-by: Armin Kuster 
+
+Index: OpenIPMI-2.0.22/unix/Makefile.am
+===
+--- OpenIPMI-2.0.22.orig/unix/Makefile.am
 OpenIPMI-2.0.22/unix/Makefile.am
+@@ -11,13 +11,13 @@ libOpenIPMIpthread_la_SOURCES = posix_th
+ libOpenIPMIpthread_la_LIBADD = -lpthread $(GDBM_LIB) \
+   $(top_builddir)/utils/libOpenIPMIutils.la
+ libOpenIPMIpthread_la_LDFLAGS = -rdynamic -version-info $(LD_VERSION) \
+-  -Wl,-Map -Wl,libOpenIPMIpthread.map -L$(libdir)
++  -Wl,-Map -Wl,libOpenIPMIpthread.map
+ 
+ libOpenIPMIposix_la_SOURCES = posix_os_hnd.c selector.c
+ libOpenIPMIposix_la_LIBADD = $(top_builddir)/utils/libOpenIPMIutils.la \
+   $(GDBM_LIB)
+ libOpenIPMIposix_la_LDFLAGS = -rdynamic -version-info $(LD_VERSION) \
+-  -Wl,-Map -Wl,libOpenIPMIposix.map -L$(libdir)
++  -Wl,-Map -Wl,libOpenIPMIposix.map
+ 
+ noinst_HEADERS = heap.h
+ 
+Index: OpenIPMI-2.0.22/glib/Makefile.am
+===
+--- OpenIPMI-2.0.22.orig/glib/Makefile.am
 OpenIPMI-2.0.22/glib/Makefile.am
+@@ -11,14 +11,14 @@ libOpenIPMIglib_la_SOURCES = glib_os_hnd
+ libOpenIPMIglib_la_CFLAGS = $(GLIB_CFLAGS) $(AM_CFLAGS)
+ libOpenIPMIglib_la_LIBADD = $(GDBM_LIB)
+ libOpenIPMIglib_la_LDFLAGS = -rdynamic -version-info $(LD_VERSION) \
+-  -Wl,-Map -Wl,libOpenIPMIglib.map $(GLIB_LIBS) -L$(libdir) \
++  -Wl,-Map -Wl,libOpenIPMIglib.map $(GLIB_LIBS) \
+   -rpath $(libdir)
+ 
+ libOpenIPMIglib12_la_SOURCES = glib_os_hnd.c
+ libOpenIPMIglib12_la_CFLAGS = $(GLIB12_CFLAGS) $(AM_CFLAGS)
+ libOpenIPMIglib12_la_LIBADD = $(GDBM_LIB)
+ libOpenIPMIglib12_la_LDFLAGS = -rdynamic -version-info $(LD_VERSION) \
+-  -Wl,-Map -Wl,libOpenIPMIglib12.map $(GLIB12_LIBS) -L$(libdir) \
++  -Wl,-Map -Wl,libOpenIPMIglib12.map $(GLIB12_LIBS) \
+   -rpath $(libdir)
+ 
+ CLEANFILES = libOpenIPMIglib.map libOpenIPMIglib12.map
+Index: OpenIPMI-2.0.22/cmdlang/Makefile.am
+===
+--- OpenIPMI-2.0.22.orig/cmdlang/Makefile.am
 OpenIPMI-2.0.22/cmdlang/Makefile.am
+@@ -16,7 +16,7 @@ libOpenIPMIcmdlang_la_LIBADD = -lm \
+   $(top_builddir)/utils/libOpenIPMIutils.la \
+   $(top_builddir)/lib/libOpenIPMI.la
+ libOpenIPMIcmdlang_la_LDFLAGS = -rdynamic -version-info $(LD_VERSION) \
+-  -Wl,-Map -Wl,libOpenIPMIcmdlang.map -L$(libdir)
++  -Wl,-Map -Wl,libOpenIPMIcmdlang.map
+ 
+ bin_PROGRAMS = openipmish
+ 
+Index: OpenIPMI-2.0.22/tcl/Makefile.am
+===
+--- OpenIPMI-2.0.22.orig/tcl/Makefile.am
 OpenIPMI-2.0.22/tcl/Makefile.am
+@@ -11,7 +11,7 @@ libOpenIPMItcl_la_SOURCES = tcl_os_hnd.c
+ libOpenIPMItcl_la_CFLAGS = $(TCL_CFLAGS) $(AM_CFLAGS)
+ libOpenIPMItcl_la_LIBADD = $(GDBM_LIB)
+ libOpenIPMItcl_la_LDFLAGS = -rdynamic -version-info $(LD_VERSION) \
+-  -Wl,-Map -Wl,libOpenIPMItcl.map $(TCL_LIBS) -L$(libdir) \
++  -Wl,-Map -Wl,libOpenIPMItcl.map $(TCL_LIBS) \
+   -rpath $(libdir)
+ 
+ noinst_PROGRAMS = test_handlers
diff --git a/meta-oe/recipes-bsp/openipmi/openipmi-2.0.22/openipmi.initscript 
b/meta-oe/recipes-bsp/openipmi/openipmi-2.0.22/openipmi.initscript
new file mode 100644
index 000..3eda3f8
--- /dev/null
+++ b/meta-oe/recipes-bsp/openipmi/openipmi-2.0.22/openipmi.initscript
@@ -0,0 +1,584 @@
+#!/bin/sh
+#
+#
+# ipmi:OpenIPMI Driver init script
+#
+# Authors: Matt Domsch 
+#   Chris Poblete 
+#
+# chkconfig: - 13 87
+# description: OpenIPMI Driver init script
+#
+### BEGIN INIT INFO
+# Provides: ipmidrv
+# Required-Start: $local_fs $remote_fs $syslog
+# Required-Stop: $local_fs $remote_fs $syslog
+# Default-Start:
+# 

Re: [oe] [PATCH][meta-qt5 3/4] qtwayland: fix build without xkbcommon-evdev

2017-02-02 Thread Martin Jansa
This isn't enough at least in some setups, but it's good start (it works
after you add -lxkbcommon in 2 incorrectly generated Makefiles) and at
least it documents that xkbcommon-evdev is now needed to be set in qtbase
PACKAGECONFIG.

On Fri, Feb 3, 2017 at 12:54 AM, Martin Jansa 
wrote:

> * xkbcommon-evdev isn't enabled in default qtbase PACKAGECONFIG
> * use patch from https://bugreports.qt.io/browse/QTBUG-57767
>
> Signed-off-by: Martin Jansa 
> ---
>  .../0001-fix-build-without-xkbcommon-evdev.patch   | 44
> ++
>  recipes-qt/qt5/qtwayland_git.bb|  3 ++
>  2 files changed, 47 insertions(+)
>  create mode 100644 recipes-qt/qt5/qtwayland/0001-
> fix-build-without-xkbcommon-evdev.patch
>
> diff --git 
> a/recipes-qt/qt5/qtwayland/0001-fix-build-without-xkbcommon-evdev.patch
> b/recipes-qt/qt5/qtwayland/0001-fix-build-without-xkbcommon-evdev.patch
> new file mode 100644
> index 000..e1e978e
> --- /dev/null
> +++ b/recipes-qt/qt5/qtwayland/0001-fix-build-without-
> xkbcommon-evdev.patch
> @@ -0,0 +1,44 @@
> +From c93dbe53e8a1b2203c750a66c7efe6fc9a326903 Mon Sep 17 00:00:00 2001
> +From: Raphael Freudiger 
> +Date: Thu, 22 Dec 2016 13:54:31 +0100
> +Subject: [PATCH] fix build without xkbcommon-evdev
> +
> +Signed-off-by: Raphael Freudiger 
> +---
> + src/compositor/compositor_api/qwaylandkeyboard.cpp | 13 +++--
> + 1 file changed, 7 insertions(+), 6 deletions(-)
> +
> +diff --git a/src/compositor/compositor_api/qwaylandkeyboard.cpp
> b/src/compositor/compositor_api/qwaylandkeyboard.cpp
> +index 55381b4..5c054c6 100644
> +--- a/src/compositor/compositor_api/qwaylandkeyboard.cpp
>  b/src/compositor/compositor_api/qwaylandkeyboard.cpp
> +@@ -338,12 +338,6 @@ void QWaylandKeyboardPrivate::createXKBState(xkb_keymap
> *keymap)
> + xkb_state = xkb_state_new(keymap);
> + }
> +
> +-uint QWaylandKeyboardPrivate::toWaylandXkbV1Key(const uint
> nativeScanCode)
> +-{
> +-const uint offset = 8;
> +-Q_ASSERT(nativeScanCode >= offset);
> +-return nativeScanCode - offset;
> +-}
> +
> + void QWaylandKeyboardPrivate::createXKBKeymap()
> + {
> +@@ -373,6 +367,13 @@ void QWaylandKeyboardPrivate::createXKBKeymap()
> + }
> + #endif
> +
> ++uint QWaylandKeyboardPrivate::toWaylandXkbV1Key(const uint
> nativeScanCode)
> ++{
> ++const uint offset = 8;
> ++Q_ASSERT(nativeScanCode >= offset);
> ++return nativeScanCode - offset;
> ++}
> ++
> + void QWaylandKeyboardPrivate::sendRepeatInfo()
> + {
> + Q_FOREACH (Resource *resource, resourceMap()) {
> +--
> +2.1.4
> +
> diff --git a/recipes-qt/qt5/qtwayland_git.bb b/recipes-qt/qt5/qtwayland_
> git.bb
> index 21abd54..d42d80a 100644
> --- a/recipes-qt/qt5/qtwayland_git.bb
> +++ b/recipes-qt/qt5/qtwayland_git.bb
> @@ -43,4 +43,7 @@ EXTRA_QMAKEVARS_CONFIGURE += "${PACKAGECONFIG_CONFARGS}"
>
>  SRCREV = "0e2a950895805457a45abe860bc91a7cc4ba405e"
>
> +# From https://bugreports.qt.io/browse/QTBUG-57767
> +SRC_URI += "file://0001-fix-build-without-xkbcommon-evdev.patch"
> +
>  BBCLASSEXTEND =+ "native nativesdk"
> --
> 2.10.2
>
>
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


[oe] [PATCH][meta-qt5 4/4] qtwebengine: disable generate_character_data

2017-02-02 Thread Martin Jansa
* qtwebengine 5.8 fails to build it, because it mixes binaries for x86_64 host 
and x86 target when building for qemux86 on 64bit host
  https://bugreports.qt.io/browse/QTBUG-57705

Signed-off-by: Martin Jansa 
---
 recipes-qt/qt5/qtwebengine_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-qt/qt5/qtwebengine_git.bb 
b/recipes-qt/qt5/qtwebengine_git.bb
index 4ab30ea..3d139d0 100644
--- a/recipes-qt/qt5/qtwebengine_git.bb
+++ b/recipes-qt/qt5/qtwebengine_git.bb
@@ -24,7 +24,7 @@ DEPENDS += " \
 "
 
 DEPENDS += "yasm-native"
-EXTRA_QMAKEVARS_PRE += "GYP_CONFIG+=use_system_yasm"
+EXTRA_QMAKEVARS_PRE += "GYP_CONFIG+=use_system_yasm 
GYP_CONFIG+=generate_character_data=0"
 
 # To use system ffmpeg you need to enable also libwebp, opus, vpx  

 # Only depenedencies available in oe-core are enabled by default
-- 
2.10.2

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


[oe] [PATCH][meta-qt5 3/4] qtwayland: fix build without xkbcommon-evdev

2017-02-02 Thread Martin Jansa
* xkbcommon-evdev isn't enabled in default qtbase PACKAGECONFIG
* use patch from https://bugreports.qt.io/browse/QTBUG-57767

Signed-off-by: Martin Jansa 
---
 .../0001-fix-build-without-xkbcommon-evdev.patch   | 44 ++
 recipes-qt/qt5/qtwayland_git.bb|  3 ++
 2 files changed, 47 insertions(+)
 create mode 100644 
recipes-qt/qt5/qtwayland/0001-fix-build-without-xkbcommon-evdev.patch

diff --git 
a/recipes-qt/qt5/qtwayland/0001-fix-build-without-xkbcommon-evdev.patch 
b/recipes-qt/qt5/qtwayland/0001-fix-build-without-xkbcommon-evdev.patch
new file mode 100644
index 000..e1e978e
--- /dev/null
+++ b/recipes-qt/qt5/qtwayland/0001-fix-build-without-xkbcommon-evdev.patch
@@ -0,0 +1,44 @@
+From c93dbe53e8a1b2203c750a66c7efe6fc9a326903 Mon Sep 17 00:00:00 2001
+From: Raphael Freudiger 
+Date: Thu, 22 Dec 2016 13:54:31 +0100
+Subject: [PATCH] fix build without xkbcommon-evdev
+
+Signed-off-by: Raphael Freudiger 
+---
+ src/compositor/compositor_api/qwaylandkeyboard.cpp | 13 +++--
+ 1 file changed, 7 insertions(+), 6 deletions(-)
+
+diff --git a/src/compositor/compositor_api/qwaylandkeyboard.cpp 
b/src/compositor/compositor_api/qwaylandkeyboard.cpp
+index 55381b4..5c054c6 100644
+--- a/src/compositor/compositor_api/qwaylandkeyboard.cpp
 b/src/compositor/compositor_api/qwaylandkeyboard.cpp
+@@ -338,12 +338,6 @@ void QWaylandKeyboardPrivate::createXKBState(xkb_keymap 
*keymap)
+ xkb_state = xkb_state_new(keymap);
+ }
+ 
+-uint QWaylandKeyboardPrivate::toWaylandXkbV1Key(const uint nativeScanCode)
+-{
+-const uint offset = 8;
+-Q_ASSERT(nativeScanCode >= offset);
+-return nativeScanCode - offset;
+-}
+ 
+ void QWaylandKeyboardPrivate::createXKBKeymap()
+ {
+@@ -373,6 +367,13 @@ void QWaylandKeyboardPrivate::createXKBKeymap()
+ }
+ #endif
+ 
++uint QWaylandKeyboardPrivate::toWaylandXkbV1Key(const uint nativeScanCode)
++{
++const uint offset = 8;
++Q_ASSERT(nativeScanCode >= offset);
++return nativeScanCode - offset;
++}
++
+ void QWaylandKeyboardPrivate::sendRepeatInfo()
+ {
+ Q_FOREACH (Resource *resource, resourceMap()) {
+-- 
+2.1.4
+
diff --git a/recipes-qt/qt5/qtwayland_git.bb b/recipes-qt/qt5/qtwayland_git.bb
index 21abd54..d42d80a 100644
--- a/recipes-qt/qt5/qtwayland_git.bb
+++ b/recipes-qt/qt5/qtwayland_git.bb
@@ -43,4 +43,7 @@ EXTRA_QMAKEVARS_CONFIGURE += "${PACKAGECONFIG_CONFARGS}"
 
 SRCREV = "0e2a950895805457a45abe860bc91a7cc4ba405e"
 
+# From https://bugreports.qt.io/browse/QTBUG-57767
+SRC_URI += "file://0001-fix-build-without-xkbcommon-evdev.patch"
+
 BBCLASSEXTEND =+ "native nativesdk"
-- 
2.10.2

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


[oe] [PATCH][meta-qt5 2/4] qtwayland: Add libxkbcommon in the dependencies

2017-02-02 Thread Martin Jansa
From: Herve Jourdain 

xkb should be optional, but it's not for the moment, so add it to the
dependencies.

Signed-off-by: Herve Jourdain 
Signed-off-by: Martin Jansa 
---
 recipes-qt/qt5/qtwayland_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-qt/qt5/qtwayland_git.bb b/recipes-qt/qt5/qtwayland_git.bb
index ec41922..21abd54 100644
--- a/recipes-qt/qt5/qtwayland_git.bb
+++ b/recipes-qt/qt5/qtwayland_git.bb
@@ -2,6 +2,7 @@ require qt5.inc
 require qt5-git.inc
 
 DEPENDS += "qtbase qtdeclarative wayland wayland-native qtwayland-native"
+DEPENDS_append_class-target = " libxkbcommon"
 
 LICENSE = "GFDL-1.3 & BSD & ( GPL-3.0 & The-Qt-Company-GPL-Exception-1.0 | 
The-Qt-Company-Commercial ) & ( GPL-2.0+ | LGPL-3.0 | The-Qt-Company-Commercial 
)"
 LIC_FILES_CHKSUM = " \
-- 
2.10.2

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


[oe] [PATCH][meta-qt5 1/4] qtbase: create empty oe-device-extra.pri

2017-02-02 Thread Martin Jansa
From: Herve Jourdain 

During configure, it complains it can't find oe-device-extra.pri,
but it doesn't result in any error. Fix it, though, just in case.

Signed-off-by: Herve Jourdain 
Signed-off-by: Martin Jansa 
---
 recipes-qt/qt5/qtbase_git.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/recipes-qt/qt5/qtbase_git.bb b/recipes-qt/qt5/qtbase_git.bb
index 354a01c..5db9aad 100644
--- a/recipes-qt/qt5/qtbase_git.bb
+++ b/recipes-qt/qt5/qtbase_git.bb
@@ -130,6 +130,9 @@ QT_CONFIG_FLAGS += " \
 "
 
 do_configure() {
+# Avoid qmake error "Cannot read 
[...]/usr/lib/qt5/mkspecs/oe-device-extra.pri: No such file or directory" 
during configuration
+touch ${S}/mkspecs/oe-device-extra.pri
+
 ${S}/configure -v \
 -opensource -confirm-license \
 -sysroot ${STAGING_DIR_TARGET} \
-- 
2.10.2

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


[oe] [PATCH] udisks2: add libxslt-native to DEPENDS for xsltproc to be in sysroot

2017-02-02 Thread Paul Gortmaker
This started showing up recently on machines w/o xsltproc in
their path:

| checking for xsltproc... no
| configure: error: xsltproc is needed
| WARNING: udisks2/2.1.7-r0/temp/run.do_configure.29255:1 exit 1
| ERROR: Function failed: do_configure (log file is located at
| 
build/tmp/work/core2-64-overc-linux/udisks2/2.1.7-r0/temp/log.do_configure.29255)

Presumably the splitting of the sysroot made this happen more
frequently on such machines that didn't have a host install of the
xsltproc binary.

Signed-off-by: Paul Gortmaker 

diff --git a/meta-oe/recipes-support/udisks/udisks2_2.1.7.bb 
b/meta-oe/recipes-support/udisks/udisks2_2.1.7.bb
index fbf6701ac3ad..976d36a2ba99 100644
--- a/meta-oe/recipes-support/udisks/udisks2_2.1.7.bb
+++ b/meta-oe/recipes-support/udisks/udisks2_2.1.7.bb
@@ -2,7 +2,7 @@ SUMMARY = "udisks provides dbus interfaces for disks and 
storage devices"
 LICENSE = "GPLv2+ & LGPLv2+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=dd79f6dbbffdbc8e86b086a8f0c0ef43"
 
-DEPENDS = "acl libatasmart polkit libgudev dbus-glib glib-2.0 intltool-native 
gnome-common-native"
+DEPENDS = "acl libatasmart polkit libgudev dbus-glib glib-2.0 intltool-native 
gnome-common-native libxslt-native"
 DEPENDS += "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'systemd', '', 
d)}"
 
 RDEPENDS_${PN} = "acl"
-- 
2.11.0

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


[oe] Fwd: [FOSDEM standholders] Practical information regarding FOSDEM stands

2017-02-02 Thread Philip Balister
Stop by and help man the stand!


 Forwarded Message 
Subject: [FOSDEM standholders] Practical information regarding FOSDEM stands
Date: Thu, 2 Feb 2017 08:47:25 +0100
From: Johan van Selst 
To: standhold...@lists.fosdem.org


--WIyZ46R2i8wDzkSu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Dear FOSDEM stand organisers,

This email contains a lot of practical information about your stands
during the FOSDEM conference. Please read it completely.


Location

Stands will be located in three buildings on the ULB campus: AW, H
and K. You can find the location of your stand on the FOSDEM site:
https://fosdem.org/2017/stands/
Note that the numbers in this list do not correspond with the numbers
in the image that circulated earlier.

Timing
---
Build-up starts from 9:00 on Saturday. Visitors will start arriving
around 10:00, and you can expect it to be properly busy by noon.
The Saturday program ends at 19:00; you're expected to be out of
the building at that time.

It is possible to start on your stand on Friday afternoon. However,
there is no exact time when the tables will be ready - so if you
arrive early, you will have be asked to help us set up those tables.

For the night between Saturday and Sunday, there are overnight storage
rooms in the H and K buildings. You can also leave stuff at your stand
overnight; the buildings will be closed overnight, but we cannot guard
the hallways on Sunday morning. We also cannot provide any insurance or
take responsibility in case of damage or theft. We do have security
staff on campus at all times.

Sunday starts around 9:00-10:00 and the teardown starts at 17:00. All
stand holders are expected to help clean up the area around their stand,
and the tables and table cloths should be returned to the collection
point by the stand holders. Your stand area should be cleared and
cleaned up and the tables returned to the collection point by 17:30.

Various
---
The tables provided are 180x80cm wide. We also provide table cloths,
but you are more than welcome to provide any on your own, especially
if you have something like a banner for your project. There will be
two chairs provided per table. You may not tape posters to the walls
or windows near the stands.

We will provide you with a power socket. If you require more than
one, please bring extension cables. Note that Belgium uses type E
sockets: http://www.worldstandards.eu/electricity/plugs-and-sockets/
If you need any adapters, make sure to bring them along.

High-speed Internet uplink will be provided by means of WiFi everywhere.
If you have a device that requires a wired ethernet connection, bring a
bridge device with you.

Keep in mind that our Code of Conduct applies to stand organisers
as well. Read it at https://fosdem.org/2017/practical/conduct/


If you have any further questions, please contact us at
. During the event, you can ask volunteers for
information or contact us at the infodesk in buildings H and K;
or via +32 2 788 74 74 in case of urgent issues.

Thank you for your participation and see you in Brussels soon!


Kind regards,
FOSDEM Stands Team

--WIyZ46R2i8wDzkSu
Content-Type: application/pgp-signature

-BEGIN PGP SIGNATURE-

iF4EAREIAAYFAliS5A0ACgkQAEpMHW8nCPRbTgEAuW4izTOSsk2b7CG9XTyb4Y54
k9V3PGCBWl2oYMVA6jwA/2AM8xNKaa8hDFskuEJjiZppIbt4qrC9QTb2ZwRtfqwD
=rFAw
-END PGP SIGNATURE-

--WIyZ46R2i8wDzkSu--

___
standholders mailing list
standhold...@lists.fosdem.org
https://lists.fosdem.org/listinfo/standholders



signature.asc
Description: OpenPGP digital signature
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


Re: [oe] [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds

2017-02-02 Thread Herve Jourdain
Hi Jacobo,

OK, I will send those extra patched to the meta-raspberry list tomorrow then.

Cheers,
Herve

> On 2 Feb 2017, at 21:28, Jacobo Aragunde Pérez  wrote:
> 
>> On 02/02/17 13:46, Herve Jourdain wrote:
>> Hi Jacobo,
>> 
>> I'm using "master", and I do have patches for enabling armv7ve. But since
>> they're needed only for raspberrypi, I planned to submit them only for
>> meta-raspberrypi.
>> If you think it could be useful in meta-browser, though, I can submit them 
>> there.
>> 
> 
> Oh, I think sending them to meta-rpi would be good enough, thank you!
> I'll keep an eye on it.
> 
> Best regards,
> -- 
> Jacobo Aragunde
> Software Engineer at Igalia
> 
> 
>> -Original Message-
>> From: Jacobo Aragunde Pérez [mailto:jaragu...@igalia.com] 
>> Sent: jeudi 2 février 2017 13:30
>> To: openembedded-devel@lists.openembedded.org
>> Cc: ota...@ossystems.com.br; Herve Jourdain 
>> Subject: Re: [meta-browser][PATCH] chromium-wayland: fix compilation problem 
>> on non-X11 builds
>> 
>> Thank you all for your reviews. This should be the last patch, it addresses 
>> Herve's problem when building on a Raspberry Pi.
>> 
>> Unfortunately, I haven't been able to reproduce his problem myself, but this 
>> patch is actually a backport of an upstream patch, so it makes no harm in my 
>> opinion.
>> 
>> Another question, are you using krogoth in you rpi build? I found problems 
>> with the declared architecture in releases newer than jethro, it is called 
>> "armv7ve" and chromium doesn't build because it expects "armv7a". We could 
>> use a patch if you have worked around this problem :)
>> 
>> Thanks again,
>> --
>> Jacobo Aragunde
>> Software Engineer at Igalia
>> 
>> 
>>> On 02/02/17 13:17, Jacobo Aragunde Pérez wrote:
>>> Certain build configurations enable a code path that includes
>>> keyboard_code_conversion_xkb.cc, but it eventually fails in non-X11
>>> environments because of a missing patch that is present upstream.
>>> 
>>> This commit adds the missing patch from
>>> https://codereview.chromium.org/2239833003
>>> 
>>> There are two versions of the patch in the code review URL above.
>>> The first version fixes the problem both under the gyp and GN build
>>> systems. That patch was rejected because gyp is considered deprecated
>>> upstream. The second version fixes the problem only on GN and it was
>>> merged upstream. We are picking the first version because our recipes
>>> still use gyp to build.
>>> 
>>> Signed-off-by: Jacobo Aragunde Pérez 
>>> ---
>>> .../chromium/chromium-wayland_53.0.2785.143.bb |  1 +
>>> .../fix-non-x11-build-when-use_xkbcommon-1.patch   | 51 
>>> ++
>>> 2 files changed, 52 insertions(+)
>>> create mode 100644 
>>> recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
>>> 
>>> diff --git a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb 
>>> b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
>>> index a75918b..ef913a7 100644
>>> --- a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
>>> +++ b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
>>> @@ -13,6 +13,7 @@ SRC_URI += "\
>>> file://chromium-wayland/0011-Replace-readdir_r-with-readdir.patch \
>>> file://chromium-wayland/remove-Werror.patch \
>>> file://chromium-wayland/guard-x11_desktop_handler-inclusion.patch \
>>> +
>>> file://chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch \
>>> ${@bb.utils.contains('PACKAGECONFIG', 'component-build', 
>>> 'file://component-build.gypi', '', d)} \
>>> ${@bb.utils.contains('PACKAGECONFIG', 'ignore-lost-context', 
>>> 'file://0001-Remove-accelerated-Canvas-support-from-blacklist.patch', '', 
>>> d)} \
>>> "
>>> diff --git 
>>> a/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
>>>  
>>> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
>>> new file mode 100644
>>> index 000..976ece9
>>> --- /dev/null
>>> +++ 
>>> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
>>> @@ -0,0 +1,51 @@
>>> +From: jbriance 
>>> +Subject: keycodes: Fix non-X11 build when use_xkbcommon=1
>>> +
>>> +Since M51, ui/events/keycodes/xkb_keysym.h follows X11 path, even if
>>> +use_xkbcommon=1 is set because USE_XKBCOMMON is not defined, leading
>>> +to the following compilation error in this case:
>>> +
>>> +  In file included from 
>>> ../../ui/events/keycodes/keyboard_code_conversion_xkb.h:12:0,
>>> +   from 
>>> ../../ui/events/keycodes/keyboard_code_conversion_xkb.cc:5:
>>> +  ../../ui/events/keycodes/xkb_keysym.h:19:19: fatal error: X11/X.h: No 
>>> such file or directory
>>> +
>>> +BUG=none
>>> +
>>> +Review-Url: https://codereview.chromium.org/2239833003
>>> +--
>>> +
>>> +Index: ui/events/keycodes/BUILD.gn
>>> +diff --git a/ui/events/keycodes/BUILD.gn b/ui/events/keycodes/BUILD.gn

Re: [oe] [meta-python][PATCH 2/2] m2crypto: depend on typing

2017-02-02 Thread Andy
you are right, this was a dependency during runtime of native, my
build of crda failed with
ERROR: Failed to import the "M2Crypto" module: No module named typing
How should the the RDPENDS look like? Obviously I was to stupid to
write it down correctly.

2017-02-02 15:00 GMT+01:00 Derek Straka :
> Is this meant to be a build time dependency?  If it were required to build,
> I would have expected to see a build failure.
>
> -Derek
>
> On Thu, Feb 2, 2017 at 8:49 AM,  wrote:
>
>> From: Andy Kling 
>>
>>   m2crypto requires typing since 0.24.0-38-g8bbd0ec
>> ---
>>  meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
>> b/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
>> index 5a9594f07..ca462229e 100644
>> --- a/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
>> +++ b/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
>> @@ -12,7 +12,7 @@ SRC_URI += "file://0001-setup.py-link-in-
>> sysroot-not-in-host-directories.patch "
>>  PYPI_PACKAGE = "M2Crypto"
>>  inherit pypi setuptools siteinfo
>>
>> -DEPENDS += "openssl swig-native"
>> +DEPENDS += "openssl swig-native python-typing"
>>
>>  DISTUTILS_BUILD_ARGS += "build_ext --openssl=${STAGING_DIR_HOST}
>> -I${STAGING_INCDIR}"
>>  DISTUTILS_INSTALL_ARGS += "build_ext --openssl=${STAGING_DIR_HOST}"
>> --
>> 2.11.0
>>
>> --
>> ___
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
> --
> ___
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


Re: [oe] [meta-python][PATCH 2/2] m2crypto: depend on typing

2017-02-02 Thread Derek Straka
Is this meant to be a build time dependency?  If it were required to build,
I would have expected to see a build failure.

-Derek

On Thu, Feb 2, 2017 at 8:49 AM,  wrote:

> From: Andy Kling 
>
>   m2crypto requires typing since 0.24.0-38-g8bbd0ec
> ---
>  meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
> b/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
> index 5a9594f07..ca462229e 100644
> --- a/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
> +++ b/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
> @@ -12,7 +12,7 @@ SRC_URI += "file://0001-setup.py-link-in-
> sysroot-not-in-host-directories.patch "
>  PYPI_PACKAGE = "M2Crypto"
>  inherit pypi setuptools siteinfo
>
> -DEPENDS += "openssl swig-native"
> +DEPENDS += "openssl swig-native python-typing"
>
>  DISTUTILS_BUILD_ARGS += "build_ext --openssl=${STAGING_DIR_HOST}
> -I${STAGING_INCDIR}"
>  DISTUTILS_INSTALL_ARGS += "build_ext --openssl=${STAGING_DIR_HOST}"
> --
> 2.11.0
>
> --
> ___
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


[oe] [meta-python][PATCH 1/2] typing: add version 3.5.3.0

2017-02-02 Thread andreas . kling
From: Andy Kling 

 this is a dependency for m2crypto > 0.24.0
---
 meta-python/recipes-devtools/python/python-typing.inc| 9 +
 meta-python/recipes-devtools/python/python-typing_3.5.3.0.bb | 2 ++
 2 files changed, 11 insertions(+)
 create mode 100644 meta-python/recipes-devtools/python/python-typing.inc
 create mode 100644 meta-python/recipes-devtools/python/python-typing_3.5.3.0.bb

diff --git a/meta-python/recipes-devtools/python/python-typing.inc 
b/meta-python/recipes-devtools/python/python-typing.inc
new file mode 100644
index 0..49da4feb1
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python-typing.inc
@@ -0,0 +1,9 @@
+SUMMARY = "Simple Python module defined by PEP 484."
+HOMEPAGE = "https://github.com/python/typing";
+LICENSE = "PSF"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=64fc2b30b67d0a8423c250e0386ed72f"
+
+SRC_URI[md5sum] = "3996a747158e5591abf689c1c5f8f9db"
+SRC_URI[sha256sum] = 
"ca2daac7e393e8ee86e9140cd0cf0172ff6bb50ebdf0b06281770f98f31bff21"
+
+BBCLASSEXTEND = "native nativesdk"
diff --git a/meta-python/recipes-devtools/python/python-typing_3.5.3.0.bb 
b/meta-python/recipes-devtools/python/python-typing_3.5.3.0.bb
new file mode 100644
index 0..04ce063c9
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python-typing_3.5.3.0.bb
@@ -0,0 +1,2 @@
+inherit pypi setuptools
+require python-typing.inc
-- 
2.11.0

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


[oe] [meta-python][PATCH 2/2] m2crypto: depend on typing

2017-02-02 Thread andreas . kling
From: Andy Kling 

  m2crypto requires typing since 0.24.0-38-g8bbd0ec
---
 meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb 
b/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
index 5a9594f07..ca462229e 100644
--- a/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
+++ b/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
@@ -12,7 +12,7 @@ SRC_URI += 
"file://0001-setup.py-link-in-sysroot-not-in-host-directories.patch "
 PYPI_PACKAGE = "M2Crypto"
 inherit pypi setuptools siteinfo
 
-DEPENDS += "openssl swig-native"
+DEPENDS += "openssl swig-native python-typing"
 
 DISTUTILS_BUILD_ARGS += "build_ext --openssl=${STAGING_DIR_HOST} 
-I${STAGING_INCDIR}"
 DISTUTILS_INSTALL_ARGS += "build_ext --openssl=${STAGING_DIR_HOST}"
-- 
2.11.0

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


Re: [oe] [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds

2017-02-02 Thread Jacobo Aragunde Pérez
On 02/02/17 13:46, Herve Jourdain wrote:
> Hi Jacobo,
> 
> I'm using "master", and I do have patches for enabling armv7ve. But since
> they're needed only for raspberrypi, I planned to submit them only for
> meta-raspberrypi.
> If you think it could be useful in meta-browser, though, I can submit them 
> there.
> 

Oh, I think sending them to meta-rpi would be good enough, thank you!
I'll keep an eye on it.

Best regards,
-- 
Jacobo Aragunde
Software Engineer at Igalia


> -Original Message-
> From: Jacobo Aragunde Pérez [mailto:jaragu...@igalia.com] 
> Sent: jeudi 2 février 2017 13:30
> To: openembedded-devel@lists.openembedded.org
> Cc: ota...@ossystems.com.br; Herve Jourdain 
> Subject: Re: [meta-browser][PATCH] chromium-wayland: fix compilation problem 
> on non-X11 builds
> 
> Thank you all for your reviews. This should be the last patch, it addresses 
> Herve's problem when building on a Raspberry Pi.
> 
> Unfortunately, I haven't been able to reproduce his problem myself, but this 
> patch is actually a backport of an upstream patch, so it makes no harm in my 
> opinion.
> 
> Another question, are you using krogoth in you rpi build? I found problems 
> with the declared architecture in releases newer than jethro, it is called 
> "armv7ve" and chromium doesn't build because it expects "armv7a". We could 
> use a patch if you have worked around this problem :)
> 
> Thanks again,
> --
> Jacobo Aragunde
> Software Engineer at Igalia
> 
> 
> On 02/02/17 13:17, Jacobo Aragunde Pérez wrote:
>> Certain build configurations enable a code path that includes
>> keyboard_code_conversion_xkb.cc, but it eventually fails in non-X11
>> environments because of a missing patch that is present upstream.
>>
>> This commit adds the missing patch from
>> https://codereview.chromium.org/2239833003
>>
>> There are two versions of the patch in the code review URL above.
>> The first version fixes the problem both under the gyp and GN build
>> systems. That patch was rejected because gyp is considered deprecated
>> upstream. The second version fixes the problem only on GN and it was
>> merged upstream. We are picking the first version because our recipes
>> still use gyp to build.
>>
>> Signed-off-by: Jacobo Aragunde Pérez 
>> ---
>>  .../chromium/chromium-wayland_53.0.2785.143.bb |  1 +
>>  .../fix-non-x11-build-when-use_xkbcommon-1.patch   | 51 
>> ++
>>  2 files changed, 52 insertions(+)
>>  create mode 100644 
>> recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
>>
>> diff --git a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb 
>> b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
>> index a75918b..ef913a7 100644
>> --- a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
>> +++ b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
>> @@ -13,6 +13,7 @@ SRC_URI += "\
>>  file://chromium-wayland/0011-Replace-readdir_r-with-readdir.patch \
>>  file://chromium-wayland/remove-Werror.patch \
>>  file://chromium-wayland/guard-x11_desktop_handler-inclusion.patch \
>> +
>> file://chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch \
>>  ${@bb.utils.contains('PACKAGECONFIG', 'component-build', 
>> 'file://component-build.gypi', '', d)} \
>>  ${@bb.utils.contains('PACKAGECONFIG', 'ignore-lost-context', 
>> 'file://0001-Remove-accelerated-Canvas-support-from-blacklist.patch', '', 
>> d)} \
>>  "
>> diff --git 
>> a/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
>>  
>> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
>> new file mode 100644
>> index 000..976ece9
>> --- /dev/null
>> +++ 
>> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
>> @@ -0,0 +1,51 @@
>> +From: jbriance 
>> +Subject: keycodes: Fix non-X11 build when use_xkbcommon=1
>> +
>> +Since M51, ui/events/keycodes/xkb_keysym.h follows X11 path, even if
>> +use_xkbcommon=1 is set because USE_XKBCOMMON is not defined, leading
>> +to the following compilation error in this case:
>> +
>> +  In file included from 
>> ../../ui/events/keycodes/keyboard_code_conversion_xkb.h:12:0,
>> +   from 
>> ../../ui/events/keycodes/keyboard_code_conversion_xkb.cc:5:
>> +  ../../ui/events/keycodes/xkb_keysym.h:19:19: fatal error: X11/X.h: No 
>> such file or directory
>> +
>> +BUG=none
>> +
>> +Review-Url: https://codereview.chromium.org/2239833003
>> +--
>> +
>> +Index: ui/events/keycodes/BUILD.gn
>> +diff --git a/ui/events/keycodes/BUILD.gn b/ui/events/keycodes/BUILD.gn
>> +index 
>> 4f2d47c2497d321332c79d0dd4e9007b50c319c7..716c7ed17cc8049ea65b95a5062e7c6e0adc6e48
>>  100644
>> +--- a/ui/events/keycodes/BUILD.gn
>>  b/ui/events/keycodes/BUILD.gn
>> +@@ -17,6 +17,10 @@ source_set("xkb") {
>> + "//base",
>> + "//ui/events:dom_keycode_converter"

Re: [oe] [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds

2017-02-02 Thread Herve Jourdain
And BTW, I'll try to test your patch tomorrow - I'm back now, so I'll have 
access to my build server.

-Original Message-
From: Herve Jourdain [mailto:herve.jourd...@neuf.fr] 
Sent: jeudi 2 février 2017 13:47
To: 'Jacobo Aragunde Pérez' ; 
'openembedded-devel@lists.openembedded.org' 

Cc: 'ota...@ossystems.com.br' 
Subject: RE: [meta-browser][PATCH] chromium-wayland: fix compilation problem on 
non-X11 builds

Hi Jacobo,

I'm using "master", and I do have patches for enabling armv7ve. But since 
they're needed only for raspberrypi, I planned to submit them only for 
meta-raspberrypi.
If you think it could be useful in meta-browser, though, I can submit them 
there.

Cheers,
Herve

-Original Message-
From: Jacobo Aragunde Pérez [mailto:jaragu...@igalia.com]
Sent: jeudi 2 février 2017 13:30
To: openembedded-devel@lists.openembedded.org
Cc: ota...@ossystems.com.br; Herve Jourdain 
Subject: Re: [meta-browser][PATCH] chromium-wayland: fix compilation problem on 
non-X11 builds

Thank you all for your reviews. This should be the last patch, it addresses 
Herve's problem when building on a Raspberry Pi.

Unfortunately, I haven't been able to reproduce his problem myself, but this 
patch is actually a backport of an upstream patch, so it makes no harm in my 
opinion.

Another question, are you using krogoth in you rpi build? I found problems with 
the declared architecture in releases newer than jethro, it is called "armv7ve" 
and chromium doesn't build because it expects "armv7a". We could use a patch if 
you have worked around this problem :)

Thanks again,
--
Jacobo Aragunde
Software Engineer at Igalia


On 02/02/17 13:17, Jacobo Aragunde Pérez wrote:
> Certain build configurations enable a code path that includes 
> keyboard_code_conversion_xkb.cc, but it eventually fails in non-X11 
> environments because of a missing patch that is present upstream.
> 
> This commit adds the missing patch from
> https://codereview.chromium.org/2239833003
> 
> There are two versions of the patch in the code review URL above.
> The first version fixes the problem both under the gyp and GN build 
> systems. That patch was rejected because gyp is considered deprecated 
> upstream. The second version fixes the problem only on GN and it was 
> merged upstream. We are picking the first version because our recipes 
> still use gyp to build.
> 
> Signed-off-by: Jacobo Aragunde Pérez 
> ---
>  .../chromium/chromium-wayland_53.0.2785.143.bb |  1 +
>  .../fix-non-x11-build-when-use_xkbcommon-1.patch   | 51 
> ++
>  2 files changed, 52 insertions(+)
>  create mode 100644 
> recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-w
> hen-use_xkbcommon-1.patch
> 
> diff --git 
> a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb 
> b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
> index a75918b..ef913a7 100644
> --- a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
> +++ b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
> @@ -13,6 +13,7 @@ SRC_URI += "\
>  file://chromium-wayland/0011-Replace-readdir_r-with-readdir.patch \
>  file://chromium-wayland/remove-Werror.patch \
>  
> file://chromium-wayland/guard-x11_desktop_handler-inclusion.patch \
> +
> + file://chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch 
> + \
>  ${@bb.utils.contains('PACKAGECONFIG', 'component-build', 
> 'file://component-build.gypi', '', d)} \
>  ${@bb.utils.contains('PACKAGECONFIG', 'ignore-lost-context', 
> 'file://0001-Remove-accelerated-Canvas-support-from-blacklist.patch', '', d)} 
> \  "
> diff --git 
> a/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build
> -when-use_xkbcommon-1.patch 
> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build
> -when-use_xkbcommon-1.patch
> new file mode 100644
> index 000..976ece9
> --- /dev/null
> +++ b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-b
> +++ uild-when-use_xkbcommon-1.patch
> @@ -0,0 +1,51 @@
> +From: jbriance 
> +Subject: keycodes: Fix non-X11 build when use_xkbcommon=1
> +
> +Since M51, ui/events/keycodes/xkb_keysym.h follows X11 path, even if
> +use_xkbcommon=1 is set because USE_XKBCOMMON is not defined, leading 
> +to the following compilation error in this case:
> +
> +  In file included from 
> ../../ui/events/keycodes/keyboard_code_conversion_xkb.h:12:0,
> +   from 
> ../../ui/events/keycodes/keyboard_code_conversion_xkb.cc:5:
> +  ../../ui/events/keycodes/xkb_keysym.h:19:19: fatal error: X11/X.h: 
> + No such file or directory
> +
> +BUG=none
> +
> +Review-Url: https://codereview.chromium.org/2239833003
> +--
> +
> +Index: ui/events/keycodes/BUILD.gn
> +diff --git a/ui/events/keycodes/BUILD.gn 
> +b/ui/events/keycodes/BUILD.gn index 
> +4f2d47c2497d321332c79d0dd4e9007b50c319c7..716c7ed17cc8049ea65b95a5062
> +e7c6e0adc6e48 100644
> +--- a/ui/events/keycodes/BUILD.gn
>  b/ui/ev

Re: [oe] [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds

2017-02-02 Thread Herve Jourdain
Hi Jacobo,

I'm using "master", and I do have patches for enabling armv7ve. But since 
they're needed only for raspberrypi, I planned to submit them only for 
meta-raspberrypi.
If you think it could be useful in meta-browser, though, I can submit them 
there.

Cheers,
Herve

-Original Message-
From: Jacobo Aragunde Pérez [mailto:jaragu...@igalia.com] 
Sent: jeudi 2 février 2017 13:30
To: openembedded-devel@lists.openembedded.org
Cc: ota...@ossystems.com.br; Herve Jourdain 
Subject: Re: [meta-browser][PATCH] chromium-wayland: fix compilation problem on 
non-X11 builds

Thank you all for your reviews. This should be the last patch, it addresses 
Herve's problem when building on a Raspberry Pi.

Unfortunately, I haven't been able to reproduce his problem myself, but this 
patch is actually a backport of an upstream patch, so it makes no harm in my 
opinion.

Another question, are you using krogoth in you rpi build? I found problems with 
the declared architecture in releases newer than jethro, it is called "armv7ve" 
and chromium doesn't build because it expects "armv7a". We could use a patch if 
you have worked around this problem :)

Thanks again,
--
Jacobo Aragunde
Software Engineer at Igalia


On 02/02/17 13:17, Jacobo Aragunde Pérez wrote:
> Certain build configurations enable a code path that includes
> keyboard_code_conversion_xkb.cc, but it eventually fails in non-X11
> environments because of a missing patch that is present upstream.
> 
> This commit adds the missing patch from
> https://codereview.chromium.org/2239833003
> 
> There are two versions of the patch in the code review URL above.
> The first version fixes the problem both under the gyp and GN build
> systems. That patch was rejected because gyp is considered deprecated
> upstream. The second version fixes the problem only on GN and it was
> merged upstream. We are picking the first version because our recipes
> still use gyp to build.
> 
> Signed-off-by: Jacobo Aragunde Pérez 
> ---
>  .../chromium/chromium-wayland_53.0.2785.143.bb |  1 +
>  .../fix-non-x11-build-when-use_xkbcommon-1.patch   | 51 
> ++
>  2 files changed, 52 insertions(+)
>  create mode 100644 
> recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
> 
> diff --git a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb 
> b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
> index a75918b..ef913a7 100644
> --- a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
> +++ b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
> @@ -13,6 +13,7 @@ SRC_URI += "\
>  file://chromium-wayland/0011-Replace-readdir_r-with-readdir.patch \
>  file://chromium-wayland/remove-Werror.patch \
>  file://chromium-wayland/guard-x11_desktop_handler-inclusion.patch \
> +file://chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch 
> \
>  ${@bb.utils.contains('PACKAGECONFIG', 'component-build', 
> 'file://component-build.gypi', '', d)} \
>  ${@bb.utils.contains('PACKAGECONFIG', 'ignore-lost-context', 
> 'file://0001-Remove-accelerated-Canvas-support-from-blacklist.patch', '', d)} 
> \
>  "
> diff --git 
> a/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
>  
> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
> new file mode 100644
> index 000..976ece9
> --- /dev/null
> +++ 
> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
> @@ -0,0 +1,51 @@
> +From: jbriance 
> +Subject: keycodes: Fix non-X11 build when use_xkbcommon=1
> +
> +Since M51, ui/events/keycodes/xkb_keysym.h follows X11 path, even if
> +use_xkbcommon=1 is set because USE_XKBCOMMON is not defined, leading
> +to the following compilation error in this case:
> +
> +  In file included from 
> ../../ui/events/keycodes/keyboard_code_conversion_xkb.h:12:0,
> +   from 
> ../../ui/events/keycodes/keyboard_code_conversion_xkb.cc:5:
> +  ../../ui/events/keycodes/xkb_keysym.h:19:19: fatal error: X11/X.h: No such 
> file or directory
> +
> +BUG=none
> +
> +Review-Url: https://codereview.chromium.org/2239833003
> +--
> +
> +Index: ui/events/keycodes/BUILD.gn
> +diff --git a/ui/events/keycodes/BUILD.gn b/ui/events/keycodes/BUILD.gn
> +index 
> 4f2d47c2497d321332c79d0dd4e9007b50c319c7..716c7ed17cc8049ea65b95a5062e7c6e0adc6e48
>  100644
> +--- a/ui/events/keycodes/BUILD.gn
>  b/ui/events/keycodes/BUILD.gn
> +@@ -17,6 +17,10 @@ source_set("xkb") {
> + "//base",
> + "//ui/events:dom_keycode_converter",
> +   ]
> ++
> ++  if (use_xkbcommon) {
> ++defines = [ "USE_XKBCOMMON" ]
> ++  }
> + }
> + 
> + if (use_x11 || ozone_platform_x11) {
> +Index: ui/events/keycodes/events_keycodes.gyp
> +diff --git a/ui/events/keycodes/events_keycodes.gyp 
> b/ui/events/keycodes/events_keycodes.gyp
> +index 
> b0796b4e2ead8bffe88fb01ed1368

Re: [oe] [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds

2017-02-02 Thread Jacobo Aragunde Pérez
Thank you all for your reviews. This should be the last patch, it
addresses Herve's problem when building on a Raspberry Pi.

Unfortunately, I haven't been able to reproduce his problem myself, but
this patch is actually a backport of an upstream patch, so it makes no
harm in my opinion.

Another question, are you using krogoth in you rpi build? I found
problems with the declared architecture in releases newer than jethro,
it is called "armv7ve" and chromium doesn't build because it expects
"armv7a". We could use a patch if you have worked around this problem :)

Thanks again,
-- 
Jacobo Aragunde
Software Engineer at Igalia


On 02/02/17 13:17, Jacobo Aragunde Pérez wrote:
> Certain build configurations enable a code path that includes
> keyboard_code_conversion_xkb.cc, but it eventually fails in non-X11
> environments because of a missing patch that is present upstream.
> 
> This commit adds the missing patch from
> https://codereview.chromium.org/2239833003
> 
> There are two versions of the patch in the code review URL above.
> The first version fixes the problem both under the gyp and GN build
> systems. That patch was rejected because gyp is considered deprecated
> upstream. The second version fixes the problem only on GN and it was
> merged upstream. We are picking the first version because our recipes
> still use gyp to build.
> 
> Signed-off-by: Jacobo Aragunde Pérez 
> ---
>  .../chromium/chromium-wayland_53.0.2785.143.bb |  1 +
>  .../fix-non-x11-build-when-use_xkbcommon-1.patch   | 51 
> ++
>  2 files changed, 52 insertions(+)
>  create mode 100644 
> recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
> 
> diff --git a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb 
> b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
> index a75918b..ef913a7 100644
> --- a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
> +++ b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
> @@ -13,6 +13,7 @@ SRC_URI += "\
>  file://chromium-wayland/0011-Replace-readdir_r-with-readdir.patch \
>  file://chromium-wayland/remove-Werror.patch \
>  file://chromium-wayland/guard-x11_desktop_handler-inclusion.patch \
> +file://chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch 
> \
>  ${@bb.utils.contains('PACKAGECONFIG', 'component-build', 
> 'file://component-build.gypi', '', d)} \
>  ${@bb.utils.contains('PACKAGECONFIG', 'ignore-lost-context', 
> 'file://0001-Remove-accelerated-Canvas-support-from-blacklist.patch', '', d)} 
> \
>  "
> diff --git 
> a/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
>  
> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
> new file mode 100644
> index 000..976ece9
> --- /dev/null
> +++ 
> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
> @@ -0,0 +1,51 @@
> +From: jbriance 
> +Subject: keycodes: Fix non-X11 build when use_xkbcommon=1
> +
> +Since M51, ui/events/keycodes/xkb_keysym.h follows X11 path, even if
> +use_xkbcommon=1 is set because USE_XKBCOMMON is not defined, leading
> +to the following compilation error in this case:
> +
> +  In file included from 
> ../../ui/events/keycodes/keyboard_code_conversion_xkb.h:12:0,
> +   from 
> ../../ui/events/keycodes/keyboard_code_conversion_xkb.cc:5:
> +  ../../ui/events/keycodes/xkb_keysym.h:19:19: fatal error: X11/X.h: No such 
> file or directory
> +
> +BUG=none
> +
> +Review-Url: https://codereview.chromium.org/2239833003
> +--
> +
> +Index: ui/events/keycodes/BUILD.gn
> +diff --git a/ui/events/keycodes/BUILD.gn b/ui/events/keycodes/BUILD.gn
> +index 
> 4f2d47c2497d321332c79d0dd4e9007b50c319c7..716c7ed17cc8049ea65b95a5062e7c6e0adc6e48
>  100644
> +--- a/ui/events/keycodes/BUILD.gn
>  b/ui/events/keycodes/BUILD.gn
> +@@ -17,6 +17,10 @@ source_set("xkb") {
> + "//base",
> + "//ui/events:dom_keycode_converter",
> +   ]
> ++
> ++  if (use_xkbcommon) {
> ++defines = [ "USE_XKBCOMMON" ]
> ++  }
> + }
> + 
> + if (use_x11 || ozone_platform_x11) {
> +Index: ui/events/keycodes/events_keycodes.gyp
> +diff --git a/ui/events/keycodes/events_keycodes.gyp 
> b/ui/events/keycodes/events_keycodes.gyp
> +index 
> b0796b4e2ead8bffe88fb01ed136814be505d967..248e961bad2ad3996ca99624b6c489c7835f6241
>  100644
> +--- a/ui/events/keycodes/events_keycodes.gyp
>  b/ui/events/keycodes/events_keycodes.gyp
> +@@ -21,6 +21,13 @@
> + 'scoped_xkb.h',
> + 'xkb_keysym.h',
> +   ],
> ++  'conditions': [
> ++['use_xkbcommon==1', {
> ++  'defines': [
> ++'USE_XKBCOMMON',
> ++  ],
> ++}],
> ++  ],
> + },
> +   ],
> +   'conditions': [
> 


-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.o

[oe] [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds

2017-02-02 Thread Jacobo Aragunde Pérez
Certain build configurations enable a code path that includes
keyboard_code_conversion_xkb.cc, but it eventually fails in non-X11
environments because of a missing patch that is present upstream.

This commit adds the missing patch from
https://codereview.chromium.org/2239833003

There are two versions of the patch in the code review URL above.
The first version fixes the problem both under the gyp and GN build
systems. That patch was rejected because gyp is considered deprecated
upstream. The second version fixes the problem only on GN and it was
merged upstream. We are picking the first version because our recipes
still use gyp to build.

Signed-off-by: Jacobo Aragunde Pérez 
---
 .../chromium/chromium-wayland_53.0.2785.143.bb |  1 +
 .../fix-non-x11-build-when-use_xkbcommon-1.patch   | 51 ++
 2 files changed, 52 insertions(+)
 create mode 100644 
recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch

diff --git a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb 
b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
index a75918b..ef913a7 100644
--- a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
+++ b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
@@ -13,6 +13,7 @@ SRC_URI += "\
 file://chromium-wayland/0011-Replace-readdir_r-with-readdir.patch \
 file://chromium-wayland/remove-Werror.patch \
 file://chromium-wayland/guard-x11_desktop_handler-inclusion.patch \
+file://chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch \
 ${@bb.utils.contains('PACKAGECONFIG', 'component-build', 
'file://component-build.gypi', '', d)} \
 ${@bb.utils.contains('PACKAGECONFIG', 'ignore-lost-context', 
'file://0001-Remove-accelerated-Canvas-support-from-blacklist.patch', '', d)} \
 "
diff --git 
a/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
 
b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
new file mode 100644
index 000..976ece9
--- /dev/null
+++ 
b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch
@@ -0,0 +1,51 @@
+From: jbriance 
+Subject: keycodes: Fix non-X11 build when use_xkbcommon=1
+
+Since M51, ui/events/keycodes/xkb_keysym.h follows X11 path, even if
+use_xkbcommon=1 is set because USE_XKBCOMMON is not defined, leading
+to the following compilation error in this case:
+
+  In file included from 
../../ui/events/keycodes/keyboard_code_conversion_xkb.h:12:0,
+   from 
../../ui/events/keycodes/keyboard_code_conversion_xkb.cc:5:
+  ../../ui/events/keycodes/xkb_keysym.h:19:19: fatal error: X11/X.h: No such 
file or directory
+
+BUG=none
+
+Review-Url: https://codereview.chromium.org/2239833003
+--
+
+Index: ui/events/keycodes/BUILD.gn
+diff --git a/ui/events/keycodes/BUILD.gn b/ui/events/keycodes/BUILD.gn
+index 
4f2d47c2497d321332c79d0dd4e9007b50c319c7..716c7ed17cc8049ea65b95a5062e7c6e0adc6e48
 100644
+--- a/ui/events/keycodes/BUILD.gn
 b/ui/events/keycodes/BUILD.gn
+@@ -17,6 +17,10 @@ source_set("xkb") {
+ "//base",
+ "//ui/events:dom_keycode_converter",
+   ]
++
++  if (use_xkbcommon) {
++defines = [ "USE_XKBCOMMON" ]
++  }
+ }
+ 
+ if (use_x11 || ozone_platform_x11) {
+Index: ui/events/keycodes/events_keycodes.gyp
+diff --git a/ui/events/keycodes/events_keycodes.gyp 
b/ui/events/keycodes/events_keycodes.gyp
+index 
b0796b4e2ead8bffe88fb01ed136814be505d967..248e961bad2ad3996ca99624b6c489c7835f6241
 100644
+--- a/ui/events/keycodes/events_keycodes.gyp
 b/ui/events/keycodes/events_keycodes.gyp
+@@ -21,6 +21,13 @@
+ 'scoped_xkb.h',
+ 'xkb_keysym.h',
+   ],
++  'conditions': [
++['use_xkbcommon==1', {
++  'defines': [
++'USE_XKBCOMMON',
++  ],
++}],
++  ],
+ },
+   ],
+   'conditions': [
-- 
2.7.4

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


[oe] State of bitbake world, Failed tasks 2017-02-01

2017-02-02 Thread Martin Jansa
On Tue, Jan 31, 2017 at 06:10:49PM +0100, Martin Jansa wrote:
> There is a lot more failures this time (mostly because of RSS), but
> I wanted to share it anyway, to be clear about the current state of
> other layers.
> :

Still a lot of failures, I've updated the report script to stop
processing test-dependencies jenkins jobs, so it's a bit shorter now,
I've sent fixes for firefox*, geoclue and vboxguestdrivers, so next
report shouls be at least 50 lines shorter as well.

== Number of issues - stats ==
{| class='wikitable'
!|Date   !!colspan='3'|Failed tasks 
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='12'|QA !!Comment
|-
||  ||qemuarm   ||qemux86   ||qemux86_64
||qemuarm||max||min ||qemux86||max||min ||all   ||already-stripped  
||libdir||textrel   ||build-deps||file-rdeps
||version-going-backwards   ||host-user-contaminated
||installed-vs-shipped  ||unknown-configure-option  ||symlink-to-sysroot
||invalid-pkgconfig ||pkgname   ||  
|-
||2017-02-01||178   ||184   ||182   ||N/A   ||N/A   ||N/A   ||N/A   ||N/A   
||N/A   ||0 ||0 ||0 ||2 ||0 
||6 ||156   ||0 ||2 ||0 
||0 ||0 ||0 ||  
|}

http://www.openembedded.org/wiki/Bitbake_World_Status

== Failed tasks 2017-02-01 ==

INFO: jenkins-job.sh-1.8.15 Complete log available at 
http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170202_004847.log

=== common (176) ===
* 
meta-browser/recipes-mozilla/firefox-addon/firefox-addon-webconverger_git.bb:do_configure
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-ach_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-af_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-an_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-ar_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-as_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-ast_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-az_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-be_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-bg_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-bn-bd_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-bn-in_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-br_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-bs_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-ca_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-cs_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-cy_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-da_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-de_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-dsb_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-el_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-en-gb_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-en-us_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-en-za_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-eo_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-es-ar_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-es-cl_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-es-es_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-es-mx_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-et_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-eu_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-fa_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-ff_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-fi_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-fr_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-fy-nl_45.6.0esr.bb:do_install
* 
meta-browser/recipes-mozilla/firefox-l10n/firefox-l10n-ga-ie_45.6.0esr.bb:do_in