Ask Your Question
1

Gnome software showing updates, despite using dnf --refresh upgrade PLUS pkcon refresh

asked 2016-12-07 03:30:37 -0500

thingummybob gravatar image

Curious thing this morning.

Run my customary

$ sudo dnf --refresh upgrade

Nothing found, all up to date. Okay, that's fine. Then a notification from Gnome software manager pops up saying "OS updates..." (whatever the precise wording). Undeterred, I then run

$ pkcon refresh

and go back to the Gnome SM and refresh. After a reboot and a

$ sudo dnf clean all

I STILL have these updates showing under gnome only, despite my terminal dnf commands insisting that everything is up to date.

The specific software that Gnome wants to install is. I should point out that I don't have uefi boot:

grub2
grub2-efi
grub2-tools
pcsc-lite-libs
perl-Encode
perl-Pod-Simple
pigz
pptp
tbb

So which part of my installation is 'broken' needs refreshing? Do I delete a bunch of temp files? Any ideas?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2016-12-07 22:13:49 -0500

florian gravatar image

Try running pkcon refresh force.

So, if you ran dnf --refresh update before and then refreshed PackageKit data your Gnome Software should be silent again.

edit flag offensive delete link more

Comments

Thanks. In the end I got around it a different way. I noted the version numbers of the above packages as listed under Gnome Sofware. Using

# dnf reinstall <package-name>

which simply reinstalled the current versions, NOT the upgraded packages listed in packagekit, I enabled the Fedora-updates-testing repo, and installed just those packages from there! I also read through more docs and have now set metadata expire=90 etc. I guess something got out of synch when pushing updates?

thingummybob gravatar imagethingummybob ( 2016-12-08 03:09:26 -0500 )edit

What you initially described is totally normal and will always happen if you have one system with two package managers (dnf and packagekit) that do not share the same package meta information. They don't even use the same mirror to sync their data.

One way to fix this long-term is to disable (mask) PackageKit service.

Enable testing repos is different. You get your packages earlier than before, they may be unstable or buggy, and you are supposed to provide feedback (karma rating and bug report).

90 minutes or 90 days?

florian gravatar imageflorian ( 2016-12-08 08:50:33 -0500 )edit

And btw: I don't think reinstalling a package solves the problem you described. I rather guess that packagekit refreshed its package data in the meantime.

florian gravatar imageflorian ( 2016-12-08 08:54:32 -0500 )edit

If one looks back, I addressed the issue of separate meta information. This behaviour was unusual in the following sense: Usually, I simply upgrade via terminal. If, during or after this process packagekit says anything different, I ignore it because refreshing it after the upgrade will always result in "software up to date". This latest incident was different because DESPITE having upgraded via dnf, refresh, delete, clean all etc. that packagekit STILL insisted that there were updates. And these updates were indeed higher versions

thingummybob gravatar imagethingummybob ( 2016-12-08 11:56:01 -0500 )edit

Therefore, simply to get the nag screen to go away, I had to enable the testing repo in order that dnf then found those same higher versions and installed them. Once done, I disabled the repo again.

As for the metadata expire, my bad. Following the docs, I used

metadata_expire=0

and not '90'. Apologies.

thingummybob gravatar imagethingummybob ( 2016-12-08 12:00:08 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2016-12-07 03:30:37 -0500

Seen: 728 times

Last updated: Dec 07 '16