Chrome doesn't properly configure repositories on Mageia 6
Reported by
ngomp...@gmail.com,
Jun 6 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36 Steps to reproduce the problem: 1. Download google-chrome rpm 2. Install it What is the expected behavior? A repo file in /etc/yum.repos.d (if the directory exists), and urpmi repo configured (if /etc/urpmi/urpmi.cfg exists). What went wrong? The repository configuration was not installed for DNF or urpmi, so Google Chrome cannot be updated after initial installation. Did this work before? No Chrome version: 59.0.3071.86 Channel: stable OS Version: Mageia 6 Flash Version: Shockwave Flash 24.0 r0 Mageia has adopted DNF (the successor to Yum) and included it as a secondary package manager in Mageia 6. It is equally supported and preloaded on all fresh Mageia 6 installs. This means that the setup typically used for RHEL/Fedora should work for Mageia now. PackageKit frontends rely on the Yum/DNF configuration, due to switching to the PackageKit-Dnf backend, so updating Chrome via tools like Plasma Discover or GNOME Software won't work either without the "yum configuration" installed.
,
Jun 6 2017
CC'ing MTV team so that they can take a look into it. In house do not have Mageia 6
,
Jun 7 2017
If I may, I'd suggest the following test: if /usr/sbin/urpmi exists, then do urpmi configuration. Otherwise don't. If /etc/yum.repos.d exists, add the .repo file as you do on Fedora systems.
,
Jul 20 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e482d0150e8698a5080f8add5d259e90547f4e0b commit e482d0150e8698a5080f8add5d259e90547f4e0b Author: Neal Gompa <ngompa13@gmail.com> Date: Thu Jul 20 18:54:47 2017 Add support for configuring DNF package manager for Mageia 6+ Mageia 6 introduces DNF as an alternative package manager. In addition, Mageia 6 switches the PackageKit backend to the DNF one, meaning that the urpmi configuration does not apply to tools like Apper, GNOME Software, and Plasma Discover, which use PackageKit as the package management backend. Since DNF (being the successor to Yum) is configured the same way as Yum is, let's reuse the Yum configuration setup for Fedora to configure it for Mageia. We do this by changing to declare an array PACKAGEMANAGERS and iterate through them and execute the actions for each PACKAGEMANAGER. This way, we can easily support future transitions and parallel package manager configurations from distributions in the future. Bug: 729888 Change-Id: I19a80ee1e150d8cfea53944a2030e6ea0ae1ce44 Reviewed-on: https://chromium-review.googlesource.com/572394 Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#488332} [modify] https://crrev.com/e482d0150e8698a5080f8add5d259e90547f4e0b/AUTHORS [modify] https://crrev.com/e482d0150e8698a5080f8add5d259e90547f4e0b/chrome/installer/linux/common/rpm.include [modify] https://crrev.com/e482d0150e8698a5080f8add5d259e90547f4e0b/chrome/installer/linux/common/rpmrepo.cron [modify] https://crrev.com/e482d0150e8698a5080f8add5d259e90547f4e0b/chrome/installer/linux/rpm/chrome.spec.template
,
Jul 26 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by ranjitkan@chromium.org
, Jun 6 2017