Hi Don!

Your fix seems sensible - at least from my quick review : I lack time to properly maintain ca-certificate-java right now, so thanks for your time.

Small question : is your fix targeted for wheezy ? maybe you should also contact release team in advance to check if they are ok with this.

Regards,

On 13/11/2012 22:18, Don Armstrong wrote:
Control: tag -1 patch

Please find the attached patches which fix this problem. I've tested
them a bit, but please review them.

ca-certificates (20121112+nmu1) unstable; urgency=low

   * Non-maintainer upload
   * Breaks ca-certificates-java (<<20121112+nmu1); partially fixing #537051.
   * Provide update-ca-certificates and update-ca-certificates-fresh
     triggers.
   * Call the triggers using no-await so that the configuration files from
     the newer version of ca-certificates-java are in places before the
     upgrade. Closes: #537051.

ca-certificates-java (20121112+nmu1) unstable; urgency=low

   * Non-maintainer upload
   * Fix test for dpkg-query in postinst; there was an extraneous --version
     here. [Probably don't even need to bother to check for dpkg-query, but
     why not.] (Closes: #690204)
   * Library path for softokn3pkg and nsspkg is potentially wrong if there
     are multiple different paths; fix it.
   * Do not run the hook if ca-certificates-java has been removed but not
     purged.
   * Use the new trigger support provided by ca-certificates (>=20121112).

  -- Don Armstrong<d...@debian.org>   Mon, 12 Nov 2012 15:45:50 -0800


I plan on uploading an NMU for ca-certificates-java as soon as I have
an ACK from the ca-certificates team that the fix looks reasonable
(unless I hear from ca-certificates-java that they want to do it.) [I
can also upload a fixed ca-certificates and pull my changes into
ca-certificates unless y'all want to handle that.]


Don Armstrong


--
Damien

__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to