On 27/6/21 21:28, Ed Greshko wrote:
On 27/06/2021 16:31, Stephen Morris wrote:
> Hi,
> I have just done a sudo dnf upgrade on F34 which I think upgraded
> 1311 packages. After the update finished I rebooted F34 and then ran
> discovery and it was still telling me there was 628 MB of F34
> Platform updates to put on, which I did put on. Why is dnf not
> installing all updates that are available? Is there a configuration
> that needs to be done to alleviate this that is not done in an "out
> of the box" install, or, is this telling me that we shouldn't be
> doing updates with dnf we should be using Discovery instead?
>
I've not looked at what goes on during the upgrade process. That is
going from a previous release of Fedora to a later version of
Fedora. I suspect that the upgrade process just compares what you
have on your system with what packages are
available in the fedora.repo (which doesn't change) and doesn't look
at the fedora-updates.repo since looking in both
places and keeping track of what package should be upgraded from which
repo would be much more work. Especially in
the case of where an update of some packages may change dependencies
or pull in packages not used previously.
So, it would be a much simpler process to upgrade from the released
repo and then do normal updates later.
I have always used dnf upgrade for normal
updates. From what I've found
dnf update and dnf upgrade do the same thing and apply updates/installs
from all active repositories, or is there a difference between the two?
I only looked at discover because I was looking at trying to use a
package that wasn't installed, and I was told to use Discover to install
it (I don't remember which package is was and I couldn't find how to
install it from Discover, so I finished up using flatpak).
regards,
Steve
Hey, at least it isn't like Windows. I have a Windows 10 VM that I
rarely use. When I do use it, and updates are
applied, it is a constant cycle of "Download updates, apply updates,
reboot" and rinse/repeat