Re: Issues with Google Chrome, PyCharm, Steam and other third-party repos in Fedora 29 prereleases

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Fri, Oct 26, 2018 at 5:11 AM Silvia Sánchez <bhkohane@xxxxxxxxx> wrote:

Hello all,

This didn't happen to me with the last version  (F28)  but I didn't install Workstation, I installed KDE Spin.  So now my question is:  Does this affect to all Fedoras, including Spins and Labs, or is it an issue that for some reason affects Workstation only?

Kind regards.
Silvia
FAS:  Lailah


It affects anyone who has installed the fedora-workstation-repos package, which is installed by default only on Fedora Workstation (as it really doesn’t do anything useful except in the context of GNOME Software).



On Thu, 25 Oct 2018 at 21:01, Stephen Gallagher <sgallagh@xxxxxxxxxx> wrote:
On Thu, Oct 25, 2018 at 3:06 PM Till Hofmann <thofmann@xxxxxxxxxxxxxxxxx> wrote:
>
>
>
> On 10/25/18 4:02 PM, Stephen Gallagher wrote:
> > It was discovered[1] a short while ago that, due to a packaging
> > mistake in the fedora-workstation-repos package, upgrades from Fedora
> > 28->Fedora 29 would replace the /etc/yum.repos.d/*.repo files provided
> > from that package with their default configuration.
> >
> > What this meant in practice is that anyone who was using those
> > repositories in Fedora 28 would find them silently disabled in Fedora
> > 29. In particular, this would mean that they might not notice that
> > they were not receiving updates, particularly (in the case of Chrome)
> > security updates.
> >
> > This has been fixed for F29 Final, but if you have upgraded from
> > F28->F29 prior to today (such as at the Beta release), you should
> > check and verify that your expected repos are correctly enabled.
> >
>
> Is it possible that this also happened on F28? I haven't upgraded to F29
> yet, but surprisingly my google-chrome repo is disabled and I'm using
> Chrome 68.0.3440.84 from 2 months ago. I'm pretty sure I never disabled
> the repo manually.
>

If there was a post-release update to the fedora-workstation-repos
package in F28, it's entirely possible, yes. It would have had the
same issue.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux