https://bugs.kde.org/show_bug.cgi?id=425470
--- Comment #5 from amit ---
Ok - thanks for letting me know...
A
On Tue, 8 Sep 2020 at 11:32, Christoph Feck wrote:
>
> https://bugs.kde.org/show_bug.cgi?id=425470
>
> Christoph Feck changed:
>
>What|Removed |Adde
https://bugs.kde.org/show_bug.cgi?id=425470
Christoph Feck changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=425470
--- Comment #3 from amit ---
Hi Christoph, sorry, that is not what I am saying. The problem arose
when I built Qt5 from source *myself* without linking to OpenSSL. So
it's not a "this is broken on Neon" it's "if someone happens to (be
silly enough?) to
https://bugs.kde.org/show_bug.cgi?id=425470
--- Comment #2 from Christoph Feck ---
Are you sure Qt on neon is configured without OpenSSL?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425470
--- Comment #1 from amit ---
I now believe this is caused by the Qt5.14 package used having been configured
without an openssl option. Conditional compilation detects the lack of openssl
but sadly leads to the mismatch reported. It would be probably pre
