[meta-oe][PATCH] cryptsetup: upgrade 2.2.2 -> 2.3.0

[meta-oe][PATCH] cryptsetup: upgrade 2.2.2 -> 2.3.0

[Wang Mingyu]

Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
 .../cryptsetup/{cryptsetup_2.2.2.bb => cryptsetup_2.3.0.bb}   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta-oe/recipes-crypto/cryptsetup/{cryptsetup_2.2.2.bb => cryptsetup_2.3.0.bb} (96%)

diff --git a/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.2.2.bb b/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.3.0.bb
similarity index 96%
rename from meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.2.2.bb
rename to meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.3.0.bb
index 479b9eb37..0e36ed4a2 100644
--- a/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.2.2.bb
+++ b/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.3.0.bb
@@ -21,8 +21,8 @@ RDEPENDS_${PN} = " \
 "
 
 SRC_URI = "${KERNELORG_MIRROR}/linux/utils/${BPN}/v${@d.getVar('PV').split('.')[0]}.${@d.getVar('PV').split('.')[1]}/${BP}.tar.xz"
-SRC_URI[md5sum] = "2b64ca9ea16e823df359eacf9c02414b"
-SRC_URI[sha256sum] = "2af0ec9551ab9c870074cae9d3f68d82cab004f4095fa89db0e4413713424a46"
+SRC_URI[md5sum] = "48be3bd7c557d051f638047d280e93ee"
+SRC_URI[sha256sum] = "395690de99509428354d3cd15cf023bed01487e6f1565b2181e013dc847bbc85"
 
 inherit autotools gettext pkgconfig
 
-- 
2.17.1

[meta-oe][PATCH] fio: upgrade 3.17 -> 3.18

