Problem: nothing provides libcrypto.so.10 needed by google-chrome-unstable

English Applications
#1

Zypper raises an error when I try to upgrade google-chrome-unstable to the latest version on openSUSE 11.4:

Problem: nothing provides libcrypto.so.10 needed by google-chrome-unstable-19.0.1068.1-126852.i386

From which repo can I get the package providing libcrypto.so.10?

#2

On 2012-03-22 00:16, rugbygangster wrote:

> From which repo can I get the package providing libcrypto.so.10?

The newest available is 1.0, not 10.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#3

There are a couple ways to address this.

First, particularly if you already have openSSL and any other crypto apps/libraries installed, update your system, in your case that might be all that’s needed to pick up the most current crypto libraries.


$zypper up

But, in general
One way is to recognize that oftentimes although a more recent library version is “required” and older version will work fine. In these cases you can create a symbolic link to the older library (There are numerous threads in these forums describing how to do this if this is what you want to do).

But, I’d generally recommend first that you go ahead and just install either the new library if you can find it… Although it’s probably possible to use a zypper command with the “provides” flag I’ve found it’s simpler to find either by

HTH,
TS

#4

On 2012-03-22 03:46, tsu2 wrote:
> But, in general
> One way is to recognize that oftentimes although a more recent library
> version is “required” and older version will work fine. In these cases
> you can create a symbolic link to the older library (There are numerous
> threads in these forums describing how to do this if this is what you
> want to do).

However, libcrypto.so.10 does not exist. It is a known problem with google
applications that want that wrong number. They think that the next version
to 0.9 is 10, when it is 1.0, that does indeed exist.

This came out long time ago, when google talk was developed:

View this
thread

The proposed solution at the time was to symlink it:


ln -s /lib/libcrypto.so.1.0.0 /lib/libcrypto.so.10
ln -s /lib/libssl.so.1.0.0 /lib/libssl.so.10

And mutandis mutandi for 64 bits.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#5

Thanks for replies! However, making symlinks is only a workaround. And what if people use Suse Studio, where you cannot ignore dependencies? Maybe the dummy package providing libcrypto.so.1.0.0 named as libcrypto.so.10 could be incorporated?

#6

On 2012-03-22 13:56, rugbygangster wrote:
>
> Thanks for replies! However, making symlinks is only a workaround. And
> what if people use Suse Studio, where you cannot ignore dependencies?
> Maybe the dummy package providing libcrypto.so.1.0.0 named as
> libcrypto.so.10 could be incorporated?

You can ask the packagers, but I’m afraid that the answer will be, as it
was before, no. There would be a problem when the real …so.10 comes. And
it is not their fault.

Or you can make an rpm package that creates the symlinks. A compatibility
package. It would not be the first one.

Or you can complain to google, the real culprits.

Or you can repackage it correctly, if the license permits. Something of the
sort was done for google talk, you should review the posts made here at the
time.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#7

It just occurred to me that your error sounded so familiar…

IMO you’re installing an old, outdated (as of today > 3mths old) version of Chrome.

Go download the latest package.
FYI as of today, my current Google Chrome version is 17.0.963.46

Don’t settle for less…

HTH,
TS

#8

No, I am trying to install the latest google-chrome-unstable-19.0.1068.1-126852.i386.

#9

Well,
Unstable is unstable. Someone is carrying forward an error that existed in “stable” as recently as 3 months ago.
Recommend you contact the Google builders to determine exactly what they did to fix the problem recently (or with any luck find it in their bugtraq). That’ll probably provide the recipe for what you should do.

HTH,
TS

#10

I’m attaching the compatibility package libcrypto-compat, which just makes a symlink to libcrypto.so.1.0.0 named libcrypto.so.10: http://ul.to/w96n7sxr