Opened 3 years ago

Last modified 3 years ago

#64183 new defect

tellico @2.3.12: search fails with SSL negotional failed message

Reported by: ryrrah Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc:
Port: tellico

Description

I'm running Tellico 2.3.12 (which by the way is seriously out of date, as I was informed by the Tellico maintainer on the KDE forum).

When I try to search for a book using the Google Book Search database, I get this message:

Could not connect to host www.googleapis.com: SSL negotiation failed.

I tried one or two other data sources and some of them fail with the same message.

I have the Google API that may be required and have successfully used that on a Fedora Linux setup running Tellico 3.4.1.

I even tried building a newer version of Tellico, but it requires newer version of KDE. Installing that is beyond my skill level.

I do not even know whether this is a problem with Tellico or with some other component. I would appreciate any suggestions on how to find the problem and resolve it.

Change History (3)

comment:1 Changed 3 years ago by ryrrah

Version: 2.7.02.7.1

comment:2 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: tellico ssl removed
Summary: Tellico search fails with SSL negotional failed messagetellico @2.3.12: search fails with SSL negotional failed message

Seems likely that such failures might already be resolved by updating to the latest version, but as you say, updating to a newer version is not possible right now. Per the tellico download page:

The latest released version of Tellico for the KDE4 platform is 2.3.12, released on January 29, 2017.

If you or anyone would like to help get KDE5 into MacPorts, consult the tickets that mention "KF5".

comment:3 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Still, the fact that this old version is mentioned explicitly on the tellico download page suggests some level of support from the developers, or that they or someone else (perhaps some other package manager) already has patches to fix this issue. If anyone can find such patches, we can apply them to the port.

Note: See TracTickets for help on using tickets.