[Wang Mingyu]

Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
 meta-oe/recipes-benchmark/fio/{fio_3.17.bb => fio_3.18.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-oe/recipes-benchmark/fio/{fio_3.17.bb => fio_3.18.bb} (96%)

diff --git a/meta-oe/recipes-benchmark/fio/fio_3.17.bb b/meta-oe/recipes-benchmark/fio/fio_3.18.bb
similarity index 96%
rename from meta-oe/recipes-benchmark/fio/fio_3.17.bb
rename to meta-oe/recipes-benchmark/fio/fio_3.18.bb
index 482928c31..b6484290f 100644
--- a/meta-oe/recipes-benchmark/fio/fio_3.17.bb
+++ b/meta-oe/recipes-benchmark/fio/fio_3.18.bb
@@ -22,7 +22,7 @@ PACKAGECONFIG_NUMA_armeb = ""
 PACKAGECONFIG ??= "${PACKAGECONFIG_NUMA}"
 PACKAGECONFIG[numa] = ",--disable-numa,numactl"
 
-SRCREV = "08ce9dc20b8a4e55db7af6d869ddfa49b4a02d03"
+SRCREV = "ac694f66968fe7b18c820468abd8333f3df333fb"
 SRC_URI = "git://git.kernel.dk/fio.git \
           file://0001-update-the-interpreter-paths.patch \
 "
-- 
2.17.1

[meta-oe][PATCH] hwdata: upgrade 0.331 -> 0.332

[Wang Mingyu]

Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
 meta-oe/recipes-support/hwdata/hwdata_git.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-oe/recipes-support/hwdata/hwdata_git.bb b/meta-oe/recipes-support/hwdata/hwdata_git.bb
index e63838f9a..77bb60aed 100644
--- a/meta-oe/recipes-support/hwdata/hwdata_git.bb
+++ b/meta-oe/recipes-support/hwdata/hwdata_git.bb
@@ -5,8 +5,8 @@ SECTION = "System/Base"
 LICENSE = "GPL-2.0+"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=1556547711e8246992b999edd9445a57"
 
-PV = "0.331"
-SRCREV = "337be5f6acbe15aa06063914e1fd25d49a05523b"
+PV = "0.332"
+SRCREV = "17cc5d636a559ae1073865846980e4db35f7989a"
 SRC_URI = "git://github.com/vcrhonek/${BPN}.git"
 
 S = "${WORKDIR}/git"
-- 
2.17.1

[meta-oe][PATCH] libdbi-perl: upgrade 1.642 -> 1.643

[Wang Mingyu]

Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
 .../perl/{libdbi-perl_1.642.bb => libdbi-perl_1.643.bb}       | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta-oe/recipes-devtools/perl/{libdbi-perl_1.642.bb => libdbi-perl_1.643.bb} (92%)

diff --git a/meta-oe/recipes-devtools/perl/libdbi-perl_1.642.bb b/meta-oe/recipes-devtools/perl/libdbi-perl_1.643.bb
similarity index 92%
rename from meta-oe/recipes-devtools/perl/libdbi-perl_1.642.bb
rename to meta-oe/recipes-devtools/perl/libdbi-perl_1.643.bb
index 7532b3fa2..75fad46bf 100644
--- a/meta-oe/recipes-devtools/perl/libdbi-perl_1.642.bb
+++ b/meta-oe/recipes-devtools/perl/libdbi-perl_1.643.bb
@@ -10,8 +10,8 @@ LICENSE = "Artistic-1.0 | GPL-1.0+"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=10982c7148e0a012c0fd80534522f5c5"
 
 SRC_URI = "http://search.cpan.org/CPAN/authors/id/T/TI/TIMB/DBI-${PV}.tar.gz"
-SRC_URI[md5sum] = "f2ba18b5cea1c8cb322a62be0a847f3d"
-SRC_URI[sha256sum] = "3f2025023a56286cebd15cb495e36ccd9b456c3cc229bf2ce1f69e9ebfc27f5d"
+SRC_URI[md5sum] = "352f80b1e23769c116082a90905d7398"
+SRC_URI[sha256sum] = "8a2b993db560a2c373c174ee976a51027dd780ec766ae17620c20393d2e836fa"
 
 S = "${WORKDIR}/DBI-${PV}"
 
-- 
2.17.1

[meta-oe][PATCH] libp11: upgrade 0.4.10 -> 11

[Wang Mingyu]

Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
 .../recipes-support/libp11/{libp11_0.4.10.bb => libp11_11.bb}   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-oe/recipes-support/libp11/{libp11_0.4.10.bb => libp11_11.bb} (93%)

diff --git a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb b/meta-oe/recipes-support/libp11/libp11_11.bb
similarity index 93%
rename from meta-oe/recipes-support/libp11/libp11_0.4.10.bb
rename to meta-oe/recipes-support/libp11/libp11_11.bb
index 655db4907..5a0951df2 100644
--- a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb
+++ b/meta-oe/recipes-support/libp11/libp11_11.bb
@@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=fad9b3332be894bab9bc501572864b29"
 DEPENDS = "libtool openssl"
 
 SRC_URI = "git://github.com/OpenSC/libp11.git"
-SRCREV = "973d31f3f58d5549ddd8b1f822ce8f72186f9d68"
+SRCREV = "e1210903291b1de9eabcad26e740a4b2fbcca692"
 
 S = "${WORKDIR}/git"
 
-- 
2.17.1

Re: [meta-oe][PATCH] fio: upgrade 3.17 -> 3.18

[Khem Raj]

https://errors.yoctoproject.org/Errors/Details/391129/

On Fri, Feb 14, 2020 at 8:11 AM Wang Mingyu <wangmy@cn.fujitsu.com> wrote:
>
> Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
> ---
>  meta-oe/recipes-benchmark/fio/{fio_3.17.bb => fio_3.18.bb} | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>  rename meta-oe/recipes-benchmark/fio/{fio_3.17.bb => fio_3.18.bb} (96%)
>
> diff --git a/meta-oe/recipes-benchmark/fio/fio_3.17.bb b/meta-oe/recipes-benchmark/fio/fio_3.18.bb
> similarity index 96%
> rename from meta-oe/recipes-benchmark/fio/fio_3.17.bb
> rename to meta-oe/recipes-benchmark/fio/fio_3.18.bb
> index 482928c31..b6484290f 100644
> --- a/meta-oe/recipes-benchmark/fio/fio_3.17.bb
> +++ b/meta-oe/recipes-benchmark/fio/fio_3.18.bb
> @@ -22,7 +22,7 @@ PACKAGECONFIG_NUMA_armeb = ""
>  PACKAGECONFIG ??= "${PACKAGECONFIG_NUMA}"
>  PACKAGECONFIG[numa] = ",--disable-numa,numactl"
>
> -SRCREV = "08ce9dc20b8a4e55db7af6d869ddfa49b4a02d03"
> +SRCREV = "ac694f66968fe7b18c820468abd8333f3df333fb"
>  SRC_URI = "git://git.kernel.dk/fio.git \
>            file://0001-update-the-interpreter-paths.patch \
>  "
> --
> 2.17.1
>
>
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [meta-oe][PATCH] fio: upgrade 3.17 -> 3.18

[Jonathan Richardson]

I was just about to submit a patch to remove the disabling of compiler
optimizations to fio. On our cortex A72 this kills the performance of fio
by 25%. That would solve this build issue also. I haven't seen any crashes
with fio. If there are some architecture specific issues can the removal
of optimizations be arch specific only and not the default?

On Sat, Feb 15, 2020 at 12:40 AM Khem Raj <raj.khem@gmail.com> wrote:
>
> https://errors.yoctoproject.org/Errors/Details/391129/
>
> On Fri, Feb 14, 2020 at 8:11 AM Wang Mingyu <wangmy@cn.fujitsu.com> wrote:
> >
> > Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
> > ---
> >  meta-oe/recipes-benchmark/fio/{fio_3.17.bb => fio_3.18.bb} | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >  rename meta-oe/recipes-benchmark/fio/{fio_3.17.bb => fio_3.18.bb} (96%)
> >
> > diff --git a/meta-oe/recipes-benchmark/fio/fio_3.17.bb b/meta-oe/recipes-benchmark/fio/fio_3.18.bb
> > similarity index 96%
> > rename from meta-oe/recipes-benchmark/fio/fio_3.17.bb
> > rename to meta-oe/recipes-benchmark/fio/fio_3.18.bb
> > index 482928c31..b6484290f 100644
> > --- a/meta-oe/recipes-benchmark/fio/fio_3.17.bb
> > +++ b/meta-oe/recipes-benchmark/fio/fio_3.18.bb
> > @@ -22,7 +22,7 @@ PACKAGECONFIG_NUMA_armeb = ""
> >  PACKAGECONFIG ??= "${PACKAGECONFIG_NUMA}"
> >  PACKAGECONFIG[numa] = ",--disable-numa,numactl"
> >
> > -SRCREV = "08ce9dc20b8a4e55db7af6d869ddfa49b4a02d03"
> > +SRCREV = "ac694f66968fe7b18c820468abd8333f3df333fb"
> >  SRC_URI = "git://git.kernel.dk/fio.git \
> >            file://0001-update-the-interpreter-paths.patch \
> >  "
> > --
> > 2.17.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

Re: [meta-oe][PATCH] fio: upgrade 3.17 -> 3.18

[Adrian Bunk]

On Tue, Feb 18, 2020 at 11:37:33AM -0800, Jonathan Richardson via Openembedded-devel wrote:
> I was just about to submit a patch to remove the disabling of compiler
> optimizations to fio. On our cortex A72 this kills the performance of fio
> by 25%. That would solve this build issue also.
>...
> > https://errors.yoctoproject.org/Errors/Details/391129/
>...

t/io_uring.c:103:17: error: '__NR_sys_io_uring_register' undeclared (first use in this function); did you mean 'SYS_io_uring_register'?

This error does not look related to optimization.

This looks like https://github.com/axboe/fio/issues/923

cu
Adrian

Re: [meta-oe][PATCH] fio: upgrade 3.17 -> 3.18

[Jonathan Richardson]

On Tue, Feb 18, 2020 at 2:09 PM Adrian Bunk <bunk@stusta.de> wrote:
>
> On Tue, Feb 18, 2020 at 11:37:33AM -0800, Jonathan Richardson via Openembedded-devel wrote:
> > I was just about to submit a patch to remove the disabling of compiler
> > optimizations to fio. On our cortex A72 this kills the performance of fio
> > by 25%. That would solve this build issue also.
> >...
> > > https://errors.yoctoproject.org/Errors/Details/391129/
> >...
>
> t/io_uring.c:103:17: error: '__NR_sys_io_uring_register' undeclared (first use in this function); did you mean 'SYS_io_uring_register'?
>
> This error does not look related to optimization.
>
> This looks like https://github.com/axboe/fio/issues/923

Yes you're right. The error is another issue. The message I was referring
to is actually only a warning. It should fix the warning only:

  397 | #  warning _FORTIFY_SOURCE requires compiling with optimization (-O)

Re: [meta-oe][PATCH] fio: upgrade 3.17 -> 3.18

[Khem Raj]

On Tue, Feb 18, 2020 at 2:09 PM Adrian Bunk <bunk@stusta.de> wrote:
>
> On Tue, Feb 18, 2020 at 11:37:33AM -0800, Jonathan Richardson via Openembedded-devel wrote:
> > I was just about to submit a patch to remove the disabling of compiler
> > optimizations to fio. On our cortex A72 this kills the performance of fio
> > by 25%. That would solve this build issue also.
> >...
> > > https://errors.yoctoproject.org/Errors/Details/391129/
> >...
>
> t/io_uring.c:103:17: error: '__NR_sys_io_uring_register' undeclared (first use in this function); did you mean 'SYS_io_uring_register'?
>
> This error does not look related to optimization.
>
> This looks like https://github.com/axboe/fio/issues/923
>

Thanks, I think this will fix the issue we have at hand, Wang would
you include this in a v2 ?

> cu
> Adrian

Re: [meta-oe][PATCH] libp11: upgrade 0.4.10 -> 11

[Ricardo Salveti]

Hi,

On Fri, Feb 14, 2020 at 1:12 PM Wang Mingyu <wangmy@cn.fujitsu.com> wrote:
>
> Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
> ---
>  .../recipes-support/libp11/{libp11_0.4.10.bb => libp11_11.bb}   | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>  rename meta-oe/recipes-support/libp11/{libp11_0.4.10.bb => libp11_11.bb} (93%)
>
> diff --git a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb b/meta-oe/recipes-support/libp11/libp11_11.bb
> similarity index 93%
> rename from meta-oe/recipes-support/libp11/libp11_0.4.10.bb
> rename to meta-oe/recipes-support/libp11/libp11_11.bb
> index 655db4907..5a0951df2 100644
> --- a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb
> +++ b/meta-oe/recipes-support/libp11/libp11_11.bb
> @@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=fad9b3332be894bab9bc501572864b29"
>  DEPENDS = "libtool openssl"
>
>  SRC_URI = "git://github.com/OpenSC/libp11.git"
> -SRCREV = "973d31f3f58d5549ddd8b1f822ce8f72186f9d68"
> +SRCREV = "e1210903291b1de9eabcad26e740a4b2fbcca692"

Is this change really correct? The latest libp11 upstream release is
0.4.10, as you can see at https://github.com/OpenSC/libp11/releases.
The next one seems that will be 0.4.11, so now sure how it was moved
to 11 directly.

Also, the SRCREV seems incorrect, as it is pointing out to the 0.4.9
release (https://github.com/OpenSC/libp11/commit/e1210903291b1de9eabcad26e740a4b2fbcca6920).

In the end this change is increasing the PV but moving SRCREV to an
even older release.

Thanks,
-- 
Ricardo Salveti

Re: [meta-oe][PATCH] libp11: upgrade 0.4.10 -> 11

[Ricardo Salveti]

On Thu, Feb 27, 2020 at 2:52 PM Ricardo Salveti <ricardo@foundries.io> wrote:
>
> Hi,
>
> On Fri, Feb 14, 2020 at 1:12 PM Wang Mingyu <wangmy@cn.fujitsu.com> wrote:
> >
> > Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
> > ---
> >  .../recipes-support/libp11/{libp11_0.4.10.bb => libp11_11.bb}   | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >  rename meta-oe/recipes-support/libp11/{libp11_0.4.10.bb => libp11_11.bb} (93%)
> >
> > diff --git a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb b/meta-oe/recipes-support/libp11/libp11_11.bb
> > similarity index 93%
> > rename from meta-oe/recipes-support/libp11/libp11_0.4.10.bb
> > rename to meta-oe/recipes-support/libp11/libp11_11.bb
> > index 655db4907..5a0951df2 100644
> > --- a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb
> > +++ b/meta-oe/recipes-support/libp11/libp11_11.bb
> > @@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=fad9b3332be894bab9bc501572864b29"
> >  DEPENDS = "libtool openssl"
> >
> >  SRC_URI = "git://github.com/OpenSC/libp11.git"
> > -SRCREV = "973d31f3f58d5549ddd8b1f822ce8f72186f9d68"
> > +SRCREV = "e1210903291b1de9eabcad26e740a4b2fbcca692"
>
> Is this change really correct? The latest libp11 upstream release is
> 0.4.10, as you can see at https://github.com/OpenSC/libp11/releases.
> The next one seems that will be 0.4.11, so now sure how it was moved
> to 11 directly.
>
> Also, the SRCREV seems incorrect, as it is pointing out to the 0.4.9
> release (https://github.com/OpenSC/libp11/commit/e1210903291b1de9eabcad26e740a4b2fbcca6920).

Had a typo, correct link:
https://github.com/OpenSC/libp11/commit/e1210903291b1de9eabcad26e740a4b2fbcca692

Cheers,
-- 
Ricardo Salveti

Re: [meta-oe][PATCH] libp11: upgrade 0.4.10 -> 11

[Khem Raj]

On Thu, Feb 27, 2020 at 9:53 AM Ricardo Salveti <ricardo@foundries.io> wrote:
>
> Hi,
>
> On Fri, Feb 14, 2020 at 1:12 PM Wang Mingyu <wangmy@cn.fujitsu.com> wrote:
> >
> > Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
> > ---
> >  .../recipes-support/libp11/{libp11_0.4.10.bb => libp11_11.bb}   | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >  rename meta-oe/recipes-support/libp11/{libp11_0.4.10.bb => libp11_11.bb} (93%)
> >
> > diff --git a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb b/meta-oe/recipes-support/libp11/libp11_11.bb
> > similarity index 93%
> > rename from meta-oe/recipes-support/libp11/libp11_0.4.10.bb
> > rename to meta-oe/recipes-support/libp11/libp11_11.bb
> > index 655db4907..5a0951df2 100644
> > --- a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb
> > +++ b/meta-oe/recipes-support/libp11/libp11_11.bb
> > @@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=fad9b3332be894bab9bc501572864b29"
> >  DEPENDS = "libtool openssl"
> >
> >  SRC_URI = "git://github.com/OpenSC/libp11.git"
> > -SRCREV = "973d31f3f58d5549ddd8b1f822ce8f72186f9d68"
> > +SRCREV = "e1210903291b1de9eabcad26e740a4b2fbcca692"
>
> Is this change really correct? The latest libp11 upstream release is
> 0.4.10, as you can see at https://github.com/OpenSC/libp11/releases.
> The next one seems that will be 0.4.11, so now sure how it was moved
> to 11 directly.
>
> Also, the SRCREV seems incorrect, as it is pointing out to the 0.4.9
> release (https://github.com/OpenSC/libp11/commit/e1210903291b1de9eabcad26e740a4b2fbcca6920).
>
> In the end this change is increasing the PV but moving SRCREV to an
> even older release.
>

you are right, and it escaped me. Would you be willing to send a patch
to correct it
since it was not long time ago.

> Thanks,
> --
> Ricardo Salveti