/etc/yum.repos.d/google-chrome-beta [google-chrome-beta] name=google-chrome-beta baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64 enabled=0 gpgcheck=1 gpgkey=https://dl.google.com/linux/linux_signing_key.pub or do you mean dnf install google-chrome-unstable google-chrome-stable-86.0.4240.198-1.x86_64 is the current verion that is stable Didn't install it, but unstable is google-chrome-unstable x86_64 88.0.4315.5-1 [google-chrome] name=google-chrome baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64 enabled=1 gpgcheck=1 gpgkey=https://dl.google.com/linux/linux_signing_key.pub On 16 Nov 2020 at 16:11, Patrick O'Callaghan wrote: Subject: Re: Update chrome? From: Patrick O'Callaghan <pocallaghan@xxxxxxxxx> To: users@xxxxxxxxxxxxxxxxxxxxxxx Date sent: Mon, 16 Nov 2020 16:11:38 +0000 Send reply to: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> > On Mon, 2020-11-16 at 10:40 -0500, Todd Zullinger wrote: > > Patrick O'Callaghan wrote: > > > On Mon, 2020-11-16 at 07:01 -0500, Neal Becker wrote: > > > > There are widely reported zero-days related to chrome, and chrome is > > > > telling me "update" in the top right corner. If I do update outside of > > > > dnf, will the next dnf update still be effective? > > > > I've seen Chrome (when installed via the official rpm > > packaging from Google) report that it needs restarted to > > pick up an update that's been installed, but I've never seen > > it update itself on Linux. (Not that I can't be wrong about > > that, of course.) > > > > The google-chrome repo managed by Google is generally kept > > up to date. Are you positive that you haven't installed an > > update to Chrome since the last time you restarted the app? > > > > I know that several vulnerabilities discussed recently have > > already been patched and shipped to the google-chrome repo. > > The latest stable version on the Chrome release page is > > 86.0.4240.198, which is what's been in the google-chrome > > package repo since the middle of last week. > > > > > AFAIK the built-in updater is not going to coordinate with the RPM > > > database, so I wouldn't do this myself. It may not even install to the > > > same location. > > > > > > You can always try: > > > > > > # dnf --enablerepo=updates-testing update google-chrome > > > > > > to see if there's a more recent version in the testing repo. > > > > Since google-chrome is not in the Fedora repos, it won't be > > in updates or updates-testing. ;) > > Oops, good point. Make that the Chrome repo(s) :-) > > poc > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx +------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@xxxxxxxx mailto:msetzerii@xxxxxxxxx Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+ _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
