Re: [oe] [meta-networking][PATCH] geoip: add downloadfilename for geoip database files

2018-11-28 Thread Martin Jansa
Thanks for update.

So there will be 4 more changes and then after:
"Starting January 2, 2019, the last build will be removed from our website."
the archive will be only on OE premirror? That's really unfortunate, I'm
not using geoip (other than seeing it fail in my world builds), but this
will be big issue for people using release branches and not the premirror,
we should at least synchronize all branches to use the same archives and in
a month we should mirror the very last build in some more stable place, I
haven't check the license, but cannot YP mirror host the files from the
very last build?

On Thu, Nov 29, 2018 at 2:31 AM Changqing Li 
wrote:

> Khem and Marthin,
>
> The failure still caused by frequently changed checksum of the database. I
> send the patch on 11.20.
>
> but the checksum changed on 1121, and it also changed on 1128, seems like
> weekly change.
>
> but it should not failed if there is a premirror saved the
>
> Here is a result I get:
>
> $ md5sum 1128/*v6*
> d98a04eded0b08b945b5629106d58760  1128/GeoIPv6 (1).dat.gz
> 4d48c102ec68298b3fc7f57763455cb5  1128/GeoLiteCityv6.dat.gz
> $ md5sum 1121/*v6*
> b0f82334f94ca89872e7722db3511bb9  1121/GeoIPv6.dat.gz
> 50ad18a8a3ea4bba7c929bea6e22db75  1121/GeoLiteCityv6.dat.gz
> $ md5sum 1120/*v6*
> a908d7a51c3883eb8f693ca197c7a142  1120/GeoIPv6.dat.gz
> 8ac3506ccabaae7e9f7d6301c2654313  1120/GeoLiteCityv6.dat.gz
>
>
> On 11/28/18 3:14 AM, Martin Jansa wrote:
>
> I'm seeing different checksum than both your builder and the recipe.
>
> $ wget http://geolite.maxmind.com/download/geoip/database/GeoIPv6.dat.gz
> --2018-11-27 20:06:32--
> http://geolite.maxmind.com/download/geoip/database/GeoIPv6.dat.gz
> Resolving geolite.maxmind.com... 104.16.37.47, 104.16.38.47,
> 2606:4700::6810:252f, ...
> Connecting to geolite.maxmind.com|104.16.37.47|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 1209046 (1.2M) [application/octet-stream]
> Saving to: ‘GeoIPv6.dat.gz’
>
> 2018-11-27 20:06:32 (10.3 MB/s) - ‘GeoIPv6.dat.gz’ saved [1209046/1209046]
>
> $ md5sum GeoIPv6.dat.gz
> d98a04eded0b08b945b5629106d58760  GeoIPv6.dat.gz
>
> Is this the legacy archive? Because
> https://dev.maxmind.com/geoip/legacy/geolite/ now shows following:
>
> Yes,  I have  pointed out this problem  the first time I changed the
> checksum. maybe we should upgrade
>
> to geoip2,  and  drop current geoip1.6.  but I think even with geoip2,
> since it's database still not version,
>
> maybe also will met similar problem.
>
>
> //changqing
>
>
> Updated versions of the GeoLite Legacy databases are now only available to
> redistribution license customers, although anyone can continue to download
> the March 2018 GeoLite Legacy builds. Starting January 2, 2019, the last
> build will be removed from our website. GeoLite Legacy database users will
> need to switch to the GeoLite2 or commercial GeoIP databases and update
> their integrations by January 2, 2019.
>
> For more information, please visit our Support Center.
>
> Note: After careful consideration, taking into account customer feedback,
> we have decided against removing latitude and longitude coordinates from
> the GeoLite2 databases. We are in the process of reviewing coordinates used
> in all of our GeoLite2 and GeoIP databases to ensure there is no risk of
> misuse.
>
> * GeoLite2 databases are free IP geolocation databases comparable to, but
> less accurate than, MaxMind’s GeoIP2 databases. Please remember to use the
> accuracy radius if displaying coordinates on a map.
>
> New Database Format Available: This page is for our GeoLite Legacy
> databases. For our latest database format, please visit our GeoLite2
> Databases page. We offer redistribution licenses for our newer GeoLite2
> databases that will allow you to package the databases with your commercial
> products. For more information, please visit the GeoLite2 Commercial
> Redistribution page.
>
>
> On Tue, Nov 27, 2018 at 8:04 PM Khem Raj  wrote:
>
>> I am seeing errors on some builders
>>
>> http://errors.yoctoproject.org/Errors/Details/202341/
>> On Mon, Nov 19, 2018 at 11:29 PM Martin Jansa 
>> wrote:
>> >
>> > Looks, good.
>> >
>> > Adding variable for 20181120 might help with maintenance (if we need to
>> > change just checksums in future). And with good variable name (or a
>> > comment) it would also document in the recipe why we're using this in
>> > downloadfilename.
>> >
>> > On Tue, Nov 20, 2018 at 7:48 AM  wrote:
>> >
>> > > From: Changqing Li 
>> > >
>> > > previous change of checksum don't trigger archive to re-downloaded,
>> > > , which will cause checksum mismatch. add downloadfilename to
>> > > trigger re-download.
>> > >
>> > > 1. for user with PREMIRROR, another benefit is it can still compile
>> > > success event upstream checksum change frequently.
>> > > 2. but for user don't use PREMIRROR, if upstream checksum changed,
>> > > still might have checksum mismatch problem.
>> > >
>> > > Signed-off-by: Changqing Li 
>> > > ---
>> 

Re: [oe] [meta-networking][PATCH] geoip: add downloadfilename for geoip database files

2018-11-28 Thread Changqing Li

Khem and Marthin,

The failure still caused by frequently changed checksum of the database. 
I send the patch on 11.20.


but the checksum changed on 1121, and it also changed on 1128, seems 
like weekly change.


but it should not failed if there is a premirror saved the

Here is a result I get:

$ md5sum 1128/*v6*
d98a04eded0b08b945b5629106d58760  1128/GeoIPv6 (1).dat.gz
4d48c102ec68298b3fc7f57763455cb5  1128/GeoLiteCityv6.dat.gz
$ md5sum 1121/*v6*
b0f82334f94ca89872e7722db3511bb9  1121/GeoIPv6.dat.gz
50ad18a8a3ea4bba7c929bea6e22db75  1121/GeoLiteCityv6.dat.gz
$ md5sum 1120/*v6*
a908d7a51c3883eb8f693ca197c7a142  1120/GeoIPv6.dat.gz
8ac3506ccabaae7e9f7d6301c2654313  1120/GeoLiteCityv6.dat.gz


On 11/28/18 3:14 AM, Martin Jansa wrote:

I'm seeing different checksum than both your builder and the recipe.

$ wget http://geolite.maxmind.com/download/geoip/database/GeoIPv6.dat.gz
--2018-11-27 20:06:32-- 
http://geolite.maxmind.com/download/geoip/database/GeoIPv6.dat.gz
Resolving geolite.maxmind.com... 104.16.37.47, 104.16.38.47, 
2606:4700::6810:252f, ...
Connecting to geolite.maxmind.com 
|104.16.37.47|:80... connected.

HTTP request sent, awaiting response... 200 OK
Length: 1209046 (1.2M) [application/octet-stream]
Saving to: ‘GeoIPv6.dat.gz’

2018-11-27 20:06:32 (10.3 MB/s) - ‘GeoIPv6.dat.gz’ saved [1209046/1209046]

$ md5sum GeoIPv6.dat.gz
d98a04eded0b08b945b5629106d58760 GeoIPv6.dat.gz

Is this the legacy archive? Because 
https://dev.maxmind.com/geoip/legacy/geolite/ now shows following:


Yes,  I have  pointed out this problem  the first time I changed the 
checksum. maybe we should upgrade


to geoip2,  and  drop current geoip1.6.  but I think even with geoip2,  
since it's database still not version,


maybe also will met similar problem.


//changqing



Updated versions of the GeoLite Legacy databases are now only 
available to redistribution license customers, although anyone can 
continue to download the March 2018 GeoLite Legacy builds. Starting 
January 2, 2019, the last build will be removed from our website. 
GeoLite Legacy database users will need to switch to the GeoLite2 or 
commercial GeoIP databases and update their integrations by January 2, 
2019.


For more information, please visit our Support Center.

Note: After careful consideration, taking into account customer 
feedback, we have decided against removing latitude and longitude 
coordinates from the GeoLite2 databases. We are in the process of 
reviewing coordinates used in all of our GeoLite2 and GeoIP databases 
to ensure there is no risk of misuse.


* GeoLite2 databases are free IP geolocation databases comparable to, 
but less accurate than, MaxMind’s GeoIP2 databases. Please remember to 
use the accuracy radius if displaying coordinates on a map.


New Database Format Available: This page is for our GeoLite Legacy 
databases. For our latest database format, please visit our GeoLite2 
Databases page. We offer redistribution licenses for our newer 
GeoLite2 databases that will allow you to package the databases with 
your commercial products. For more information, please visit the 
GeoLite2 Commercial Redistribution page.



On Tue, Nov 27, 2018 at 8:04 PM Khem Raj > wrote:


I am seeing errors on some builders

http://errors.yoctoproject.org/Errors/Details/202341/
On Mon, Nov 19, 2018 at 11:29 PM Martin Jansa
mailto:martin.ja...@gmail.com>> wrote:
>
> Looks, good.
>
> Adding variable for 20181120 might help with maintenance (if we
need to
> change just checksums in future). And with good variable name (or a
> comment) it would also document in the recipe why we're using
this in
> downloadfilename.
>
> On Tue, Nov 20, 2018 at 7:48 AM mailto:changqing...@windriver.com>> wrote:
>
> > From: Changqing Li mailto:changqing...@windriver.com>>
> >
> > previous change of checksum don't trigger archive to
re-downloaded,
> > , which will cause checksum mismatch. add downloadfilename to
> > trigger re-download.
> >
> > 1. for user with PREMIRROR, another benefit is it can still
compile
> > success event upstream checksum change frequently.
> > 2. but for user don't use PREMIRROR, if upstream checksum changed,
> > still might have checksum mismatch problem.
> >
> > Signed-off-by: Changqing Li mailto:changqing...@windriver.com>>
> > ---
> >  .../recipes-support/geoip/geoip_1.6.12.bb
         | 24
> > +++---
> >  1 file changed, 12 insertions(+), 12 deletions(-)
> >
> > diff --git
a/meta-networking/recipes-support/geoip/geoip_1.6.12.bb

> > b/meta-networking/recipes-support/geoip/geoip_1.6.12.bb

> > index 1e1a7ff..57f0b67 100644
> > --- a/meta-networking/recipes-support/geoip/geoip_1.6.12.bb

> > 

[oe] [meta-networking][PATCH V2] autofs: upgrade to 5.1.5

2018-11-28 Thread changqing.li
From: Changqing Li 

Signed-off-by: Changqing Li 
---
 .../0001-Do-not-hardcode-path-for-pkg.m4.patch | 19 +++--
 .../0002-Replace-__S_IEXEC-with-S_IEXEC.patch  | 36 ++---
 .../autofs-5.0.7-do-not-check-for-modprobe.patch   | 89 --
 .../autofs/autofs/pkgconfig-libnsl.patch   | 35 +
 ...-pkg-config-to-detect-libxml-2.0-and-krb5.patch | 24 --
 .../autofs/{autofs_5.1.4.bb => autofs_5.1.5.bb}| 10 ++-
 6 files changed, 83 insertions(+), 130 deletions(-)
 delete mode 100644 
meta-networking/recipes-daemons/autofs/autofs/autofs-5.0.7-do-not-check-for-modprobe.patch
 rename meta-networking/recipes-daemons/autofs/{autofs_5.1.4.bb => 
autofs_5.1.5.bb} (90%)

diff --git 
a/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
 
b/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
index f3f25f4..410827b 100644
--- 
a/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
+++ 
b/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
@@ -1,21 +1,26 @@
-From 6d24365f0828185fd1bb4d199209ca07eb95c41d Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Fri, 24 Aug 2018 06:24:36 +
-Subject: [PATCH] Do not hardcode path for pkg.m4
+From a27217a5437da313d251b4a765bf7cb60ffaa62d Mon Sep 17 00:00:00 2001
+From: Changqing Li 
+Date: Tue, 27 Nov 2018 15:27:47 +0800
+Subject: [PATCH] From 6d24365f0828185fd1bb4d199209ca07eb95c41d Mon Sep 17
+ 00:00:00 2001 From: Khem Raj  Date: Fri, 24 Aug 2018
+ 06:24:36 + Subject: [PATCH] Do not hardcode path for pkg.m4
 
 Upstream-Status: Pending
 
 Signed-off-by: Khem Raj 
+
+update patch to version 5.1.5
+Signed-off-by: Changqing Li 
 ---
  configure.in | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/configure.in b/configure.in
-index 50aed15..f81767c 100644
+index 493b9f1..268d06b 100644
 --- a/configure.in
 +++ b/configure.in
 @@ -12,7 +12,7 @@ define([AC_CACHE_SAVE], )dnl
- AC_INIT(.autofs-5.1.4)
+ AC_INIT(.autofs-5.1.5)
  
  # for pkg-config macros
 -m4_include([/usr/share/aclocal/pkg.m4])
@@ -24,5 +29,5 @@ index 50aed15..f81767c 100644
  #
  # autofs installs by default in /usr
 -- 
-1.9.1
+2.7.4
 
diff --git 
a/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch
 
b/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch
index 469027a..e7fdd10 100644
--- 
a/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch
+++ 
b/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch
@@ -1,22 +1,26 @@
-From 557ca399f4b3a397f20bb147ec6dc4ab9732dd1e Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Fri, 31 Mar 2017 19:12:10 -0700
-Subject: [PATCH] Replace __S_IEXEC with S_IEXEC
+From 096e33743158e0e8c04d60d01cc66e2945d79777 Mon Sep 17 00:00:00 2001
+From: Changqing Li 
+Date: Tue, 27 Nov 2018 16:52:35 +0800
+Subject: [PATCH] From 557ca399f4b3a397f20bb147ec6dc4ab9732dd1e Mon Sep 17
+ 00:00:00 2001 From: Khem Raj  Date: Fri, 31 Mar 2017
+ 19:12:10 -0700 Subject: [PATCH] Replace __S_IEXEC with S_IEXEC
 
 S_IEXEC is portable
 
 Signed-off-by: Khem Raj 
 
+update patch to version 5.1.5
+Signed-off-by: Changqing Li 
 ---
- daemon/lookup.c| 4 ++--
+ daemon/lookup.c| 6 +++---
  modules/lookup_multi.c | 2 +-
- 2 files changed, 3 insertions(+), 3 deletions(-)
+ 2 files changed, 4 insertions(+), 4 deletions(-)
 
 diff --git a/daemon/lookup.c b/daemon/lookup.c
-index 201ccbb..d821db8 100644
+index 18df935..d35d484 100644
 --- a/daemon/lookup.c
 +++ b/daemon/lookup.c
-@@ -366,7 +366,7 @@ static int read_file_source_instance(struct autofs_point 
*ap, struct map_source
+@@ -382,7 +382,7 @@ static int read_file_source_instance(struct autofs_point 
*ap, struct map_source
if (!S_ISREG(st.st_mode))
return NSS_STATUS_NOTFOUND;
  
@@ -25,7 +29,7 @@ index 201ccbb..d821db8 100644
type = src_prog;
else
type = src_file;
-@@ -856,7 +856,7 @@ static int lookup_name_file_source_instance(struct 
autofs_point *ap, struct map_
+@@ -942,7 +942,7 @@ static int lookup_name_file_source_instance(struct 
autofs_point *ap, struct map_
if (!S_ISREG(st.st_mode))
return NSS_STATUS_NOTFOUND;
  
@@ -34,8 +38,17 @@ index 201ccbb..d821db8 100644
type = src_prog;
else
type = src_file;
+@@ -1118,7 +1118,7 @@ static struct map_source *lookup_get_map_source(struct 
master_mapent *entry)
+   if (!S_ISREG(st.st_mode))
+   return NULL;
+ 
+-  if (st.st_mode & __S_IEXEC)
++  if (st.st_mode & S_IEXEC)
+   type = "program";
+   else
+   type = "file";
 diff --git a/modules/lookup_multi.c b/modules/lookup_multi.c
-index fadd2ea..3ecda6d 100644
+index bb9f88c..cf109de 100644
 --- a/modules/lookup_multi.c
 +++ 

Re: [oe] [meta-networking][PATCH V2] autofs: upgrade to 5.1.5

2018-11-28 Thread Changqing Li



On 11/29/18 10:53 AM, changqing...@windriver.com wrote:

From: Changqing Li 

Signed-off-by: Changqing Li 
---
  .../0001-Do-not-hardcode-path-for-pkg.m4.patch | 19 +++--
  .../0002-Replace-__S_IEXEC-with-S_IEXEC.patch  | 36 ++---
  .../autofs-5.0.7-do-not-check-for-modprobe.patch   | 89 --
  .../autofs/autofs/pkgconfig-libnsl.patch   | 35 +
  ...-pkg-config-to-detect-libxml-2.0-and-krb5.patch | 24 --
  .../autofs/{autofs_5.1.4.bb => autofs_5.1.5.bb}| 10 ++-
  6 files changed, 83 insertions(+), 130 deletions(-)
  delete mode 100644 
meta-networking/recipes-daemons/autofs/autofs/autofs-5.0.7-do-not-check-for-modprobe.patch
  rename meta-networking/recipes-daemons/autofs/{autofs_5.1.4.bb => 
autofs_5.1.5.bb} (90%)

diff --git 
a/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
 
b/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
index f3f25f4..410827b 100644
--- 
a/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
+++ 
b/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
@@ -1,21 +1,26 @@
-From 6d24365f0828185fd1bb4d199209ca07eb95c41d Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Fri, 24 Aug 2018 06:24:36 +
-Subject: [PATCH] Do not hardcode path for pkg.m4
+From a27217a5437da313d251b4a765bf7cb60ffaa62d Mon Sep 17 00:00:00 2001
+From: Changqing Li 
+Date: Tue, 27 Nov 2018 15:27:47 +0800
+Subject: [PATCH] From 6d24365f0828185fd1bb4d199209ca07eb95c41d Mon Sep 17
+ 00:00:00 2001 From: Khem Raj  Date: Fri, 24 Aug 2018
+ 06:24:36 + Subject: [PATCH] Do not hardcode path for pkg.m4
  
  Upstream-Status: Pending
  
  Signed-off-by: Khem Raj 

+
+update patch to version 5.1.5
+Signed-off-by: Changqing Li 
  ---
   configure.in | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
  
  diff --git a/configure.in b/configure.in

-index 50aed15..f81767c 100644
+index 493b9f1..268d06b 100644
  --- a/configure.in
  +++ b/configure.in
  @@ -12,7 +12,7 @@ define([AC_CACHE_SAVE], )dnl
- AC_INIT(.autofs-5.1.4)
+ AC_INIT(.autofs-5.1.5)
   
   # for pkg-config macros

  -m4_include([/usr/share/aclocal/pkg.m4])
@@ -24,5 +29,5 @@ index 50aed15..f81767c 100644
   #
   # autofs installs by default in /usr
  --
-1.9.1
+2.7.4
  
diff --git a/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch b/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch

index 469027a..e7fdd10 100644
--- 
a/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch
+++ 
b/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch
@@ -1,22 +1,26 @@
-From 557ca399f4b3a397f20bb147ec6dc4ab9732dd1e Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Fri, 31 Mar 2017 19:12:10 -0700
-Subject: [PATCH] Replace __S_IEXEC with S_IEXEC
+From 096e33743158e0e8c04d60d01cc66e2945d79777 Mon Sep 17 00:00:00 2001
+From: Changqing Li 
+Date: Tue, 27 Nov 2018 16:52:35 +0800
+Subject: [PATCH] From 557ca399f4b3a397f20bb147ec6dc4ab9732dd1e Mon Sep 17
+ 00:00:00 2001 From: Khem Raj  Date: Fri, 31 Mar 2017
+ 19:12:10 -0700 Subject: [PATCH] Replace __S_IEXEC with S_IEXEC
  
  S_IEXEC is portable
  
  Signed-off-by: Khem Raj 
  
+update patch to version 5.1.5

+Signed-off-by: Changqing Li 
  ---
- daemon/lookup.c| 4 ++--
+ daemon/lookup.c| 6 +++---
   modules/lookup_multi.c | 2 +-
- 2 files changed, 3 insertions(+), 3 deletions(-)
+ 2 files changed, 4 insertions(+), 4 deletions(-)
  
  diff --git a/daemon/lookup.c b/daemon/lookup.c

-index 201ccbb..d821db8 100644
+index 18df935..d35d484 100644
  --- a/daemon/lookup.c
  +++ b/daemon/lookup.c
-@@ -366,7 +366,7 @@ static int read_file_source_instance(struct autofs_point 
*ap, struct map_source
+@@ -382,7 +382,7 @@ static int read_file_source_instance(struct autofs_point 
*ap, struct map_source
if (!S_ISREG(st.st_mode))
return NSS_STATUS_NOTFOUND;
   
@@ -25,7 +29,7 @@ index 201ccbb..d821db8 100644

type = src_prog;
else
type = src_file;
-@@ -856,7 +856,7 @@ static int lookup_name_file_source_instance(struct 
autofs_point *ap, struct map_
+@@ -942,7 +942,7 @@ static int lookup_name_file_source_instance(struct 
autofs_point *ap, struct map_
if (!S_ISREG(st.st_mode))
return NSS_STATUS_NOTFOUND;
   
@@ -34,8 +38,17 @@ index 201ccbb..d821db8 100644

type = src_prog;
else
type = src_file;
+@@ -1118,7 +1118,7 @@ static struct map_source *lookup_get_map_source(struct 
master_mapent *entry)
+   if (!S_ISREG(st.st_mode))
+   return NULL;
+
+-  if (st.st_mode & __S_IEXEC)
++  if (st.st_mode & S_IEXEC)
+   type = "program";
+   else
+   type = "file";
  diff --git a/modules/lookup_multi.c 

[oe] [PATCH 2/2] libxklavier: Fix keyboard layout bug for xfce4-settings

2018-11-28 Thread Andreas Müller
* This was one the longest lasting and most annoying bug
* While we are at it: rename path files -> libxklavier

Signed-off-by: Andreas Müller 
---
 ...nfig_xkb.c-Fix-keyboard-layout-settings-f.patch | 39 ++
 .../fix-do_installe-failure.patch  |  0
 .../recipes-gnome/libxklavier/libxklavier_5.4.bb   |  1 +
 3 files changed, 40 insertions(+)
 create mode 100644 
meta-gnome/recipes-gnome/libxklavier/libxklavier/0001-xklavier_config_xkb.c-Fix-keyboard-layout-settings-f.patch
 rename meta-gnome/recipes-gnome/libxklavier/{files => 
libxklavier}/fix-do_installe-failure.patch (100%)

diff --git 
a/meta-gnome/recipes-gnome/libxklavier/libxklavier/0001-xklavier_config_xkb.c-Fix-keyboard-layout-settings-f.patch
 
b/meta-gnome/recipes-gnome/libxklavier/libxklavier/0001-xklavier_config_xkb.c-Fix-keyboard-layout-settings-f.patch
new file mode 100644
index 0..6c2d09112
--- /dev/null
+++ 
b/meta-gnome/recipes-gnome/libxklavier/libxklavier/0001-xklavier_config_xkb.c-Fix-keyboard-layout-settings-f.patch
@@ -0,0 +1,39 @@
+From 1a75ebdde705ab2a4f9459a60ab824d9f770bba4 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Andreas=20M=C3=BCller?= 
+Date: Wed, 28 Nov 2018 18:03:31 +0100
+Subject: [PATCH] xklavier_config_xkb.c: Fix keyboard layout settings for xfce
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+* Got helping hint at [1]
+* Patch stolen from [2]
+
+[1] https://bugzilla.xfce.org/show_bug.cgi?id=14185
+[2] https://launchpadlibrarian.net/399410035/revert-default-group-change.patch
+
+Upstream-Status: Pending
+
+Signed-off-by: Andreas Müller 
+---
+ libxklavier/xklavier_config_xkb.c | 4 
+ 1 file changed, 4 deletions(-)
+
+diff --git a/libxklavier/xklavier_config_xkb.c 
b/libxklavier/xklavier_config_xkb.c
+index baec569..c823e5b 100644
+--- a/libxklavier/xklavier_config_xkb.c
 b/libxklavier/xklavier_config_xkb.c
+@@ -403,10 +403,6 @@ xkl_config_get_keyboard(XklEngine * engine,
+   /* Return to normal X error processing */
+   xkl_engine_priv(engine, critical_section) = FALSE;
+ 
+-  if (activate)
+-  xkl_config_set_group_by_description(engine,
+-  
preactivation_group_description);
+-
+   xkl_debug(160,
+ "Unlinking the temporary xkb file %s\n",
+ xkb_fn);
+-- 
+2.14.5
+
diff --git 
a/meta-gnome/recipes-gnome/libxklavier/files/fix-do_installe-failure.patch 
b/meta-gnome/recipes-gnome/libxklavier/libxklavier/fix-do_installe-failure.patch
similarity index 100%
rename from 
meta-gnome/recipes-gnome/libxklavier/files/fix-do_installe-failure.patch
rename to 
meta-gnome/recipes-gnome/libxklavier/libxklavier/fix-do_installe-failure.patch
diff --git a/meta-gnome/recipes-gnome/libxklavier/libxklavier_5.4.bb 
b/meta-gnome/recipes-gnome/libxklavier/libxklavier_5.4.bb
index 2ef54f212..501a44972 100644
--- a/meta-gnome/recipes-gnome/libxklavier/libxklavier_5.4.bb
+++ b/meta-gnome/recipes-gnome/libxklavier/libxklavier_5.4.bb
@@ -13,6 +13,7 @@ RDEPENDS_${PN} += "iso-codes xkbcomp"
 SRC_URI = " \
 
