Extra Repo listed (for Chrome) after I added just one

aggie · April 10, 2024, 2:02pm

So, I just installed 15.6 on my laptop (bare metal, not in a VM). I use Brave and Chrome browsers, so after install, I added those repos. However, when i ran Yast2 to check on something else, I noticed that there are TWO Chrome repos - the one I added and then a second one.

Where did that second come from?? Can I remove the second one

(Maybe because of the “wget” execution? because I see it is related to https, and the repo add is a http?)

This is what I executed to add the Chrome repo then install it:

# zypper ar http://dl.google.com/linux/chrome/rpm/stable/x86_64 Google-Chrome
# wget https://dl.google.com/linux/linux_signing_key.pub
# rpm --import  linux_signing_key.pub
# zypper in google-chrome-stable

.
And here is the list of repos - notice the two Chrome repos, the “Google-Chrome” entry that I added, and then the second one (lower-case, and shows as disabled).

# zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.

#  | Alias                       | Name                        | Enabled | GPG Check | Refresh | URI
---+-----------------------------+-----------------------------+---------+-----------+---------+------------------------------------------------------------------------
 1 | Google-Chrome               | Google-Chrome               | Yes     | (r ) Yes  | Yes     | http://dl.google.com/linux/chrome/rpm/stable/x86_64
 2 | brave-browser-beta          | Brave Browser - Beta        | Yes     | (r ) Yes  | Yes     | https://brave-browser-rpm-beta.s3.brave.com/x86_64
 3 | google-chrome               | google-chrome               | No      | ----      | ----    | https://dl.google.com/linux/chrome/rpm/stable/x86_64
 4 | repo-backports-debug-update | Update repository with up-> | No      | ----      | ----    | http://download.opensuse.org/update/leap/15.6/backports_debug/
 5 | repo-backports-update       | Update repository of open-> | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.6/backports/
 6 | repo-debug                  | Debug Repository            | No      | ----      | ----    | http://download.opensuse.org/debug/distribution/leap/15.6/repo/oss/
 7 | repo-debug-non-oss          | Debug Repository (Non-OSS)  | No      | ----      | ----    | http://download.opensuse.org/debug/distribution/leap/15.6/repo/non-oss/
 8 | repo-debug-update           | Update Repository (Debug)   | No      | ----      | ----    | http://download.opensuse.org/debug/update/leap/15.6/oss/
 9 | repo-debug-update-non-oss   | Update Repository (Debug,-> | No      | ----      | ----    | http://download.opensuse.org/debug/update/leap/15.6/non-oss/
10 | repo-non-oss                | Non-OSS Repository          | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/distribution/leap/15.6/repo/non-oss/
11 | repo-openh264               | Open H.264 Codec (openSUS-> | Yes     | (r ) Yes  | Yes     | http://codecs.opensuse.org/openh264/openSUSE_Leap/
12 | repo-oss                    | Main Repository             | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/distribution/leap/15.6/repo/oss/
13 | repo-sle-debug-update       | Update repository with de-> | No      | ----      | ----    | http://download.opensuse.org/debug/update/leap/15.6/sle/
14 | repo-sle-update             | Update repository with up-> | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.6/sle/
15 | repo-source                 | Source Repository           | No      | ----      | ----    | http://download.opensuse.org/source/distribution/leap/15.6/repo/oss/
16 | repo-update                 | Main Update Repository      | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.6/oss/
17 | repo-update-non-oss         | Update Repository (Non-Oss) | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.6/non-oss/

OrsoBruno · April 10, 2024, 2:06pm

deleted by user

aggie · April 10, 2024, 2:11pm

I edited my original and used zypper lr -u to show the repo URLs (same time as your reply).

malcolmlewis · April 10, 2024, 2:14pm

@aggie that’s because Google place a (sneaky?) cron job to run and add, see /etc/cron.daily/google-chrome.

aggie · April 10, 2024, 2:25pm

Wow - correct @malcolmlewis … opened that file in Kate and did a quick scan

So, do I need to keep both repos, or can I delete one of those?
(I avoid redundancy if possible)
.

[ snipped header comments ]
# $DEFAULTS_FILE is the same as setting the value to "false".

# System-wide package configuration.
DEFAULTS_FILE="/etc/default/google-chrome"

# sources.list setting for google-chrome updates.
REPOCONFIG="https://dl.google.com/linux/chrome/rpm/stable"
.
[ snipped another 500+ lines ]

malcolmlewis · April 10, 2024, 2:29pm

@aggie I would suggest removing the one you added, or remove the cron job and the repo created. AFAIK it will add the cron job on a google update, I don’t know because I have a script that removes it if it’s there after I update, which also disables the repo, don’t need it active all the time…

pavinjoseph · April 10, 2024, 2:57pm

I’ve installed Chrome and VSCode from external repos/RPMs, in both cases the repo configuration was added when installing the RPM using zypper.

I too found out adding the repo config manually was redundant, not sure if this is standard practice for all external RPMs
I would think so as otherwise it would be a chore to add them manually.

With the way it’s now:

Download external RPM and verify its hash
sudo zypper in ./path-to-rpm
Accept their new GPG key and finish installation. repo config is added automatically when installing.

OrsoBruno · April 10, 2024, 3:18pm

I think Google goes the extra mile here, not every “external” .rpm has a repo configured for openSUSE.
This is the rule for “1-Click-Install” files though and that causes several problems reported here on the forums.

aggie · April 10, 2024, 10:36pm

As a follow-up, I did as suggested by @malcolmlewis … I kept the duplicate Chrome repo listed (vs the one I initially created, which I’ve deleted)

3 | google-chrome https://dl.google.com/linux/chrome/rpm/stable/x86_64

A few minutes ago, I did a zypper dup and saw that Chrome had an update available, so did the update, then checked the Google site and yes, it is the current version now. So, the sneaky version works as expected.

system · April 17, 2024, 10:36pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.