On Fri, May 31, 2019 at 12:43 PM stan via users
On Fri, 31 May 2019 10:40:45 -0400
Garry Williams <gtwilliams(a)gmail.com> wrote:
> On Fri, May 24, 2019 at 4:21 AM Samuel Sieb <samuel(a)sieb.net> wrote:
> > Can't you just use "--refresh"?
> Nether one of those suggestions gets around the problem I seem to
> garry@ifr$ sudo dnf makecache;sudo dnf upgrade
[snip mangled quote]
> Failed to synchronize cache for repo 'updates'
> The only way I found is to clean all. :-(
It sounds like it is using a stale repository. Have you any plugins
that restrict repositories or is there some setting in
the /etc/dnf/dnf.conf file?
Don't know about plugins, but
garry@ifr$ cat /etc/dnf/dnf.conf
What happens if you do
dnf clean metadata
dnf clean all?
I don't know. The next time I can try is Monday.
But, of course, the issue is why this happens in the first place. I
suspect no one here knows, so I will open a bug against dnf next week.
Perhaps a developer will request data that will shed light on the
What happens without the makecache?
That command was suggested instead of "dnf clean all". The reason I
showed it was that it didn't help when I received "Error: Failed to
synchronize cache for repo 'updates'" without it.
Are there any anomalies in the /etc/yum.repos.d directory?
are enabled that should be disabled, and vice versa.
Only modular is disabled. Normal otherwise.