18 Oct
2010
18 Oct
'10
3:55 p.m.
On Mon, 18 Oct 2010 08:32:54 +0200, Jan de Groot <jan@jgc.homeip.net> wrote:
On Sun, 2010-10-17 at 18:50 +0200, Pierre Schmitz wrote:
This is not that critical. This is caused by some kind of bug/missing feature in ca-certificates-java which needs an update. Maybe I'll ask Jan if I could adopt that package.
That's not a problem with ca-certificates-java, but with java itself. One of the certificates is signed with a hash that is not supported by java.
Yes, we are both right. But the new upstream version has a workaround/alternative way to import that cert. -- Pierre Schmitz, https://users.archlinux.de/~pierre