Bug 1575098 - toggling f-w-r *disables security updates* for google-chrome installed from google website
Summary: toggling f-w-r *disables security updates* for google-chrome installed from g...
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-workstation-repositories
Version: 28
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-04 18:38 UTC by Alan Jenkins
Modified: 2018-12-03 18:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-12-03 18:23:58 UTC
Type: Bug

Attachments (Terms of Use)

Description Alan Jenkins 2018-05-04 18:38:29 UTC
Description of problem:

Installing and then removing fedora-workstation-repositories *disables security updates*, for the google-chrome package which has been installed from the google website.

Version-Release number of selected component (if applicable): 28-1.fc28

How reproducible: always

Steps to Reproduce:
1. Install Chrome from the RPM download at https://www.google.com/chrome/
2. dnf repolist --all
3. dnf install fedora-workstation-repositories
4. dnf remove fedora-workstation-repositories
5. dnf repolist --all

Actual results:
google-chrome remains installed.  But the google-chrome repo which is shown in step 2, is no longer present in step 5.

Expected results:

Don't mess with the security updates :).  Leave google-chrome.repo intact... somehow.

I would think it's possible to have a google-chrome-repo package, which conflicts with /etc/cron.daily/google-chrome, and is only a soft dependency of fedora-workstation-repositories.

That would avoid messing with google-chrome.repo when google-chrome-stable etc. is already installed.

Additional info:

/etc/yum.d/google-chrome.repo is not directly owned by google-chrome-stable etc., instead it is created by /etc/cron.daily/google-chrome.repo (which is also run by rpmscript or something).  Hence why RPM did not flag up this conflict automatically.

After the first run, the cronjob sets `repo_add_once="false"` in /etc/default/google-chrome.  Therefore, the cronjob does *not* recreate google-chrome.repo afterwards.

Comment 1 Alan Jenkins 2018-12-03 18:23:58 UTC
I withdraw this bug on my account, I hope that's OK.

fedora-workstation-repositories has been modified, and AIUI should no longer disable google-chrome.repo when *installed*.

google-chrome.repo is still be removed when fedora-workstation-repositories is removed.  (It is renamed to google-chrome.repo.rpmsave).

This solves the most important part of the problem, thanks!  ...I personally don't have anything else to ask for.

Note You need to log in before you can comment on or make changes to this bug.