Heinz Diehl <htd...@fritha.org> wrote:
> F22, in short: first running "dnf --refresh upgrade" shows some new
> packets. Then "dnf clean all" followed by "dnf --refresh upgrade"
> shows the same packets to be updated, and *some more*.
Yes, you are correct. Several people have verified this behavior,
they reported this as bug, and according to Fedora and DNF developers
it is intentional.
"dnf --refresh" is more like "dnf clean expire-cache", which sometimes
gives additional updates to plain "dnf upgrade", but there still seems
some caching involved that keeps it from providing all updates available.
"dnf clean all" does the job, of course, but for that specific purpose,
"dnf clean metadata" is sufficient. Both force dnf to download and
rebuild all metadata. The metadata is the key to the solution.
Unfortunately, this needs lots of bandwidth and CPU. If you just want
fresh updates, there's usually no need to process the big base fedora
metadata over and over again.
For me, this does the trick:
dnf --disablerepo=fedora clean metadata ; dnf upgrade
It's pretty fast and gives latest updates. Well, there's still a chance
to get redirected to a mirror which isn't synced with latest stuff. But
there's not much you can do about that.
Greetings, Andreas
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
