https://bugs.kde.org/show_bug.cgi?id=482144

--- Comment #2 from d.korev...@bessenland.nl ---
Bonjour Stéphane,

Je suis entièrement d'accord. Mais skrooge ne doit pas être bloqué, 
c'était ca le but de ce déclaration de bug. Il y a un workaround, mais 
pas évident. Changer le provider (comme 
exchangeratesapi.io), n'est pas possible tant que skrooge est bloqué.

Cordialement,
Derk Korevaar

On 01-03-2024 20:05, Stephane MANKOWSKI wrote:
> https://bugs.kde.org/show_bug.cgi?id=482144
>
> Stephane MANKOWSKI <steph...@mankowski.fr> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|REPORTED                    |RESOLVED
>           Resolution|---                         |UPSTREAM
>
> --- Comment #1 from Stephane MANKOWSKI <steph...@mankowski.fr> ---
> The issue is not in skrooge.
> The issue is due to grandtrunk.net that have an invalid certificate.
>
> You can use another source like exchangeratesapi.io.
>

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to