Google Chrome repository

Hi there!
Can somebody tell me the repository’s URL added when you install Google Chrome?
Thank you.

the contrib repo and it would Chromium as it the open source version openSUSE:Contrib - openSUSE

there are some official Google repos for Chrome but iirc Chromium is actually more featured (don’t recall differences or why)

I know. But I’m looking for Chrome official repo.
Thanks a lot.

http://dl.google.com/linux/rpm/stable/i386
http://dl.google.com/linux/rpm/stable/x86_64

Thank you very much!

sorry of bringing back this old topic.
i am also looking for a valid adress for google chrome. i remember, back in february when i first installed chrome, it added an adress by itself. the same things happening in ubuntu: it adds a adress in software source.
it is not the case today in opensuse. the only way to update is to check online for the chrome version, download the .rpm and install it manually.

I have this:
http://dl.google.com/linux/chrome/rpm/stable/x86_6
and in yast software manager I have this:
| google-chrome-stable - Google Chrome
|
|

|| Alternate Version
|—|
| Installed Version
|
| Version:
| 38.0.2125.101-1
| 38.0.2125.101-1
|
| Build Time:
| Wed 01 Oct 2014 05:37:30 AM CEST
| Wed 01 Oct 2014 05:37:30 AM CEST
|
| Install Time:
|| Wed 08 Oct 2014 08:52:32 PM CEST
|
| Package Group:
| Applications/Internet
| Applications/Internet
|
| License:
| Multiple, see http://chrome.google.com/
| Multiple, see http://chrome.google.com/
|
| Installed Size:
| 172.6 MiB
| 172.6 MiB
|
| Download Size:
| 57.9 MiB
| 0 B
|
| Distribution:
|||
| Vendor:
| Google Inc.
| Google Inc.
|
| Packager:
| Chrome Linux Team <chromium-dev@chromium.org>
| Chrome Linux Team <chromium-dev@chromium.org>
|
| Architecture:
| x86_64
| x86_64
|
| Build Host:
|||
| URL:
| http://chrome.google.com/
| http://chrome.google.com/
|
| Source Package:
| google-chrome-stable-38.0.2125.101-1
| google-chrome-stable-38.0.2125.101-1
|
| Media No.:
| 0
| 0
|
| Authors:
|||

thanx a lot man, i actually added the adress:
http://dl.google.com/linux/rpm/stable/i386
and to my surprise, it worked.

For anyone that may look into this thread, like I did:
starting this month, March 2016, Google gave up their 32 bit Chrome for linux, so the old repository https://dl.google.com/linux/rpm/stable/i386 does no longer work, and thus no more updates.

Though, the 64 bit variant of the same repository is OK: https://dl.google.com/linux/rpm/stable/x86_64

Which is a good thing actually, 64 bit version works better anyway :slight_smile:

But that link doesn’t work, and hasn’t worked for a bit more than a week now. I don’t know what’s happening over at google, but they’re letting us down somewhat. I’ve had to disable that repo as it lengthens the time it takes to do my updates (waiting for the timeout which does happen every time for both the zypper ref and the zypper up). Clicking on your link for 64bit gets me (eventually)

This webpage is not available

ERR_CONNECTION_TIMED_OUT

which is normal as we aren’t supposed to access that location through the browser.

If I do a

zypper ref;zypper up

, I get a

Timeout exceeded when accessing ‘http://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml’.
.

Are you by any chance using a proxy? I had problem too accessing that url behind my proxy.

And this url should be put up somewhere instead of hiding in a forum post. There is not such a url on google’s page at least.

No, no proxy. The thing is, even if I had been using a proxy, I’ve been using that repository for years without any problem.

I just did a sudo zypper ref, and google-chrome repo updated with no errors or delays.

Here is my repo:

harry@intrepid:~> zypper lr -Pd
#  | Alias                           | Name                                       | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                                         | Service
---+---------------------------------+--------------------------------------------+---------+-----------+---------+----------+--------+---------------------------------------------------------------------------------------------+--------
 7 | packman                         | Packman 13.2 Repository                    | Yes     | (r ) Yes  | Yes     |   80     | rpm-md | http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_13.2/                               |        
...
 4 | google-chrome                   | google-chrome                              | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                                         |        

Note the different URL.

Sorry for the poor formatting; this is actually my first post here on the openSUSE forums!

Hope this helps.

–Harry

Well, I found out what the problem actually was for me.
After trying your suggestion, hhtoigo, which didn’t work by the way,
something started niggling at the back of my neck. I can’t remember
when, or why exactly, I did this, but the problem was an entry in
my /etc/hosts file for dl.google.com. I proceeded to remove the entry in
the /etc/hosts file, then put the original URL for the chrome entry in
Software Repositories in YAST, zypper ref, zypper up, and chrome updated.
My bad.
I also tried the URL you suggested hhtoigo after I fixed the /etc/hosts file, but
that didn’t work for me.
So, to sum it up: always note the changes you have made to your system,
and keep them up to date.
For me, this is solved.

The link I posted above, and the one I have in my repository list is with https:// , not http://
And just a few seconds ago, on a try of “refresh” worked OK (in yast2, “Software repositories” app).
Could you try again, with this change ?
I mean, this: https://dl.google.com/linux/rpm/stable/x86_64
I have no problem with, just now.

Mine originally (from chrome’s own setup) was http:. For completeness-sake, I modified the entry through YAST, and refreshed. It worked as well. So, everything is working still.

Ha-Joon: Ah, a rogue /etc/hosts entry! That will certainly do it. How often I have run into the same situation, having neglected in the heat of the moment to document in my captains-log a change I made to my system, and then forgetting all about it. Glad you found the issue and got it working.

I did some more testing here, and noticed something interesting (to me, at least). Modifying the URI of the google-chrome repo to any one of the following seems to work:
](https://dl.google.com/linux/rpm/stable/x86_64)|http://dl.google.com/linux/chrome/rpm/stable/x86_64| (set by Google’s rpm at install)|
|—|—|
|https://dl.google.com/linux/chrome/rpm/stable/x86_64||
|https://dl.google.com/linux/rpm/stable/x86_64||

I set the URI of the chrome repo to each of the above addresses in turn, did a sudo zypper ref, and then a zypper search --repo google-chrome. In each case, the output was exactly the same:

S | Name                   | Summary                  | Type   
--+------------------------+--------------------------+--------
  | google-chrome-beta     | Google Chrome (beta)     | package
i | google-chrome-stable   | Google Chrome            | package
  | google-chrome-unstable | Google Chrome (unstable) | package

Cheers,

Harry Toigo