libgcrypt and google-chrome

drago01 drago01 at
Mon Apr 28 15:09:42 UTC 2014

On Mon, Apr 28, 2014 at 5:05 PM, Adam Williamson <awilliam at> wrote:
> On Mon, 2014-04-28 at 15:43 +0200, Fidel Leon wrote:
>> On Monday 28 April 2014 08:31:19 piruthiviraj natarajan wrote:
>> > Recent libgcrypt update to libgcrypt-1.6.1-2.fc21 doesn't allow you to
>> > install google-chrome current version in rawhide. The maintainer
>> > specifically removed the old .so compatibility with this new release. Is
>> > there any other way how to workaround this without downgrading the
>> package?
>> +1, it's a quite disruptive change, it breaks compatibility for a VERY MAJOR
>> software product! We're not talking about an obscure app living under a rock in
>> Github, we're talking about Google Chrome!
> Given the description of the actual changes behind the soname bump:
> "Unfortunately the rebase bumps soname to due to
> dropping some long-ago deprecated API calls. This should not break
> builds of any reasonably current software."
> I suspect the ugly hack of symlinking should work, for Chrome. But
> really, Google ought to do a new build. Or you could use Chromium;
> there's a COPR that carries it at
> ,
> though I can't vouch for the quality/safety personally at all (I don't
> use Chrome or Chromium).

How about filing a bug upstream i.e telling google about it? Might not
get you a fixed build ASAP but it is better then relying on
workarounds ...

More information about the test mailing list