On Sat, Feb 21, 2026 at 9:54 AM Charles Dennett <[email protected]> wrote:
> > > [...] Comments in the script state: > > # This script is part of the google-chrome package. > # > # It creates the repository configuration file for package updates, since > # we cannot do this during the google-chrome installation since the > repository > # is locked. > # > # This functionality can be controlled by creating the $DEFAULTS_FILE and > # setting "repo_add_once" to "true" or "false" as desired. An empty > # $DEFAULTS_FILE is the same as setting the value to "false". > > and then the DEFAULTS_FILE has this: > > cat /etc/default/google-chrome > repo_add_once="false" > > > I have not seen this reported here nor in the Fedora Discussion Forums > at https://discussion.fedoraproject.org/. Googling pulls up some old > reports. Looks like this has happened in the past. There's a variable > in the script called SUB_KEY_LIST and the best I can tell, they forgot > to add the current key to it. A key is supplied in the script. > I have not encountered the issue. Here: % cat /etc/default/google-chrome repo_add_once="true" -- George N. White III
-- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
