All of lore.kernel.org
 help / color / mirror / Atom feed
* [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure
@ 2018-09-07 18:10 Yevgeny Popovych
  2018-09-07 18:10 ` [meta-java][PATCH 1/3] ca-certificates-java: Fix sysconfdir for -native recipe Yevgeny Popovych
                   ` (3 more replies)
  0 siblings, 4 replies; 14+ messages in thread
From: Yevgeny Popovych @ 2018-09-07 18:10 UTC (permalink / raw)
  To: openembedded-devel; +Cc: andre.draszik

This series fixes several issues with ca-certificates-java:
* when used as a native tool
* failure on do_rootfs

This doesn't fix all the issues and there is definitely a room for improvement.
I presume that running it on the target doesn't work - at least ${sysconfdir} is
not expanded in the hook.
I also think that will be best to drop create-ca-certificates-java usage in
the postinst and let it be called as a hook of ca-certificates. This will allow
us to remove some code and simplify both script and recipe.

It would be great if others could test their use cases;
and clarify them - is create-ca-certificates-java really needed?.

Yevgeny Popovych (3):
  ca-certificates-java: Fix sysconfdir for -native recipe
  ca-certificates-java: Don't fail when called via hook on do_rootfs
  ca-certificates-java: Distinguish between SYSROOT and D

 .../ca-certificates-java.hook.in                   | 23 +++++++++++-----------
 .../ca-certificates-java_20180516.bb               | 11 ++++++++---
 2 files changed, 19 insertions(+), 15 deletions(-)

-- 
2.7.4



^ permalink raw reply	[flat|nested] 14+ messages in thread

* [meta-java][PATCH 1/3] ca-certificates-java: Fix sysconfdir for -native recipe
  2018-09-07 18:10 [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure Yevgeny Popovych
@ 2018-09-07 18:10 ` Yevgeny Popovych
  2018-09-17 14:39   ` André Draszik
  2018-09-07 18:10 ` [meta-java][PATCH 2/3] ca-certificates-java: Don't fail when called via hook on do_rootfs Yevgeny Popovych
                   ` (2 subsequent siblings)
  3 siblings, 1 reply; 14+ messages in thread
From: Yevgeny Popovych @ 2018-09-07 18:10 UTC (permalink / raw)
  To: openembedded-devel; +Cc: andre.draszik

When ca-certificates-java-native is built, sysconfdir variable will
be set to value that includes WORKDIR.
Avoid patching source with this value - use sysconfdir_native.

Change-Id: I8ac79c3cd5016a8139d9d8c8d58bc2976d0b6fa3
Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
---
 .../ca-certificates-java/ca-certificates-java_20180516.bb        | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb b/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
index 2db1915..7db5110 100644
--- a/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
+++ b/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
@@ -41,9 +41,14 @@ do_patch_append () {
     bb.build.exec_func('do_fix_sysconfdir', d)
 }
 
+# sysconfdir will include absolute native sysroot path in -native builds, avoid this
+# (see 36.24 of https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#faq)
+SYSCONFDIR_VALUE_class-target = "${sysconfdir}"
+SYSCONFDIR_VALUE_class-native = "${sysconfdir_native}"
+
 do_fix_sysconfdir () {
-	sed -e 's|/etc/ssl/certs/java|${sysconfdir}/ssl/certs/java|g' \
-	    -i ${S}/src/main/java/org/debian/security/UpdateCertificates.java
+    sed -e 's|/etc/ssl/certs/java|${SYSCONFDIR_VALUE}/ssl/certs/java|g' \
+        -i ${S}/src/main/java/org/debian/security/UpdateCertificates.java
 }
 
 do_compile () {
-- 
2.7.4



^ permalink raw reply related	[flat|nested] 14+ messages in thread

* [meta-java][PATCH 2/3] ca-certificates-java: Don't fail when called via hook on do_rootfs
  2018-09-07 18:10 [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure Yevgeny Popovych
  2018-09-07 18:10 ` [meta-java][PATCH 1/3] ca-certificates-java: Fix sysconfdir for -native recipe Yevgeny Popovych
@ 2018-09-07 18:10 ` Yevgeny Popovych
  2018-09-17 14:44   ` André Draszik
  2018-09-07 18:10 ` [meta-java][PATCH 3/3] ca-certificates-java: Distinguish between SYSROOT and D Yevgeny Popovych
  2018-09-17 15:10 ` [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure André Draszik
  3 siblings, 1 reply; 14+ messages in thread
From: Yevgeny Popovych @ 2018-09-07 18:10 UTC (permalink / raw)
  To: openembedded-devel; +Cc: andre.draszik

It is possible that ca-certificates-java hook will be called via
update-ca-certificates hook during do_roofs (the case when D is set
and JVM_LIBDIR is not).
This is a valid case so don't fail.

Change-Id: I908e2f0acec487c41499543014014e29919bd6ab
Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
---
 .../ca-certificates-java/ca-certificates-java.hook.in               | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes-core/ca-certificates-java/ca-certificates-java/ca-certificates-java.hook.in b/recipes-core/ca-certificates-java/ca-certificates-java/ca-certificates-java.hook.in
index 89c764f..611a4ef 100755
--- a/recipes-core/ca-certificates-java/ca-certificates-java/ca-certificates-java.hook.in
+++ b/recipes-core/ca-certificates-java/ca-certificates-java/ca-certificates-java.hook.in
@@ -14,9 +14,9 @@ jvm_libdir="@@libdir_jvm@@"
 if [ -n "${D:-}" ] ; then
     # called from postinst as part of image build on host
     if [ -z "${JVM_LIBDIR:-}" ] ; then
-        # should never happen, this is supposed to be passed in
-        echo "$0: no JVM_LIBDIR specified" >&2
-        false
+        # if JVM_LIBDIR is not present - we were called as a hook
+        echo "called as a hook of ca-certificates on do_rootfs, exiting"
+        exit 0
     fi
 fi
 if [ -n "${JVM_LIBDIR:-}" ] ; then
-- 
2.7.4



^ permalink raw reply related	[flat|nested] 14+ messages in thread

* [meta-java][PATCH 3/3] ca-certificates-java: Distinguish between SYSROOT and D
  2018-09-07 18:10 [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure Yevgeny Popovych
  2018-09-07 18:10 ` [meta-java][PATCH 1/3] ca-certificates-java: Fix sysconfdir for -native recipe Yevgeny Popovych
  2018-09-07 18:10 ` [meta-java][PATCH 2/3] ca-certificates-java: Don't fail when called via hook on do_rootfs Yevgeny Popovych
@ 2018-09-07 18:10 ` Yevgeny Popovych
  2018-09-17 15:00   ` André Draszik
  2018-09-17 15:10 ` [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure André Draszik
  3 siblings, 1 reply; 14+ messages in thread
From: Yevgeny Popovych @ 2018-09-07 18:10 UTC (permalink / raw)
  To: openembedded-devel; +Cc: andre.draszik

This fixes ca-certificates-java-hook invocation via
update-ca-certificates on build host and as a native tool.
Provide SYSROOT variable in the postinst and consume it in the script,
like ca-certificates recipe does.

SYSROOT is set whenever the script is executed on the build host
(do_rootfs, or as native dependency).
D is only set during do_rootfs.

Change-Id: Ifbf50ca705a98012e1357ebf5afa33c07ea6cd87
Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
---
 .../ca-certificates-java/ca-certificates-java.hook.in   | 17 ++++++++---------
 .../ca-certificates-java_20180516.bb                    |  2 +-
 2 files changed, 9 insertions(+), 10 deletions(-)

diff --git a/recipes-core/ca-certificates-java/ca-certificates-java/ca-certificates-java.hook.in b/recipes-core/ca-certificates-java/ca-certificates-java/ca-certificates-java.hook.in
index 611a4ef..5e89dd9 100755
--- a/recipes-core/ca-certificates-java/ca-certificates-java/ca-certificates-java.hook.in
+++ b/recipes-core/ca-certificates-java/ca-certificates-java/ca-certificates-java.hook.in
@@ -8,20 +8,21 @@
 # and package update in OE, so the distinction between cases 2)
 # and 3) isn't perfect.
 
+# SYSROOT is set whenever the script is executed on the build host
+# (do_rootfs, or as native dependency).
+# D is only set during do_rootfs.
+
 self=$(basename $0)
-jvm_libdir="@@libdir_jvm@@"
+jvm_libdir="${JVM_LIBDIR:-@@libdir_jvm@@}"
 
-if [ -n "${D:-}" ] ; then
-    # called from postinst as part of image build on host
+if [ -n "${SYSROOT:-}" ] ; then
+    # called on build host - from postinst (directly or as a hook) or as a native tool
     if [ -z "${JVM_LIBDIR:-}" ] ; then
         # if JVM_LIBDIR is not present - we were called as a hook
         echo "called as a hook of ca-certificates on do_rootfs, exiting"
         exit 0
     fi
 fi
-if [ -n "${JVM_LIBDIR:-}" ] ; then
-    jvm_libdir="${JVM_LIBDIR}"
-fi
 
 for JAVA in icedtea7-native/bin/java \
             openjdk-8-native/bin/java openjdk-8/bin/java openjre-8/bin/java \
@@ -58,6 +59,4 @@ else
     while read filename ; do
         echo "+${filename}"
     done
-fi | SYSROOT="${D:-}" ${JAVA} -Xmx64m \
-                              -jar ${D:-}@@datadir_java@@/@@JARFILENAME@@ \
-                              -storepass changeit
+fi | ${JAVA} -Xmx64m -jar ${D:-}@@datadir_java@@/@@JARFILENAME@@ -storepass changeit
diff --git a/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb b/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
index 7db5110..2f2536d 100644
--- a/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
+++ b/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
@@ -100,7 +100,7 @@ pkg_postinst_${PN} () {
 	    fi
 	    JVM_LIBDIR=$NATIVE_ROOT${libdir_jvm}
 	fi
-	JVM_LIBDIR=$JVM_LIBDIR $D${sbindir}/create-ca-certificates-java
+	SYSROOT=$D JVM_LIBDIR=$JVM_LIBDIR $D${sbindir}/create-ca-certificates-java
 }
 
 RDEPENDS_${PN} = "ca-certificates"
-- 
2.7.4



^ permalink raw reply related	[flat|nested] 14+ messages in thread

* Re: [meta-java][PATCH 1/3] ca-certificates-java: Fix sysconfdir for -native recipe
  2018-09-07 18:10 ` [meta-java][PATCH 1/3] ca-certificates-java: Fix sysconfdir for -native recipe Yevgeny Popovych
@ 2018-09-17 14:39   ` André Draszik
  2018-09-19  9:48     ` Yevgeny Popovych
  0 siblings, 1 reply; 14+ messages in thread
From: André Draszik @ 2018-09-17 14:39 UTC (permalink / raw)
  To: openembedded-devel

On Fri, 2018-09-07 at 21:10 +0300, Yevgeny Popovych wrote:
> When ca-certificates-java-native is built, sysconfdir variable will
> be set to value that includes WORKDIR.

What is your use-case for a -native version of this?

> Avoid patching source with this value - use sysconfdir_native.
> 
> Change-Id: I8ac79c3cd5016a8139d9d8c8d58bc2976d0b6fa3
> Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
> ---
>  .../ca-certificates-java/ca-certificates-java_20180516.bb        | 9
> +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes-core/ca-certificates-java/ca-certificates-
> java_20180516.bb b/recipes-core/ca-certificates-java/ca-certificates-
> java_20180516.bb
> index 2db1915..7db5110 100644
> --- a/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
> +++ b/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
> @@ -41,9 +41,14 @@ do_patch_append () {
>      bb.build.exec_func('do_fix_sysconfdir', d)
>  }
>  
> +# sysconfdir will include absolute native sysroot path in -native builds,
> avoid this
> +# (see 36.24 of 
> https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#faq)
> +SYSCONFDIR_VALUE_class-target = "${sysconfdir}"
> +SYSCONFDIR_VALUE_class-native = "${sysconfdir_native}"
> +
>  do_fix_sysconfdir () {
> -	sed -e 's|/etc/ssl/certs/java|${sysconfdir}/ssl/certs/java|g' \
> -	    -i
> ${S}/src/main/java/org/debian/security/UpdateCertificates.java
> +    sed -e 's|/etc/ssl/certs/java|${SYSCONFDIR_VALUE}/ssl/certs/java|g' \
> +        -i ${S}/src/main/java/org/debian/security/UpdateCertificates.java
>  }
>  

No.

It's probably best to remove the BBCLASSEXTEND statement in this recipe
instead, as it was never tested, and is unlikely to be needed.

The whole idea is to make this independent of the build machine paths. If
you want a -native version of this, you still need to make sure to point
this into the yocto sysroot. Otherwise this will try to write to the *build
machine's* /etc/ directory!

If you really want a -native version, you need to point this into the
sysroot, and update this dynamically because of sstate usage, too.


Cheers,
Andre'




^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [meta-java][PATCH 2/3] ca-certificates-java: Don't fail when called via hook on do_rootfs
  2018-09-07 18:10 ` [meta-java][PATCH 2/3] ca-certificates-java: Don't fail when called via hook on do_rootfs Yevgeny Popovych
@ 2018-09-17 14:44   ` André Draszik
  2018-09-19  9:49     ` Yevgeny Popovych
  0 siblings, 1 reply; 14+ messages in thread
From: André Draszik @ 2018-09-17 14:44 UTC (permalink / raw)
  To: openembedded-devel

On Fri, 2018-09-07 at 21:10 +0300, Yevgeny Popovych wrote:
> It is possible that ca-certificates-java hook will be called via
> update-ca-certificates hook during do_roofs (the case when D is set
> and JVM_LIBDIR is not).
> This is a valid case so don't fail.
> 
> Change-Id: I908e2f0acec487c41499543014014e29919bd6ab
> Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
> ---
>  .../ca-certificates-java/ca-certificates-java.hook.in               | 6
> +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-core/ca-certificates-java/ca-certificates-java/ca-
> certificates-java.hook.in b/recipes-core/ca-certificates-java/ca-
> certificates-java/ca-certificates-java.hook.in
> index 89c764f..611a4ef 100755
> --- a/recipes-core/ca-certificates-java/ca-certificates-java/ca-
> certificates-java.hook.in
> +++ b/recipes-core/ca-certificates-java/ca-certificates-java/ca-
> certificates-java.hook.in
> @@ -14,9 +14,9 @@ jvm_libdir="@@libdir_jvm@@"
>  if [ -n "${D:-}" ] ; then
>      # called from postinst as part of image build on host
>      if [ -z "${JVM_LIBDIR:-}" ] ; then
> -        # should never happen, this is supposed to be passed in
> -        echo "$0: no JVM_LIBDIR specified" >&2
> -        false
> +        # if JVM_LIBDIR is not present - we were called as a hook
> +        echo "called as a hook of ca-certificates on do_rootfs, exiting"
> +        exit 0

I don't understand how silently not creating / updating the Java certificate
store any more is good? True, there is an issue here, but I'd say that this
should actually do something useful, not just pretend to have done
something.

Cheers,
Andre'




^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [meta-java][PATCH 3/3] ca-certificates-java: Distinguish between SYSROOT and D
  2018-09-07 18:10 ` [meta-java][PATCH 3/3] ca-certificates-java: Distinguish between SYSROOT and D Yevgeny Popovych
@ 2018-09-17 15:00   ` André Draszik
  2018-09-19 10:09     ` Yevgeny Popovych
  0 siblings, 1 reply; 14+ messages in thread
From: André Draszik @ 2018-09-17 15:00 UTC (permalink / raw)
  To: openembedded-devel

On Fri, 2018-09-07 at 21:10 +0300, Yevgeny Popovych wrote:
> This fixes ca-certificates-java-hook invocation via
> update-ca-certificates on build host and as a native tool.
> Provide SYSROOT variable in the postinst and consume it in the script,
> like ca-certificates recipe does.
> 
> SYSROOT is set whenever the script is executed on the build host
> (do_rootfs, or as native dependency).
> D is only set during do_rootfs.
> 

I think I'm missing something...
It looks like this patch switches the hook script to use $SYSROOT instead of
$D, and SYSROOT is set to $D in the postinst explicitly.

In both cases, the expansion of $SYSROOT or $D will yield the same. How is
that fixing anything? What am I missing?


Cheers,
Andre'


> Change-Id: Ifbf50ca705a98012e1357ebf5afa33c07ea6cd87
> Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
> ---
>  .../ca-certificates-java/ca-certificates-java.hook.in   | 17 ++++++++--
> -------
>  .../ca-certificates-java_20180516.bb                    |  2 +-
>  2 files changed, 9 insertions(+), 10 deletions(-)
> 
> diff --git a/recipes-core/ca-certificates-java/ca-certificates-java/ca-
> certificates-java.hook.in b/recipes-core/ca-certificates-java/ca-
> certificates-java/ca-certificates-java.hook.in
> index 611a4ef..5e89dd9 100755
> --- a/recipes-core/ca-certificates-java/ca-certificates-java/ca-
> certificates-java.hook.in
> +++ b/recipes-core/ca-certificates-java/ca-certificates-java/ca-
> certificates-java.hook.in
> @@ -8,20 +8,21 @@
>  # and package update in OE, so the distinction between cases 2)
>  # and 3) isn't perfect.
>  
> +# SYSROOT is set whenever the script is executed on the build host
> +# (do_rootfs, or as native dependency).
> +# D is only set during do_rootfs.
> +
>  self=$(basename $0)
> -jvm_libdir="@@libdir_jvm@@"
> +jvm_libdir="${JVM_LIBDIR:-@@libdir_jvm@@}"
>  
> -if [ -n "${D:-}" ] ; then
> -    # called from postinst as part of image build on host
> +if [ -n "${SYSROOT:-}" ] ; then
> +    # called on build host - from postinst (directly or as a hook) or as
> a native tool
>      if [ -z "${JVM_LIBDIR:-}" ] ; then
>          # if JVM_LIBDIR is not present - we were called as a hook
>          echo "called as a hook of ca-certificates on do_rootfs, exiting"
>          exit 0
>      fi
>  fi
> -if [ -n "${JVM_LIBDIR:-}" ] ; then
> -    jvm_libdir="${JVM_LIBDIR}"
> -fi
>  
>  for JAVA in icedtea7-native/bin/java \
>              openjdk-8-native/bin/java openjdk-8/bin/java openjre-
> 8/bin/java \
> @@ -58,6 +59,4 @@ else
>      while read filename ; do
>          echo "+${filename}"
>      done
> -fi | SYSROOT="${D:-}" ${JAVA} -Xmx64m \
> -                              -jar ${D:-}@@datadir_java@@/@@JARFILENAME@@ 
> \
> -                              -storepass changeit
> +fi | ${JAVA} -Xmx64m -jar ${D:-}@@datadir_java@@/@@JARFILENAME@@
> -storepass changeit
> diff --git a/recipes-core/ca-certificates-java/ca-certificates-
> java_20180516.bb b/recipes-core/ca-certificates-java/ca-certificates-
> java_20180516.bb
> index 7db5110..2f2536d 100644
> --- a/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
> +++ b/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
> @@ -100,7 +100,7 @@ pkg_postinst_${PN} () {
>  	    fi
>  	    JVM_LIBDIR=$NATIVE_ROOT${libdir_jvm}
>  	fi
> -	JVM_LIBDIR=$JVM_LIBDIR $D${sbindir}/create-ca-certificates-java
> +	SYSROOT=$D JVM_LIBDIR=$JVM_LIBDIR $D${sbindir}/create-ca-
> certificates-java
>  }
>  
>  RDEPENDS_${PN} = "ca-certificates"
> -- 
> 2.7.4
> 



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure
  2018-09-07 18:10 [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure Yevgeny Popovych
                   ` (2 preceding siblings ...)
  2018-09-07 18:10 ` [meta-java][PATCH 3/3] ca-certificates-java: Distinguish between SYSROOT and D Yevgeny Popovych
@ 2018-09-17 15:10 ` André Draszik
  2018-09-19  9:45   ` Yevgeny Popovych
  3 siblings, 1 reply; 14+ messages in thread
From: André Draszik @ 2018-09-17 15:10 UTC (permalink / raw)
  To: openembedded-devel

On Fri, 2018-09-07 at 21:10 +0300, Yevgeny Popovych wrote:
> This series fixes several issues with ca-certificates-java:
> * when used as a native tool
> * failure on do_rootfs

Can you share complete logs? I'd like to understand the do_rootfs issues you
are seeing (I don't see any).

> This doesn't fix all the issues and there is definitely a room for
> improvement.

What other issues?

> I presume that running it on the target doesn't work - at least
> ${sysconfdir} is
> not expanded in the hook.

True.

> I also think that will be best to drop create-ca-certificates-java usage
> in
> the postinst and let it be called as a hook of ca-certificates. This will
> allow
> us to remove some code and simplify both script and recipe.

You can't do that, because ca-certificates could be installed before ca-
certificates-java. In which case the hook will not be run.

> 
> It would be great if others could test their use cases;
> and clarify them - is create-ca-certificates-java really needed?.

As per above.

Cheers,
Andre'

> 
> Yevgeny Popovych (3):
>   ca-certificates-java: Fix sysconfdir for -native recipe
>   ca-certificates-java: Don't fail when called via hook on do_rootfs
>   ca-certificates-java: Distinguish between SYSROOT and D
> 
>  .../ca-certificates-java.hook.in                   | 23 +++++++++++----
> -------
>  .../ca-certificates-java_20180516.bb               | 11 ++++++++---
>  2 files changed, 19 insertions(+), 15 deletions(-)
> 
> -- 
> 2.7.4
> 



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure
  2018-09-17 15:10 ` [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure André Draszik
@ 2018-09-19  9:45   ` Yevgeny Popovych
  0 siblings, 0 replies; 14+ messages in thread
From: Yevgeny Popovych @ 2018-09-19  9:45 UTC (permalink / raw)
  To: André Draszik, openembedded-devel

Hi Andre,

Thanks for the feedback!


On 09/17/2018 06:10 PM, André Draszik wrote:
> On Fri, 2018-09-07 at 21:10 +0300, Yevgeny Popovych wrote:
>> This series fixes several issues with ca-certificates-java:
>> * when used as a native tool
>> * failure on do_rootfs
> 
> Can you share complete logs? I'd like to understand the do_rootfs issues you
> are seeing (I don't see any).

The issue is that during do_rootfs, ca-certificates postinst calls
ca-certificates-java hook and the hook fails. (didn't save the log, sorry)
This is what patch #2 tries to fix (ca-certificates-java: Don't fail when called via hook on do_rootfs).

Richard also saw this issue when he tried another patch
(http://lists.openembedded.org/pipermail/openembedded-devel/2018-August/120066.html).
Although that doesn't matter IMO, I am using deb `PACKAGE_CLASSES`,
and Richard supposedly uses ipk (the default one).

> 
>> This doesn't fix all the issues and there is definitely a room for
>> improvement.
> 
> What other issues?

At least the use case for the target (the one mentioned below) and
some postinst issues that may appear (didn't test that).

> 
>> I presume that running it on the target doesn't work - at least
>> ${sysconfdir} is
>> not expanded in the hook.
> 
> True.
> 
>> I also think that will be best to drop create-ca-certificates-java usage
>> in
>> the postinst and let it be called as a hook of ca-certificates. This will
>> allow
>> us to remove some code and simplify both script and recipe.
> 
> You can't do that, because ca-certificates could be installed before ca-
> certificates-java. In which case the hook will not be run.

This can't really happen.
In OE, all packages are first unpacked and only then, in a separate step, the postinst are run.
This means that during do_rootfs, ca-certificates will always have the java hook present.

In addition to that, having the empty postinst in ca-certificates-java is desirable
for target/runtime because on upgrades, the hook should be run by ca-certificates
and our ca-certificates-java package should do nothing in this case.
What I mean is that the package should just be a way to deliver the hook.

> 
>>
>> It would be great if others could test their use cases;
>> and clarify them - is create-ca-certificates-java really needed?.
> 
> As per above.
> 
> Cheers,
> Andre'
> 
>>
>> Yevgeny Popovych (3):
>>   ca-certificates-java: Fix sysconfdir for -native recipe
>>   ca-certificates-java: Don't fail when called via hook on do_rootfs
>>   ca-certificates-java: Distinguish between SYSROOT and D
>>
>>  .../ca-certificates-java.hook.in                   | 23 +++++++++++----
>> -------
>>  .../ca-certificates-java_20180516.bb               | 11 ++++++++---
>>  2 files changed, 19 insertions(+), 15 deletions(-)
>>
>> -- 
>> 2.7.4
>>
> 

-- 
Sincerely,
Yevgeny Popovych


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [meta-java][PATCH 1/3] ca-certificates-java: Fix sysconfdir for -native recipe
  2018-09-17 14:39   ` André Draszik
@ 2018-09-19  9:48     ` Yevgeny Popovych
  2018-09-19 14:27       ` André Draszik
  0 siblings, 1 reply; 14+ messages in thread
From: Yevgeny Popovych @ 2018-09-19  9:48 UTC (permalink / raw)
  To: André Draszik, openembedded-devel



On 09/17/2018 05:39 PM, André Draszik wrote:
> On Fri, 2018-09-07 at 21:10 +0300, Yevgeny Popovych wrote:
>> When ca-certificates-java-native is built, sysconfdir variable will
>> be set to value that includes WORKDIR.
> 
> What is your use-case for a -native version of this?

I'm glad you asked as this should answer some questions..

I am building a package that contains prebuilt ca-certificates
(including what ca-certificates itself build and JKS),
for this package I need -native version of ca-certificates-java.
We have an immutable (readonly) rootfs, so running scripts at runtime is not an option.
With patches I have recently sent it works pretty well.

The bottom line is that there is a use-case for -native version.
Even if you don't have an immutable (readonly) rootfs - you might want to use it
that way because running scripts is quite error prone.

> 
>> Avoid patching source with this value - use sysconfdir_native.
>>
>> Change-Id: I8ac79c3cd5016a8139d9d8c8d58bc2976d0b6fa3
>> Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
>> ---
>>  .../ca-certificates-java/ca-certificates-java_20180516.bb        | 9
>> +++++++--
>>  1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/recipes-core/ca-certificates-java/ca-certificates-
>> java_20180516.bb b/recipes-core/ca-certificates-java/ca-certificates-
>> java_20180516.bb
>> index 2db1915..7db5110 100644
>> --- a/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
>> +++ b/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
>> @@ -41,9 +41,14 @@ do_patch_append () {
>>      bb.build.exec_func('do_fix_sysconfdir', d)
>>  }
>>  
>> +# sysconfdir will include absolute native sysroot path in -native builds,
>> avoid this
>> +# (see 36.24 of 
>> https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#faq)
>> +SYSCONFDIR_VALUE_class-target = "${sysconfdir}"
>> +SYSCONFDIR_VALUE_class-native = "${sysconfdir_native}"
>> +
>>  do_fix_sysconfdir () {
>> -	sed -e 's|/etc/ssl/certs/java|${sysconfdir}/ssl/certs/java|g' \
>> -	    -i
>> ${S}/src/main/java/org/debian/security/UpdateCertificates.java
>> +    sed -e 's|/etc/ssl/certs/java|${SYSCONFDIR_VALUE}/ssl/certs/java|g' \
>> +        -i ${S}/src/main/java/org/debian/security/UpdateCertificates.java
>>  }
>>  
> 
> No.
> 
> It's probably best to remove the BBCLASSEXTEND statement in this recipe
> instead, as it was never tested, and is unlikely to be needed.

We have a use-case for -native and this series fixes it.

> 
> The whole idea is to make this independent of the build machine paths. If
> you want a -native version of this, you still need to make sure to point
> this into the yocto sysroot. Otherwise this will try to write to the *build
> machine's* /etc/ directory!
> 
> If you really want a -native version, you need to point this into the
> sysroot, and update this dynamically because of sstate usage, too.

Ok, I suppose that ${sysconfdir_native} has mislead you -
it does _not_ resolve to an absolute path into native sysroot.
The value of ${sysconfdir_native} is always "/etc", it does not mangle in any way (that's why I have used it).
So this don't have any issue with sstate or else.


> 
> 
> Cheers,
> Andre'
> 
> 

-- 
Sincerely,
Yevgeny Popovych


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [meta-java][PATCH 2/3] ca-certificates-java: Don't fail when called via hook on do_rootfs
  2018-09-17 14:44   ` André Draszik
@ 2018-09-19  9:49     ` Yevgeny Popovych
  0 siblings, 0 replies; 14+ messages in thread
From: Yevgeny Popovych @ 2018-09-19  9:49 UTC (permalink / raw)
  To: André Draszik, openembedded-devel



On 09/17/2018 05:44 PM, André Draszik wrote:
> On Fri, 2018-09-07 at 21:10 +0300, Yevgeny Popovych wrote:
>> It is possible that ca-certificates-java hook will be called via
>> update-ca-certificates hook during do_roofs (the case when D is set
>> and JVM_LIBDIR is not).
>> This is a valid case so don't fail.
>>
>> Change-Id: I908e2f0acec487c41499543014014e29919bd6ab
>> Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
>> ---
>>  .../ca-certificates-java/ca-certificates-java.hook.in               | 6
>> +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/recipes-core/ca-certificates-java/ca-certificates-java/ca-
>> certificates-java.hook.in b/recipes-core/ca-certificates-java/ca-
>> certificates-java/ca-certificates-java.hook.in
>> index 89c764f..611a4ef 100755
>> --- a/recipes-core/ca-certificates-java/ca-certificates-java/ca-
>> certificates-java.hook.in
>> +++ b/recipes-core/ca-certificates-java/ca-certificates-java/ca-
>> certificates-java.hook.in
>> @@ -14,9 +14,9 @@ jvm_libdir="@@libdir_jvm@@"
>>  if [ -n "${D:-}" ] ; then
>>      # called from postinst as part of image build on host
>>      if [ -z "${JVM_LIBDIR:-}" ] ; then
>> -        # should never happen, this is supposed to be passed in
>> -        echo "$0: no JVM_LIBDIR specified" >&2
>> -        false
>> +        # if JVM_LIBDIR is not present - we were called as a hook
>> +        echo "called as a hook of ca-certificates on do_rootfs, exiting"
>> +        exit 0
> 
> I don't understand how silently not creating / updating the Java certificate
> store any more is good? True, there is an issue here, but I'd say that this
> should actually do something useful, not just pretend to have done
> something.

I have explained the issue in cover letter thread, quick summary:

I don't like how it is now, but this patch is just a fix.
IMO (as outlined in cover letter thread),
it would be nicer to have the ca-certificates call the hook,
and make postinst of this recipe a no-op.
I can implement this if you agree (either instead of this change or on top of it - I would prefer on top).

> 
> Cheers,
> Andre'
> 
> 

-- 
Sincerely,
Yevgeny Popovych


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [meta-java][PATCH 3/3] ca-certificates-java: Distinguish between SYSROOT and D
  2018-09-17 15:00   ` André Draszik
@ 2018-09-19 10:09     ` Yevgeny Popovych
  0 siblings, 0 replies; 14+ messages in thread
From: Yevgeny Popovych @ 2018-09-19 10:09 UTC (permalink / raw)
  To: André Draszik, openembedded-devel



On 09/17/2018 06:00 PM, André Draszik wrote:
> On Fri, 2018-09-07 at 21:10 +0300, Yevgeny Popovych wrote:
>> This fixes ca-certificates-java-hook invocation via
>> update-ca-certificates on build host and as a native tool.
>> Provide SYSROOT variable in the postinst and consume it in the script,
>> like ca-certificates recipe does.
>>
>> SYSROOT is set whenever the script is executed on the build host
>> (do_rootfs, or as native dependency).
>> D is only set during do_rootfs.
>>
> 
> I think I'm missing something...
> It looks like this patch switches the hook script to use $SYSROOT instead of
> $D, and SYSROOT is set to $D in the postinst explicitly.
> 
> In both cases, the expansion of $SYSROOT or $D will yield the same. How is
> that fixing anything? What am I missing?

The only difference would be between usage as a native tool and on do_rootfs.
SYSROOT is always set when run on build host and it points to the files we want to modify.
D is used only on do_rootfs and is used to find the hook (jar). On do_roofs these are equal.

> 
> 
> Cheers,
> Andre'
> 
> 
>> Change-Id: Ifbf50ca705a98012e1357ebf5afa33c07ea6cd87
>> Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
>> ---
>>  .../ca-certificates-java/ca-certificates-java.hook.in   | 17 ++++++++--
>> -------
>>  .../ca-certificates-java_20180516.bb                    |  2 +-
>>  2 files changed, 9 insertions(+), 10 deletions(-)
>>
>> diff --git a/recipes-core/ca-certificates-java/ca-certificates-java/ca-
>> certificates-java.hook.in b/recipes-core/ca-certificates-java/ca-
>> certificates-java/ca-certificates-java.hook.in
>> index 611a4ef..5e89dd9 100755
>> --- a/recipes-core/ca-certificates-java/ca-certificates-java/ca-
>> certificates-java.hook.in
>> +++ b/recipes-core/ca-certificates-java/ca-certificates-java/ca-
>> certificates-java.hook.in
>> @@ -8,20 +8,21 @@
>>  # and package update in OE, so the distinction between cases 2)
>>  # and 3) isn't perfect.
>>  
>> +# SYSROOT is set whenever the script is executed on the build host
>> +# (do_rootfs, or as native dependency).
>> +# D is only set during do_rootfs.
>> +
>>  self=$(basename $0)
>> -jvm_libdir="@@libdir_jvm@@"
>> +jvm_libdir="${JVM_LIBDIR:-@@libdir_jvm@@}"
>>  
>> -if [ -n "${D:-}" ] ; then
>> -    # called from postinst as part of image build on host
>> +if [ -n "${SYSROOT:-}" ] ; then
>> +    # called on build host - from postinst (directly or as a hook) or as
>> a native tool
>>      if [ -z "${JVM_LIBDIR:-}" ] ; then
>>          # if JVM_LIBDIR is not present - we were called as a hook
>>          echo "called as a hook of ca-certificates on do_rootfs, exiting"
>>          exit 0
>>      fi
>>  fi
>> -if [ -n "${JVM_LIBDIR:-}" ] ; then
>> -    jvm_libdir="${JVM_LIBDIR}"
>> -fi
>>  
>>  for JAVA in icedtea7-native/bin/java \
>>              openjdk-8-native/bin/java openjdk-8/bin/java openjre-
>> 8/bin/java \
>> @@ -58,6 +59,4 @@ else
>>      while read filename ; do
>>          echo "+${filename}"
>>      done
>> -fi | SYSROOT="${D:-}" ${JAVA} -Xmx64m \
>> -                              -jar ${D:-}@@datadir_java@@/@@JARFILENAME@@ 
>> \
>> -                              -storepass changeit
>> +fi | ${JAVA} -Xmx64m -jar ${D:-}@@datadir_java@@/@@JARFILENAME@@
>> -storepass changeit
>> diff --git a/recipes-core/ca-certificates-java/ca-certificates-
>> java_20180516.bb b/recipes-core/ca-certificates-java/ca-certificates-
>> java_20180516.bb
>> index 7db5110..2f2536d 100644
>> --- a/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
>> +++ b/recipes-core/ca-certificates-java/ca-certificates-java_20180516.bb
>> @@ -100,7 +100,7 @@ pkg_postinst_${PN} () {
>>  	    fi
>>  	    JVM_LIBDIR=$NATIVE_ROOT${libdir_jvm}
>>  	fi
>> -	JVM_LIBDIR=$JVM_LIBDIR $D${sbindir}/create-ca-certificates-java
>> +	SYSROOT=$D JVM_LIBDIR=$JVM_LIBDIR $D${sbindir}/create-ca-
>> certificates-java
>>  }
>>  
>>  RDEPENDS_${PN} = "ca-certificates"
>> -- 
>> 2.7.4
>>
> 

-- 
Sincerely,
Yevgeny Popovych


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [meta-java][PATCH 1/3] ca-certificates-java: Fix sysconfdir for -native recipe
  2018-09-19  9:48     ` Yevgeny Popovych
@ 2018-09-19 14:27       ` André Draszik
  2018-09-19 16:00         ` Yevgeny Popovych
  0 siblings, 1 reply; 14+ messages in thread
From: André Draszik @ 2018-09-19 14:27 UTC (permalink / raw)
  To: Yevgeny Popovych, openembedded-devel

On Wed, 2018-09-19 at 12:48 +0300, Yevgeny Popovych wrote:
> 
> On 09/17/2018 05:39 PM, André Draszik wrote:
> > On Fri, 2018-09-07 at 21:10 +0300, Yevgeny Popovych wrote:
> > > When ca-certificates-java-native is built, sysconfdir variable will
> > > be set to value that includes WORKDIR.
> > 
> > What is your use-case for a -native version of this?
> 
> I'm glad you asked as this should answer some questions..
> 
> I am building a package that contains prebuilt ca-certificates
> (including what ca-certificates itself build and JKS),
> for this package I need -native version of ca-certificates-java.
> We have an immutable (readonly) rootfs, so running scripts at runtime is
> not an option.
> With patches I have recently sent it works pretty well.
> 
> The bottom line is that there is a use-case for -native version.
> Even if you don't have an immutable (readonly) rootfs - you might want to
> use it
> that way because running scripts is quite error prone.
> 
> > 
> > > Avoid patching source with this value - use sysconfdir_native.
> > > 
> > > Change-Id: I8ac79c3cd5016a8139d9d8c8d58bc2976d0b6fa3
> > > Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
> > > ---
> > >  .../ca-certificates-java/ca-certificates-java_20180516.bb        | 9
> > > +++++++--
> > >  1 file changed, 7 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/recipes-core/ca-certificates-java/ca-certificates-
> > > java_20180516.bb b/recipes-core/ca-certificates-java/ca-certificates-
> > > java_20180516.bb
> > > index 2db1915..7db5110 100644
> > > --- a/recipes-core/ca-certificates-java/ca-certificates-
> > > java_20180516.bb
> > > +++ b/recipes-core/ca-certificates-java/ca-certificates-
> > > java_20180516.bb
> > > @@ -41,9 +41,14 @@ do_patch_append () {
> > >      bb.build.exec_func('do_fix_sysconfdir', d)
> > >  }
> > >  
> > > +# sysconfdir will include absolute native sysroot path in -native
> > > builds,
> > > avoid this
> > > +# (see 36.24 of 
> > > https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#faq
> > > )
> > > +SYSCONFDIR_VALUE_class-target = "${sysconfdir}"
> > > +SYSCONFDIR_VALUE_class-native = "${sysconfdir_native}"
> > > +
> > >  do_fix_sysconfdir () {
> > > -	sed -e 's|/etc/ssl/certs/java|${sysconfdir}/ssl/certs/java|g' \
> > > -	    -i
> > > ${S}/src/main/java/org/debian/security/UpdateCertificates.java
> > > +    sed -e
> > > 's|/etc/ssl/certs/java|${SYSCONFDIR_VALUE}/ssl/certs/java|g' \
> > > +        -i
> > > ${S}/src/main/java/org/debian/security/UpdateCertificates.java
> > >  }
> > >  
> > 
> > No.
> > 
> > It's probably best to remove the BBCLASSEXTEND statement in this recipe
> > instead, as it was never tested, and is unlikely to be needed.
> 
> We have a use-case for -native and this series fixes it.
> 
> > 
> > The whole idea is to make this independent of the build machine paths.
> > If
> > you want a -native version of this, you still need to make sure to point
> > this into the yocto sysroot. Otherwise this will try to write to the
> > *build
> > machine's* /etc/ directory!
> > 
> > If you really want a -native version, you need to point this into the
> > sysroot, and update this dynamically because of sstate usage, too.
> 
> Ok, I suppose that ${sysconfdir_native} has mislead you -
> it does _not_ resolve to an absolute path into native sysroot.
> The value of ${sysconfdir_native} is always "/etc", it does not mangle in
> any way (that's why I have used it).

Exactly, so the code in UpdateCertificates.java will try to access
${SYSCONFDIR_VALUE}/ssl/certs/java, i.e. /etc/ssl/certs/java, which is what
your linux distro might or might not provide. It's not what yocto provides.


Cheers,
Andre'




^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [meta-java][PATCH 1/3] ca-certificates-java: Fix sysconfdir for -native recipe
  2018-09-19 14:27       ` André Draszik
@ 2018-09-19 16:00         ` Yevgeny Popovych
  0 siblings, 0 replies; 14+ messages in thread
From: Yevgeny Popovych @ 2018-09-19 16:00 UTC (permalink / raw)
  To: André Draszik, openembedded-devel



On 09/19/2018 05:27 PM, André Draszik wrote:
> On Wed, 2018-09-19 at 12:48 +0300, Yevgeny Popovych wrote:
>>
>> On 09/17/2018 05:39 PM, André Draszik wrote:
>>> On Fri, 2018-09-07 at 21:10 +0300, Yevgeny Popovych wrote:
>>>> When ca-certificates-java-native is built, sysconfdir variable will
>>>> be set to value that includes WORKDIR.
>>>
>>> What is your use-case for a -native version of this?
>>
>> I'm glad you asked as this should answer some questions..
>>
>> I am building a package that contains prebuilt ca-certificates
>> (including what ca-certificates itself build and JKS),
>> for this package I need -native version of ca-certificates-java.
>> We have an immutable (readonly) rootfs, so running scripts at runtime is
>> not an option.
>> With patches I have recently sent it works pretty well.
>>
>> The bottom line is that there is a use-case for -native version.
>> Even if you don't have an immutable (readonly) rootfs - you might want to
>> use it
>> that way because running scripts is quite error prone.
>>
>>>
>>>> Avoid patching source with this value - use sysconfdir_native.
>>>>
>>>> Change-Id: I8ac79c3cd5016a8139d9d8c8d58bc2976d0b6fa3
>>>> Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
>>>> ---
>>>>  .../ca-certificates-java/ca-certificates-java_20180516.bb        | 9
>>>> +++++++--
>>>>  1 file changed, 7 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/recipes-core/ca-certificates-java/ca-certificates-
>>>> java_20180516.bb b/recipes-core/ca-certificates-java/ca-certificates-
>>>> java_20180516.bb
>>>> index 2db1915..7db5110 100644
>>>> --- a/recipes-core/ca-certificates-java/ca-certificates-
>>>> java_20180516.bb
>>>> +++ b/recipes-core/ca-certificates-java/ca-certificates-
>>>> java_20180516.bb
>>>> @@ -41,9 +41,14 @@ do_patch_append () {
>>>>      bb.build.exec_func('do_fix_sysconfdir', d)
>>>>  }
>>>>  
>>>> +# sysconfdir will include absolute native sysroot path in -native
>>>> builds,
>>>> avoid this
>>>> +# (see 36.24 of 
>>>> https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#faq
>>>> )
>>>> +SYSCONFDIR_VALUE_class-target = "${sysconfdir}"
>>>> +SYSCONFDIR_VALUE_class-native = "${sysconfdir_native}"
>>>> +
>>>>  do_fix_sysconfdir () {
>>>> -	sed -e 's|/etc/ssl/certs/java|${sysconfdir}/ssl/certs/java|g' \
>>>> -	    -i
>>>> ${S}/src/main/java/org/debian/security/UpdateCertificates.java
>>>> +    sed -e
>>>> 's|/etc/ssl/certs/java|${SYSCONFDIR_VALUE}/ssl/certs/java|g' \
>>>> +        -i
>>>> ${S}/src/main/java/org/debian/security/UpdateCertificates.java
>>>>  }
>>>>  
>>>
>>> No.
>>>
>>> It's probably best to remove the BBCLASSEXTEND statement in this recipe
>>> instead, as it was never tested, and is unlikely to be needed.
>>
>> We have a use-case for -native and this series fixes it.
>>
>>>
>>> The whole idea is to make this independent of the build machine paths.
>>> If
>>> you want a -native version of this, you still need to make sure to point
>>> this into the yocto sysroot. Otherwise this will try to write to the
>>> *build
>>> machine's* /etc/ directory!
>>>
>>> If you really want a -native version, you need to point this into the
>>> sysroot, and update this dynamically because of sstate usage, too.
>>
>> Ok, I suppose that ${sysconfdir_native} has mislead you -
>> it does _not_ resolve to an absolute path into native sysroot.
>> The value of ${sysconfdir_native} is always "/etc", it does not mangle in
>> any way (that's why I have used it).
> 
> Exactly, so the code in UpdateCertificates.java will try to access
> ${SYSCONFDIR_VALUE}/ssl/certs/java, i.e. /etc/ssl/certs/java, which is what
> your linux distro might or might not provide. It's not what yocto provides.

That's why we provide it with SYSROOT variable
(which is prepended to what becomes "/etc/ssl/certs/java")
because we want it to operate on a specific SYSROOT/file, not build host files.
Even if you forgot to specify SYSROOT - you are not going to screw up
your system because these files should be owned by root.

>> 
> Cheers,
> Andre'
> 
> 

-- 
Sincerely,
Yevgeny Popovych


^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2018-09-19 16:00 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-09-07 18:10 [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure Yevgeny Popovych
2018-09-07 18:10 ` [meta-java][PATCH 1/3] ca-certificates-java: Fix sysconfdir for -native recipe Yevgeny Popovych
2018-09-17 14:39   ` André Draszik
2018-09-19  9:48     ` Yevgeny Popovych
2018-09-19 14:27       ` André Draszik
2018-09-19 16:00         ` Yevgeny Popovych
2018-09-07 18:10 ` [meta-java][PATCH 2/3] ca-certificates-java: Don't fail when called via hook on do_rootfs Yevgeny Popovych
2018-09-17 14:44   ` André Draszik
2018-09-19  9:49     ` Yevgeny Popovych
2018-09-07 18:10 ` [meta-java][PATCH 3/3] ca-certificates-java: Distinguish between SYSROOT and D Yevgeny Popovych
2018-09-17 15:00   ` André Draszik
2018-09-19 10:09     ` Yevgeny Popovych
2018-09-17 15:10 ` [meta-java][PATCH 0/3] ca-certificates-java: Fix usage as a native tool, do_rootfs failure André Draszik
2018-09-19  9:45   ` Yevgeny Popovych

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.