robin_listas:
On 2015-08-20 22:46, Downwitdvp wrote:
> I understood that part, just not how to fix it. I’m used to GUIs not
> command prompts.
Then use YaST
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I have the stable repository in my software repos. Here.
David@linux-gu7v:~> zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+---------------------------+------------------------------------+---------+-----------+---------+----------+--------+-----------------------------------------------------------------+--------
1 | google | google | Yes | ( p) Yes | Yes | 99 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
2 | openSUSE-13.2-0 | openSUSE-13.2-0 | No | ---- | Yes | 99 | yast2 | hd:///?device=/dev/disk/by-id/scsi-1hp_x702w |
3 | packman | packman | Yes | (r ) Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_13.2/ |
4 | repo-debug | openSUSE-13.2-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/13.2/repo/oss/ |
5 | repo-debug-update | openSUSE-13.2-Update-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.2/ |
6 | repo-debug-update-non-oss | openSUSE-13.2-Update-Debug-Non-Oss | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.2-non-oss/ |
7 | repo-non-oss | openSUSE-13.2-Non-Oss | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.2/repo/non-oss/ |
8 | repo-oss | openSUSE-13.2-Oss | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.2/repo/oss/ |
9 | repo-source | openSUSE-13.2-Source | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/13.2/repo/oss/ |
10 | repo-update | openSUSE-13.2-Update | Yes | ( p) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.2/ |
11 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss | Yes | ( p) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.2-non-oss/ |
David@linux-gu7v:~>
But when I try to install at the end its always the unstable version that its telling me its installing.
Then install google-chrome-stable:
sudo zypper in google-chrome-stable
The repo contains google-chrome-stable, google-chrome-beta, and google-chrome-unstable. Apparently all three packages provide “google-chrome”, so zypper picks the highest version which is google-chrome-unstable.
Or use YaST->Software Management as suggested already, and search for “chrome” or “google-chrome” and select the one you want.
On 2015-08-21 00:26, wolfi323 wrote:
> The repo contains google-chrome-stable, google-chrome-beta, and
> google-chrome-unstable. Apparently all three packages provide
> “google-chrome”,
Oh!
> so zypper picks the highest version which is
> google-chrome-unstable.
Makes sense, of course.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
linux-h4xb:/home/wa6mbz # zypper in google-chrome
Error building the cache:
[google|Linux Software Repositories – Google ] Valid metadata not found at specified URL
Warning: Skipping repository ‘google’ because of the above error.
Error building the cache:
[google1|Linux Software Repositories – Google ] Valid metadata not found at specified URL
Warning: Skipping repository ‘google1’ because of the above error.
Loading repository data…
Reading installed packages…
‘google-chrome’ not found in package names. Trying capabilities.
No provider of ‘google-chrome’ found.
Resolving package dependencies…
I_A:
a few things to try
#1 use chromium which is basically chrome minus some google tweaks to get a full functioning chromium do:
you need packman for mp4 support, if you have packman just do
sudo zypper in chromium chromium-ffmpeg chromium-pdf-plugin chromium-pepper-flash
#2 if you really want chrome add google’s repo try
sudo zypper ar https://www.google.com/linuxrepositories google
sudo zypper in google-chrome
ps I don’t use any google chrome so I have not tested this.
This version of the repo worked in that it allowed me to install
google-chrome but it was version google-chrome-unable-46…
sudo zypper ar http://dl.google.com/linux/rpm/stable/x86_64
I_A:
I did say I’ve never used google and I made a mistake about their repo’s, remove the above repository it’s wrong
sudo zypper rr https://www.google.com/linuxrepositories
then add this one http://dl.google.com/linux/rpm/stable/x86_64
sudo zypper ar http://dl.google.com/linux/rpm/stable/x86_64
refresh the repositories and install google-chrome
sudo zypper ref
sudo zypper in google-chrome
google does not have a propper repo so the above is for 64bit only for 32 bit you’d need to use
http://dl.google.com/linux/rpm/stable/i386
I tried the line with the dl.google.com … and it gave me chrome version 46, an unstable version !!!
Downwitdvp:
My repos. And no I’m not sure why I got the unstable version.
David@linux-gu7v:~> zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+---------------------------+------------------------------------+---------+-----------+---------+----------+--------+-----------------------------------------------------------------+--------
1 | openSUSE-13.2-0 | openSUSE-13.2-0 | No | ---- | Yes | 99 | yast2 | hd:///?device=/dev/disk/by-id/scsi-1hp_x702w |
2 | packman | packman | Yes | (r ) Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_13.2/ |
3 | repo-debug | openSUSE-13.2-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/13.2/repo/oss/ |
4 | repo-debug-update | openSUSE-13.2-Update-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.2/ |
5 | repo-debug-update-non-oss | openSUSE-13.2-Update-Debug-Non-Oss | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.2-non-oss/ |
6 | repo-non-oss | openSUSE-13.2-Non-Oss | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.2/repo/non-oss/ |
7 | repo-oss | openSUSE-13.2-Oss | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.2/repo/oss/ |
8 | repo-source | openSUSE-13.2-Source | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/13.2/repo/oss/ |
9 | repo-update | openSUSE-13.2-Update | Yes | ( p) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.2/ |
10 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss | Yes | ( p) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.2-non-oss/ |
David@linux-gu7v:~>
On 2015-08-21 22:16, wa6mbz bb wrote:
>
> linux-h4xb:/home/wa6mbz # zypper in google-chrome
> Error building the cache:
> [google|https://www.google.com/linuxrepositories] Valid metadata not
> found at specified URL
That’s not the correct URL. Read the rest of the thread, it is written
somewhere
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2015-08-21 22:36, wa6mbz bb wrote:
> I tried the line with the dl.google.com … and it gave me chrome version
> 46, an unstable version !!!
This exact question has been answered in a post in this thread. Just
read the entire thread
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
[google-chrome]
name=google-chrome
enabled=1
autorefresh=1
baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
type=rpm-md
keeppackages=0
My version as above gives me and error and then it asks if I want to install
the unable version, ie, version 46, so something must be wrong with the url !!!
I_A:
I forgot you need to give the repository a local name, the name can be google
sudo zypper ar http://dl.google.com/linux/rpm/stable/x86_64 google
then do a refresh and ask for chrome
sudo zypper ref
sudo zypper in google-chrome
wa6mbz_bb:
My version as above gives me and error and then it asks if I want to install
the unable version, ie, version 46, so something must be wrong with the url !!!
No.
As has been said already, read the thread, in particular the few posts before yours.
In short, explicitly install google-chrome-stable.
There are 3 verions in the repository. You have to tell it to install the stable version. As has been said look through the earlier posts in the thread and the command to do that is there, it worked for me. It really is as simple as what they’re saying.