Your message dated Sat, 16 Feb 2019 11:36:33 +0000
with message-id <1550316993.21192.50.ca...@adam-barratt.org.uk>
and subject line Closing bugs for updates included in 9.8
has caused the Debian Bug report #921997,
regarding stretch-pu: package ca-certificates-java/20170929~deb9u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian....@packages.debian.org
Usertags: pu
Control: block 921748 with -1

Hi,

ca-certificates-java is uninstallable on armhf: #874276

The proposed patch has only been build-tested (on amd64), the resulting
(arch:all) package has *not* been tested on armhf at all.
But it does not look like it could make the situation worse.
The package has *not* been uploaded, waiting for an explicit ACK.


Andreas
diff -Nru ca-certificates-java-20170531+nmu1/debian/changelog 
ca-certificates-java-20170929~deb9u1/debian/changelog
--- ca-certificates-java-20170531+nmu1/debian/changelog 2017-06-15 
17:33:00.000000000 +0200
+++ ca-certificates-java-20170929~deb9u1/debian/changelog       2019-02-11 
05:34:52.000000000 +0100
@@ -1,3 +1,21 @@
+ca-certificates-java (20170929~deb9u1) stretch; urgency=medium
+
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann <a...@debian.org>  Mon, 11 Feb 2019 05:34:52 +0100
+
+ca-certificates-java (20170929) unstable; urgency=low
+
+  [ Gianfranco Costamagna ]
+  * Team upload.
+  * Ack previous NMU, thanks
+
+  [ Rico Tzschichholz ]
+  * Fix temporary jvm-*.cfg generation on armhf (Closes: #874276)
+    - the armhf installation path is different from other architectures.
+
+ -- Rico Tzschichholz <ric...@ubuntu.com>  Wed, 27 Sep 2017 17:17:59 +0200
+
 ca-certificates-java (20170531+nmu1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru ca-certificates-java-20170531+nmu1/debian/jks-keystore.hook.in 
ca-certificates-java-20170929~deb9u1/debian/jks-keystore.hook.in
--- ca-certificates-java-20170531+nmu1/debian/jks-keystore.hook.in      
2017-05-31 14:39:26.000000000 +0200
+++ ca-certificates-java-20170929~deb9u1/debian/jks-keystore.hook.in    
2017-09-27 17:17:59.000000000 +0200
@@ -53,7 +53,11 @@
     # the jre is not yet configured, but jvm.cfg is needed to run it
     temp_jvm_cfg=/etc/${jvm%-$arch}/jvm-$arch.cfg
     mkdir -p /etc/${jvm%-$arch}
-    printf -- "-server KNOWN\n" > $temp_jvm_cfg
+    if [ "$arch" == "armhf" ]; then
+        printf -- "-client KNOWN\n-server ALIASED_TO -client\n" > $temp_jvm_cfg
+    else
+        printf -- "-server KNOWN\n" > $temp_jvm_cfg
+    fi
 fi
 
 if dpkg-query --version >/dev/null; then
diff -Nru ca-certificates-java-20170531+nmu1/debian/postinst.in 
ca-certificates-java-20170929~deb9u1/debian/postinst.in
--- ca-certificates-java-20170531+nmu1/debian/postinst.in       2017-05-31 
14:39:26.000000000 +0200
+++ ca-certificates-java-20170929~deb9u1/debian/postinst.in     2017-09-27 
17:17:59.000000000 +0200
@@ -100,7 +100,11 @@
                 # the jre is not yet configured, but jvm.cfg is needed to run 
it
                 temp_jvm_cfg=/etc/${jvm%-$arch}/jvm-$arch.cfg
                 mkdir -p /etc/${jvm%-$arch}
-                printf -- "-server KNOWN\n" > $temp_jvm_cfg
+                if [ "$arch" == "armhf" ]; then
+                       printf -- "-client KNOWN\n-server ALIASED_TO -client\n" 
> $temp_jvm_cfg
+                else
+                       printf -- "-server KNOWN\n" > $temp_jvm_cfg
+                fi
             fi
 
             trap do_cleanup EXIT

--- End Message ---
--- Begin Message ---
Version: 9.8

Hi,

The update referenced by each of these bugs was included in this
morning's stretch point release.

Regards,

Adam

--- End Message ---

Reply via email to