Yum reports that there are 121 updates needed but apper reports that the system is up to date. Why?
Thanks - jon
On Sun, 15 Mar 2015 13:01:56 -0700 Jonathan Ryshpan jonrysh@pacbell.net wrote:
Yum reports that there are 121 updates needed but apper reports that the system is up to date. Why?
Thanks - jon
They use different cache, also they can get data from different mirrors. So that is probably OK, if you wait some time apper should pick up new data and show updates available.
Cache is valid for some time period, and as I understand it, it doesn't try to get new data until that period expires (probably few hours ... or more), so if you ask apper to check for updates it will probably report the same until cache expires and then start downloading new.
On 03/16/15 04:01, Jonathan Ryshpan wrote:
Yum reports that there are 121 updates needed but apper reports that the system is up to date. Why?
Thanks - jon
See....
https://bugzilla.redhat.com/show_bug.cgi?id=1152079
https://bugzilla.redhat.com/show_bug.cgi?id=1189602
Ed
On 03/16/15 04:01, Jonathan Ryshpan wrote:
Yum reports that there are 121 updates needed but apper reports that
the system is up to date. Why?
On Mon, 2015-03-16 at 05:39 +0800, Ed Greshko wrote:
See....
It looks from bug 1189602 that apper and some other similar apps are completely broken. If so, this should be a top priority for getting fixed. In the meanwhile users should run yum frequently either via yumex or from the console.
On 03/15/2015 06:09 PM, Jonathan Ryshpan wrote:
On 03/16/15 04:01, Jonathan Ryshpan wrote:
Yum reports that there are 121 updates needed but apper reports that
the system is up to date. Why?
On Mon, 2015-03-16 at 05:39 +0800, Ed Greshko wrote:
See....
It looks from bug 1189602 that apper and some other similar apps are completely broken. If so, this should be a top priority for getting fixed. In the meanwhile users should run yum frequently either via yumex or from the console.
This is my own but:
https://bugzilla.redhat.com/show_bug.cgi?id=1188207
Here is where we are:
The trouble lies with PackageKit, the CLI command behind Apper. The command "pkcon" is assuming an indefinite cache age. In short it is not even checking its cache.
I have been working around this by executing:
# pkcon refresh force
every morning at startup. (Of course, $sudo pkcon refresh force is the new way to execute admin-level commands.)
Rumors began to fly that maybe the problem got fixed somewhere along the way, by accident. This is not true. This morning I waited twenty-four hours since the last refresh and didn't get an update notice. I ran the force-refresh command, and got a notice of the push of the latest version of the kernel.
Once I run that command, I get notices of updates available. I then excuse this by GUI methods, as I always did.
They're working on it, all right. They know now the PackageKit system is assuming an indefinite or infinite cache age by default. They're trying to get that default changed to 86400 second (which is to say, twenty-four hours). I don't know what's holding things up. As many of you as think you have any special pull, can go to that bug, add yourselves to the CC list, and put in your tuppence, deux centimes, zwei pfennigen, whatever.
Temlakos
-
Branko Grubic -
Ed Greshko -
Jonathan Ryshpan -
Temlakos