http://pkgs.fedoraproject.org/repo/pkgs/${BPN}/${BPN}-${PV}.tar.bz2/13af74dcb6011ecedf1e3ed122bd31fa/${BPN}-${PV}.tar.bz2
 \
 file://fix-do_installe-failure.patch \
+file://0001-xklavier_config_xkb.c-Fix-keyboard-layout-settings-f.patch \
 "
 SRC_URI[md5sum] = "13af74dcb6011ecedf1e3ed122bd31fa"
 SRC_URI[sha256sum] = 
"17a34194df5cbcd3b7bfd0f561d95d1f723aa1c87fca56bc2c209514460a9320"
-- 
2.14.5

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


Re: [oe] [meta-networking][PATCH] geoip: add downloadfilename for geoip database files

2018-11-28 Thread Khem Raj
We have two options

Download and rename may be add a date component and save it on
sources.oe.org

Second option is to download the databases during build as temporary
artifacts but this might cause reproducibility problems

Either way it is going to have some issues
May be option 1 even though tedious can be better of two

On Wed, Nov 28, 2018 at 5:31 PM Changqing Li 
wrote:

> Khem and Marthin,
>
> The failure still caused by frequently changed checksum of the database. I
> send the patch on 11.20.
>
> but the checksum changed on 1121, and it also changed on 1128, seems like
> weekly change.
>
> but it should not failed if there is a premirror saved the
>
> Here is a result I get:
>
> $ md5sum 1128/*v6*
> d98a04eded0b08b945b5629106d58760  1128/GeoIPv6 (1).dat.gz
> 4d48c102ec68298b3fc7f57763455cb5  1128/GeoLiteCityv6.dat.gz
> $ md5sum 1121/*v6*
> b0f82334f94ca89872e7722db3511bb9  1121/GeoIPv6.dat.gz
> 50ad18a8a3ea4bba7c929bea6e22db75  1121/GeoLiteCityv6.dat.gz
> $ md5sum 1120/*v6*
> a908d7a51c3883eb8f693ca197c7a142  1120/GeoIPv6.dat.gz
> 8ac3506ccabaae7e9f7d6301c2654313  1120/GeoLiteCityv6.dat.gz
>
>
> On 11/28/18 3:14 AM, Martin Jansa wrote:
>
> I'm seeing different checksum than both your builder and the recipe.
>
> $ wget http://geolite.maxmind.com/download/geoip/database/GeoIPv6.dat.gz
> --2018-11-27 20:06:32--
> http://geolite.maxmind.com/download/geoip/database/GeoIPv6.dat.gz
> Resolving geolite.maxmind.com... 104.16.37.47, 104.16.38.47,
> 2606:4700::6810:252f, ...
> Connecting to geolite.maxmind.com|104.16.37.47|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 1209046 (1.2M) [application/octet-stream]
> Saving to: ‘GeoIPv6.dat.gz’
>
> 2018-11-27 20:06:32 (10.3 MB/s) - ‘GeoIPv6.dat.gz’ saved [1209046/1209046]
>
> $ md5sum GeoIPv6.dat.gz
> d98a04eded0b08b945b5629106d58760  GeoIPv6.dat.gz
>
> Is this the legacy archive? Because
> https://dev.maxmind.com/geoip/legacy/geolite/ now shows following:
>
> Yes,  I have  pointed out this problem  the first time I changed the
> checksum. maybe we should upgrade
>
> to geoip2,  and  drop current geoip1.6.  but I think even with geoip2,
> since it's database still not version,
>
> maybe also will met similar problem.
>
>
> //changqing
>
>
> Updated versions of the GeoLite Legacy databases are now only available to
> redistribution license customers, although anyone can continue to download
> the March 2018 GeoLite Legacy builds. Starting January 2, 2019, the last
> build will be removed from our website. GeoLite Legacy database users will
> need to switch to the GeoLite2 or commercial GeoIP databases and update
> their integrations by January 2, 2019.
>
> For more information, please visit our Support Center.
>
> Note: After careful consideration, taking into account customer feedback,
> we have decided against removing latitude and longitude coordinates from
> the GeoLite2 databases. We are in the process of reviewing coordinates used
> in all of our GeoLite2 and GeoIP databases to ensure there is no risk of
> misuse.
>
> * GeoLite2 databases are free IP geolocation databases comparable to, but
> less accurate than, MaxMind’s GeoIP2 databases. Please remember to use the
> accuracy radius if displaying coordinates on a map.
>
> New Database Format Available: This page is for our GeoLite Legacy
> databases. For our latest database format, please visit our GeoLite2
> Databases page. We offer redistribution licenses for our newer GeoLite2
> databases that will allow you to package the databases with your commercial
> products. For more information, please visit the GeoLite2 Commercial
> Redistribution page.
>
>
> On Tue, Nov 27, 2018 at 8:04 PM Khem Raj  wrote:
>
>> I am seeing errors on some builders
>>
>> http://errors.yoctoproject.org/Errors/Details/202341/
>> On Mon, Nov 19, 2018 at 11:29 PM Martin Jansa 
>> wrote:
>> >
>> > Looks, good.
>> >
>> > Adding variable for 20181120 might help with maintenance (if we need to
>> > change just checksums in future). And with good variable name (or a
>> > comment) it would also document in the recipe why we're using this in
>> > downloadfilename.
>> >
>> > On Tue, Nov 20, 2018 at 7:48 AM  wrote:
>> >
>> > > From: Changqing Li 
>> > >
>> > > previous change of checksum don't trigger archive to re-downloaded,
>> > > , which will cause checksum mismatch. add downloadfilename to
>> > > trigger re-download.
>> > >
>> > > 1. for user with PREMIRROR, another benefit is it can still compile
>> > > success event upstream checksum change frequently.
>> > > 2. but for user don't use PREMIRROR, if upstream checksum changed,
>> > > still might have checksum mismatch problem.
>> > >
>> > > Signed-off-by: Changqing Li 
>> > > ---
>> > >  .../recipes-support/geoip/geoip_1.6.12.bb  | 24
>> > > +++---
>> > >  1 file changed, 12 insertions(+), 12 deletions(-)
>> > >
>> > > diff --git a/meta-networking/recipes-support/geoip/geoip_1.6.12.bb
>> > > 

[oe] [PATCH 1/2] libmtp: fix paths for packages

2018-11-28 Thread Andreas Müller
Upstream has moved udev-rules/mtp-probe. That was not detected on previous
update commit so this is a follow-up.

Signed-off-by: Andreas Müller 
---
 meta-oe/recipes-connectivity/libmtp/libmtp_1.1.16.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-oe/recipes-connectivity/libmtp/libmtp_1.1.16.bb 
b/meta-oe/recipes-connectivity/libmtp/libmtp_1.1.16.bb
index a648c890e..c7e2bafdd 100644
--- a/meta-oe/recipes-connectivity/libmtp/libmtp_1.1.16.bb
+++ b/meta-oe/recipes-connectivity/libmtp/libmtp_1.1.16.bb
@@ -38,10 +38,10 @@ PACKAGES =+ "${BPN}-common ${BPN}-runtime"
 RDEPENDS_${BPN} += "libmtp-common"
 RRECOMMENDS_${BPN} += "libmtp-runtime ${PN}-bin"
 
-FILES_${BPN}-common = "${nonarch_base_libdir}/udev/rules.d/*"
+FILES_${BPN}-common = "${nonarch_libdir}/udev/rules.d/*"
 SUMMARY_${BPN}-common = "The udev rules file for MTP devices"
 
-FILES_${BPN}-runtime = "${nonarch_base_libdir}/udev/mtp-probe"
+FILES_${BPN}-runtime = "${nonarch_libdir}/udev/mtp-probe"
 RDEPENDS_${BPN}-runtime = "libmtp-common"
 SUMMARY_${BPN}-runtime = "mtp-probe, used for the MTP udev rules"
 DESCRIPTION_${BPN}-runtime = "This package provides mtp-probe, a program to 
probe newly connected device interfaces from userspace to determine if they are 
MTP devices, used for udev rules."
-- 
2.14.5

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


[oe] [meta-oe][PATCH] libcereal: Allow empty package

2018-11-28 Thread Brad Bishop
libcereal is header-only so create the empty base package so that
libcereal can be sanely included in an SDK via IMAGE_INSTALL, RDEPENDS,
and the like.

Signed-off-by: Brad Bishop 
---
 meta-oe/recipes-support/libcereal/libcereal_1.2.2.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta-oe/recipes-support/libcereal/libcereal_1.2.2.bb 
b/meta-oe/recipes-support/libcereal/libcereal_1.2.2.bb
index e02b4c960..365b40b17 100644
--- a/meta-oe/recipes-support/libcereal/libcereal_1.2.2.bb
+++ b/meta-oe/recipes-support/libcereal/libcereal_1.2.2.bb
@@ -15,4 +15,6 @@ inherit cmake
 
 EXTRA_OECMAKE = "-DJUST_INSTALL_CEREAL=ON"
 
+ALLOW_EMPTY_${PN} = "1"
+
 BBCLASSEXTEND = "native nativesdk"
-- 
2.19.1
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


Re: [oe] [meta-networking][PATCH 4/4] autofs: upgrade to 5.1.5

2018-11-28 Thread Khem Raj
http://errors.yoctoproject.org/Errors/Details/202450/
On Tue, Nov 27, 2018 at 1:38 AM  wrote:
>
> From: Changqing Li 
>
> Signed-off-by: Changqing Li 
> ---
>  .../0001-Do-not-hardcode-path-for-pkg.m4.patch | 19 +++--
>  .../0002-Replace-__S_IEXEC-with-S_IEXEC.patch  | 36 ++---
>  .../autofs-5.0.7-do-not-check-for-modprobe.patch   | 89 
> --
>  .../autofs/autofs/pkgconfig-libnsl.patch   | 35 +
>  ...-pkg-config-to-detect-libxml-2.0-and-krb5.patch | 24 --
>  .../autofs/{autofs_5.1.4.bb => autofs_5.1.5.bb}|  7 +-
>  6 files changed, 80 insertions(+), 130 deletions(-)
>  delete mode 100644 
> meta-networking/recipes-daemons/autofs/autofs/autofs-5.0.7-do-not-check-for-modprobe.patch
>  rename meta-networking/recipes-daemons/autofs/{autofs_5.1.4.bb => 
> autofs_5.1.5.bb} (92%)
>
> diff --git 
> a/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
>  
> b/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
> index f3f25f4..410827b 100644
> --- 
> a/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
> +++ 
> b/meta-networking/recipes-daemons/autofs/autofs/0001-Do-not-hardcode-path-for-pkg.m4.patch
> @@ -1,21 +1,26 @@
> -From 6d24365f0828185fd1bb4d199209ca07eb95c41d Mon Sep 17 00:00:00 2001
> -From: Khem Raj 
> -Date: Fri, 24 Aug 2018 06:24:36 +
> -Subject: [PATCH] Do not hardcode path for pkg.m4
> +From a27217a5437da313d251b4a765bf7cb60ffaa62d Mon Sep 17 00:00:00 2001
> +From: Changqing Li 
> +Date: Tue, 27 Nov 2018 15:27:47 +0800
> +Subject: [PATCH] From 6d24365f0828185fd1bb4d199209ca07eb95c41d Mon Sep 17
> + 00:00:00 2001 From: Khem Raj  Date: Fri, 24 Aug 2018
> + 06:24:36 + Subject: [PATCH] Do not hardcode path for pkg.m4
>
>  Upstream-Status: Pending
>
>  Signed-off-by: Khem Raj 
> +
> +update patch to version 5.1.5
> +Signed-off-by: Changqing Li 
>  ---
>   configure.in | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
>  diff --git a/configure.in b/configure.in
> -index 50aed15..f81767c 100644
> +index 493b9f1..268d06b 100644
>  --- a/configure.in
>  +++ b/configure.in
>  @@ -12,7 +12,7 @@ define([AC_CACHE_SAVE], )dnl
> - AC_INIT(.autofs-5.1.4)
> + AC_INIT(.autofs-5.1.5)
>
>   # for pkg-config macros
>  -m4_include([/usr/share/aclocal/pkg.m4])
> @@ -24,5 +29,5 @@ index 50aed15..f81767c 100644
>   #
>   # autofs installs by default in /usr
>  --
> -1.9.1
> +2.7.4
>
> diff --git 
> a/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch
>  
> b/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch
> index 469027a..e7fdd10 100644
> --- 
> a/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch
> +++ 
> b/meta-networking/recipes-daemons/autofs/autofs/0002-Replace-__S_IEXEC-with-S_IEXEC.patch
> @@ -1,22 +1,26 @@
> -From 557ca399f4b3a397f20bb147ec6dc4ab9732dd1e Mon Sep 17 00:00:00 2001
> -From: Khem Raj 
> -Date: Fri, 31 Mar 2017 19:12:10 -0700
> -Subject: [PATCH] Replace __S_IEXEC with S_IEXEC
> +From 096e33743158e0e8c04d60d01cc66e2945d79777 Mon Sep 17 00:00:00 2001
> +From: Changqing Li 
> +Date: Tue, 27 Nov 2018 16:52:35 +0800
> +Subject: [PATCH] From 557ca399f4b3a397f20bb147ec6dc4ab9732dd1e Mon Sep 17
> + 00:00:00 2001 From: Khem Raj  Date: Fri, 31 Mar 2017
> + 19:12:10 -0700 Subject: [PATCH] Replace __S_IEXEC with S_IEXEC
>
>  S_IEXEC is portable
>
>  Signed-off-by: Khem Raj 
>
> +update patch to version 5.1.5
> +Signed-off-by: Changqing Li 
>  ---
> - daemon/lookup.c| 4 ++--
> + daemon/lookup.c| 6 +++---
>   modules/lookup_multi.c | 2 +-
> - 2 files changed, 3 insertions(+), 3 deletions(-)
> + 2 files changed, 4 insertions(+), 4 deletions(-)
>
>  diff --git a/daemon/lookup.c b/daemon/lookup.c
> -index 201ccbb..d821db8 100644
> +index 18df935..d35d484 100644
>  --- a/daemon/lookup.c
>  +++ b/daemon/lookup.c
> -@@ -366,7 +366,7 @@ static int read_file_source_instance(struct autofs_point 
> *ap, struct map_source
> +@@ -382,7 +382,7 @@ static int read_file_source_instance(struct autofs_point 
> *ap, struct map_source
> if (!S_ISREG(st.st_mode))
> return NSS_STATUS_NOTFOUND;
>
> @@ -25,7 +29,7 @@ index 201ccbb..d821db8 100644
> type = src_prog;
> else
> type = src_file;
> -@@ -856,7 +856,7 @@ static int lookup_name_file_source_instance(struct 
> autofs_point *ap, struct map_
> +@@ -942,7 +942,7 @@ static int lookup_name_file_source_instance(struct 
> autofs_point *ap, struct map_
> if (!S_ISREG(st.st_mode))
> return NSS_STATUS_NOTFOUND;
>
> @@ -34,8 +38,17 @@ index 201ccbb..d821db8 100644
> type = src_prog;
> else
> type = src_file;
> +@@ -1118,7 +1118,7 @@ static struct map_source *lookup_get_map_source(struct 
> master_mapent *entry)
> +   if (!S_ISREG(st.st_mode))
> + 

Re: [oe] [meta-multimedia][PATCH v4] Add a working Tvheadend recipe

2018-11-28 Thread Khem Raj
Thanks Martin, I missed it. I have now send a patch to add the recipe
for missing package.
On Tue, Nov 27, 2018 at 2:32 PM Martin Jansa  wrote:
>
> What is supposed to provide libdvbcsa? It's not in any public layers
> registered here:
> https://layers.openembedded.org/layerindex/branch/master/recipes/?q=libdvbcsa
>
> Latest world build shows the same issue:
>
> ERROR: Nothing PROVIDES 'libdvbcsa' (but
> /home/jenkins/oe/world/yoe/sources/meta-openembedded/meta-multimedia/recipes-dvb/tvheadend/
> tvheadend_git.bb
> DEPENDS on or otherwise requires it). Close matches:
>
> On Fri, Nov 23, 2018 at 11:31 PM Peter Bašista  wrote:
>
> > The original one was previously removed
> > by commit ec9e5ed06256ad92c818474cdb490dc0d3a0d0a3
> > as part of a clean-up of blacklisted recipes.
> >
> > Signed-off-by: Peter Bašista 
> > ---
> >  .../recipes-dvb/tvheadend/tvheadend_git.bb| 23 +++
> >  1 file changed, 23 insertions(+)
> >  create mode 100644 meta-multimedia/recipes-dvb/tvheadend/tvheadend_git.bb
> >
> > diff --git a/meta-multimedia/recipes-dvb/tvheadend/tvheadend_git.bb
> > b/meta-multimedia/recipes-dvb/tvheadend/tvheadend_git.bb
> > new file mode 100644
> > index 0..95cf10bf6
> > --- /dev/null
> > +++ b/meta-multimedia/recipes-dvb/tvheadend/tvheadend_git.bb
> > @@ -0,0 +1,23 @@
> > +SUMMARY = "Tvheadend: TV streaming server and recorder"
> > +HOMEPAGE = "https://tvheadend.org/;
> > +
> > +inherit autotools-brokensep gettext gitpkgv pkgconfig
> > +
> > +DEPENDS = "avahi cmake-native libdvbcsa libpcre2 openssl uriparser zlib"
> > +
> > +LICENSE = "GPLv3+"
> > +LIC_FILES_CHKSUM =
> > "file://LICENSE.md;md5=9cae5acac2e9ee2fc3aec01ac88ce5db"
> > +
> > +SRC_URI = "git://github.com/tvheadend/tvheadend.git"
> > +
> > +SRCREV = "bdc2ae9e19520a10cdf0bec0fcc0050b32bc75ff"
> > +PV = "4.3+git${SRCPV}"
> > +PKGV = "4.3+git${GITPKGV}"
> > +
> > +S = "${WORKDIR}/git"
> > +
> > +EXTRA_OECONF += "--arch=${TARGET_ARCH} \
> > + --disable-hdhomerun_static \
> > + --disable-ffmpeg_static \
> > + --disable-libav \
> > + "
> > --
> > 2.19.1
> >
> > --
> > ___
> > 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


[oe] [meta-multimedia][PATCH] libdvbcsa: Add recipe

2018-11-28 Thread Khem Raj
tvheadend needs this library

Signed-off-by: Khem Raj 
---
 .../libdvbcsa/libdvbcsa/libdvbcsa.pc  | 10 ++
 .../libdvbcsa/libdvbcsa_1.1.0.bb  | 19 +++
 2 files changed, 29 insertions(+)
 create mode 100644 
meta-multimedia/recipes-multimedia/libdvbcsa/libdvbcsa/libdvbcsa.pc
 create mode 100644 
meta-multimedia/recipes-multimedia/libdvbcsa/libdvbcsa_1.1.0.bb

diff --git 
a/meta-multimedia/recipes-multimedia/libdvbcsa/libdvbcsa/libdvbcsa.pc 
b/meta-multimedia/recipes-multimedia/libdvbcsa/libdvbcsa/libdvbcsa.pc
new file mode 100644
index 00..57e74668eb
--- /dev/null
+++ b/meta-multimedia/recipes-multimedia/libdvbcsa/libdvbcsa/libdvbcsa.pc
@@ -0,0 +1,10 @@
+prefix=/usr
+libdir=${prefix}/lib
+includedir=${prefix}/include
+
+Name: libdvbcsa
+Description:  is a free implementation of the DVB Common Scrambling Algorithm 
- DVB/CSA - with encryption and decryption capabilities.
+Version: 1.1.0
+Requires:
+Libs: -L${libdir} -ldvbcsa
+
diff --git a/meta-multimedia/recipes-multimedia/libdvbcsa/libdvbcsa_1.1.0.bb 
b/meta-multimedia/recipes-multimedia/libdvbcsa/libdvbcsa_1.1.0.bb
new file mode 100644
index 00..7f042c382f
--- /dev/null
+++ b/meta-multimedia/recipes-multimedia/libdvbcsa/libdvbcsa_1.1.0.bb
@@ -0,0 +1,19 @@
+SUMMARY = "Open implementation of the DVB Common Scrambling Algorithm, encrypt 
and decrypt "
+SECTION = "libs/multimedia"
+LICENSE = "LGPLv2.1+"
+LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
+
+SRCREV = "bc6c0b164a87ce05e9925785cc6fb3f54c02b026"
+
+SRC_URI = "git://code.videolan.org/videolan/libdvbcsa.git;protocol=https \
+   file://libdvbcsa.pc \
+"
+
+S = "${WORKDIR}/git"
+
+inherit autotools lib_package pkgconfig
+
+do_install_append() {
+install -D -m 0644 ${S}/src/dvbcsa/dvbcsa.h 
${D}${includedir}/dvbcsa/dvbcsa.h
+install -D -m 0644 ${WORKDIR}/libdvbcsa.pc 
${D}${libdir}/pkgconfig/libdvbcsa.pc
+}
-- 
2.19.2

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


Re: [oe] [meta-oe][sumo][PATCH] nodejs: Enable system ICU support

2018-11-28 Thread Raphael Kubo da Costa
akuster808  writes:

> On 11/26/18 10:45 AM, Khem Raj wrote:
>> Armin
>>
>> This is ok for rocko
>> On Tue, Nov 20, 2018 at 7:40 AM Raphael Kubo da Costa
>>  wrote:
>>> From: Khem Raj 
>>>
>>> Latest Chromium needs it during build
>
> Is this keeping chromium from building.

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


[oe] OpenJDK 8 Segfault on i.MX6

2018-11-28 Thread Attie Grande
Hi all,

I've been trying to get OpenJDK 8 162-b12 running on Linux on an ARM
platform (i.MX6), using the Yocto Sumo recipes from meta-java [1].

Unfortunately, the result is a java executable that cannot startup
without hitting a SIGSEGV. Even running "simple" things like `java` or
`java -help` result in a segmentation fault.

I've tried to investigate it, but I don't have the insight into the
project to really be able to debug the issue properly myself.

I've been in contact with jdk-dev [2], who have been helpful so far,
but we're starting to wonder about the patches applied as part of the
Yocto build.

After enabling fastdebug, I still get a segfault with little insight
into the issue - a fatal error log is available here [3].

Investigating with GDB shows that the segfault is in libjvm.so, but
there are no symbols in this region of memory, and the stack has been
destroyed (I suspect as part of the VM's operation).

We've confirmed that another build of OpenJDK 8 runs on this platform
[4] (currently jdk8u191-b12).

I've spent some time trying to update to 191-b12, but a number of the
patches appear to be necessary for Yocto's build environment, while
others require major rework to apply cleanly.

I see that Thud is using 172b11 [5] which is somewhere in between...
so I could give those recipes a try - though there is a Sumo / Thud
dependency issue with xorg-proto.

Has anyone seen this before, or have any insight into the patches / Yocto build?

Aleksey (from jdk-dev) mentioned [6] a user on IRC called hitendra had
a similar sounding issue with Yocto Sumo / i.MX6 / OpenJDK 8 162-b12,
and I've also come across a brief / frutiless IRC log in #yocto [7].

Regards,
Attie

[1]: 
https://git.yoctoproject.org/cgit/cgit.cgi/meta-java/tree/recipes-core/openjdk?h=sumo
[2]: http://mail.openjdk.java.net/pipermail/jdk-dev/2018-November/002246.html
[3]: https://pastebin.com/raw/iXTz8v9z
[4]: 
https://builds.shipilev.net/openjdk-jdk8-redhat/openjdk-jdk8-redhat-latest-linux-arm32-hflt-zero-fastdebug.tar.xz
[5]: 
https://git.yoctoproject.org/cgit/cgit.cgi/meta-java/tree/recipes-core/openjdk?h=master-next
[6]: http://mail.openjdk.java.net/pipermail/jdk-dev/2018-November/002251.html
[7]: 
https://www.yoctoproject.org/irc/%23yocto.2018-10-23.log.html#t2018-10-23T09:46:21
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


Re: [oe] [PATCH v2] mpd: update to 0.21.3

2018-11-28 Thread Khem Raj
On Tue, Nov 27, 2018 at 11:34 PM Max Kellermann
 wrote:
>
> On 2018/11/28 06:53, Khem Raj  wrote:
> > Hi Max
> >
> > it fails to build with systemd see
> > http://errors.yoctoproject.org/Errors/Details/202303/
> >
> > It seems the new meson change is not installing the system unit files
> > and socket file during do_install properly, one way is that we explicitly
> > install/copy them during do_install, but I think its better to fix it in mpd
> > itself if possible
>
> We had this problem already when I submitted version 0.21 for the
> first time, and my 0.21.3 patch contained more explicit options to
> enable systemd, hoping to make it fail earlier, but it didn't.
>
> Packaging with systemd works perfectly fine here on my machine, all
> the units are in the right place.  Unfortunately, your Yocto build
> logs are devoid of any hints what went wrong.
>
> So yes, I agree with you that we should fix this in MPD upstream (I am
> the MPD upstream maintainer, btw.), but I have no idea what's wrong.
> If only I could reproduce the problem.
>
> Is there any way to get more verbose logs from your build bot?
>

I can reproduce it locally as well when building for

MACHINE = "raspberrypi3"
DISTRO_FEATURES_append = " systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"


ERROR: mpd-0.21.3-r0 do_package: SYSTEMD_SERVICE_mpd value mpd.socket
does not exist
ERROR: mpd-0.21.3-r0 do_package: Function failed: systemd_populate_packages
ERROR: Logfile of failure stored in:
/mnt/a/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/mpd/0.21.3-r0/temp/log.do_package.25748
ERROR: Task 
(/mnt/a/yoe/sources/meta-openembedded/meta-multimedia/recipes-multimedia/musicpd/mpd_0.21.3.bb:do_package)
failed with exit code '1'
logs are here
https://gist.github.com/b69ddd940689c5ad02bce7ef2eb89a73
https://gist.github.com/4c1dd2c382a209b03d290447146cc9c4
https://gist.github.com/675704fde3469895b4c6207d4c83041d


if you are interested here is the distro setup I use.
https://github.com/YoeDistro/yoe-distro

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


Re: [oe] OpenJDK 8 Segfault on i.MX6

2018-11-28 Thread Attie Grande
Hi again,

As a follow-up (under Aleksey's guidance) I applied the following patches:

- JDK-8202600 [1][2] had no effect, but I'll be keeping it applied.
- JDK-8194739 [3][4] and things have sprung into life.

I'll prepare a patch and submit tomorrow.

Attie

[1]: https://bugs.openjdk.java.net/browse/JDK-8202600
[2]: http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/rev/ca4663e58916
[3]: https://bugs.openjdk.java.net/browse/JDK-8194739
[4]: http://hg.openjdk.java.net/jdk/jdk10/rev/69d1a1590485
On Wed, 28 Nov 2018 at 17:30, Attie Grande
 wrote:
>
> Hi all,
>
> I've been trying to get OpenJDK 8 162-b12 running on Linux on an ARM
> platform (i.MX6), using the Yocto Sumo recipes from meta-java [1].
>
> Unfortunately, the result is a java executable that cannot startup
> without hitting a SIGSEGV. Even running "simple" things like `java` or
> `java -help` result in a segmentation fault.
>
> I've tried to investigate it, but I don't have the insight into the
> project to really be able to debug the issue properly myself.
>
> I've been in contact with jdk-dev [2], who have been helpful so far,
> but we're starting to wonder about the patches applied as part of the
> Yocto build.
>
> After enabling fastdebug, I still get a segfault with little insight
> into the issue - a fatal error log is available here [3].
>
> Investigating with GDB shows that the segfault is in libjvm.so, but
> there are no symbols in this region of memory, and the stack has been
> destroyed (I suspect as part of the VM's operation).
>
> We've confirmed that another build of OpenJDK 8 runs on this platform
> [4] (currently jdk8u191-b12).
>
> I've spent some time trying to update to 191-b12, but a number of the
> patches appear to be necessary for Yocto's build environment, while
> others require major rework to apply cleanly.
>
> I see that Thud is using 172b11 [5] which is somewhere in between...
> so I could give those recipes a try - though there is a Sumo / Thud
> dependency issue with xorg-proto.
>
> Has anyone seen this before, or have any insight into the patches / Yocto 
> build?
>
> Aleksey (from jdk-dev) mentioned [6] a user on IRC called hitendra had
> a similar sounding issue with Yocto Sumo / i.MX6 / OpenJDK 8 162-b12,
> and I've also come across a brief / frutiless IRC log in #yocto [7].
>
> Regards,
> Attie
>
> [1]: 
> https://git.yoctoproject.org/cgit/cgit.cgi/meta-java/tree/recipes-core/openjdk?h=sumo
> [2]: http://mail.openjdk.java.net/pipermail/jdk-dev/2018-November/002246.html
> [3]: https://pastebin.com/raw/iXTz8v9z
> [4]: 
> https://builds.shipilev.net/openjdk-jdk8-redhat/openjdk-jdk8-redhat-latest-linux-arm32-hflt-zero-fastdebug.tar.xz
> [5]: 
> https://git.yoctoproject.org/cgit/cgit.cgi/meta-java/tree/recipes-core/openjdk?h=master-next
> [6]: http://mail.openjdk.java.net/pipermail/jdk-dev/2018-November/002251.html
> [7]: 
> https://www.yoctoproject.org/irc/%23yocto.2018-10-23.log.html#t2018-10-23T09:46:21
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel