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?
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!
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 libgcrypt.so.20 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 http://copr.fedoraproject.org/coprs/churchyard/chromium-russianfedora/ , though I can't vouch for the quality/safety personally at all (I don't use Chrome or Chromium).
On Mon, Apr 28, 2014 at 5:05 PM, Adam Williamson awilliam@redhat.com 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 libgcrypt.so.20 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 http://copr.fedoraproject.org/coprs/churchyard/chromium-russianfedora/ , 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 ...
On Monday 28 April 2014 08:05:46 Adam Williamson wrote:
"Unfortunately the rebase bumps soname to libgcrypt.so.20 due to dropping some long-ago deprecated API calls. This should not break builds of any reasonably current software."
BTW it also "breaks" Remmina updates...
-Remove official Chrome and use a COPR or Chromium.... -Remove Remmina... and use Vinagre....
Seems like a plan.
On Monday 28 April 2014 23:28:28 Christopher Meng wrote:
No one should blame Fedora, you should blame can't follow the
updates.
Blame is a waste of time 8) At least from my part, I report with the healthy intention of get problems solved, not having fingers pointed at anyone...
On Mon, 2014-04-28 at 17:24 +0200, Fidel Leon wrote:
On Monday 28 April 2014 08:05:46 Adam Williamson wrote:
"Unfortunately the rebase bumps soname to libgcrypt.so.20 due to dropping some long-ago deprecated API calls. This should not break builds of any reasonably current software."
BTW it also "breaks" Remmina updates...
-Remove official Chrome and use a COPR or Chromium.... -Remove Remmina... and use Vinagre....
Seems like a plan.
Well, we have control over Remmina (we don't over binary builds of Chrome). It looks like Tomas tried to rebuild it the day he bumped libgcrypt, but the rebuild failed:
http://koji.fedoraproject.org/koji/buildinfo?buildID=512993
Someone happens to have filed a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1091796
i'll see if I can fix the rebuild today.
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 ...
------------------------------
Already filed it. But no response yet. https://productforums.google.com/forum/?utm_medium=email&utm_source=foot...
On Mon, Apr 28, 2014 at 8:31 AM, piruthiviraj natarajan < piruthiviraj@gmail.com> 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?
-
Adam Williamson -
Christopher Meng -
drago01 -
Fidel Leon -
piruthiviraj natarajan