Red Hat Bugzilla – Bug 212494
puplet doesn't honor excluded packages in yum.conf
Last modified: 2007-11-30 17:11:46 EST
Description of problem:
If there are packages excluded from updates in yum.conf, puplet doesn't honor
them in reporting how many updates are available in the notification bubble
Version-Release number of selected component (if applicable):
Set up an exclude list of packages that are set to be updated, and notice the
the reported number of updates before and after is the same
Steps to Reproduce:
1. Wait for an update notification to appear (note number)
2. Edit yum.conf to include a line like "exclude=*" (or just one package)
3. Tell puplet to refresh (right click on the icon -> refresh)
4. Note number is not different
Available packages doesn't change.
The user has explicitly asked to exclude those packages, so they shouldn't show
up in the count of updates.
Pup itelf honors the setting just fine.
*** Bug 212553 has been marked as a duplicate of this bug. ***
Did you restart yum-updatesd? The config is only read when the daemon starts.
It's been ignoring my exclude line (with Freshrpms) after many reboots, so
that's not the problem. I haven't checked whether it ignores excludes for all
repositories or just the non-default ones.
I should have mentioned that my exclude line is not in yum.conf, but in
It seems it ignores excludes for all repos. My config entry looks as follows:
and puplet keeps telling me there are 2 updates available even though I have
updated all non-excluded packages.
Okay, I think I've got this pretty happy now. Can you grab
http://people.redhat.com/~katzj/yum-updatesd.py and replace
/usr/share/yum-cli/yumupd.py, restart yum-updatesd and see if it works better?
Well, you mean to replace yumupd.py with yum-updatesd.py?
Not being familiar with python, or with the roles of the 3 files yumupd.py,
yumupd.pyc, and yumupd.pyo, I just did exactly what you said, replacing
yumupd.py with yum-updatesd.py (assuming that the fact that the name is
different is okay), ignoring the other two files. No change.
Well, I replaced the file and now the puplet icon does not appear anymore. It
sometimes takes a while, though. Maybe I am just not patient enough.
Fixes it for me.
Andre -- did you do "service yum-updatesd restart" ?
Julian -- try running "dbus-send --system --print-reply --type=method_call
--dest=edu.duke.linux.yum /Updatesd edu.duke.linux.yum.CheckNow"
I did restart yum-updatesd. But I'm not clear on exactly what I was supposed
to do. I renamed the existing yumupd.py to yumupd.py.tmp, and then copied the
file yum-updatesd.py into the same directory (_without_ changing the name to
yumupd.py) - is this correct?
(In reply to comment #11)
> I did restart yum-updatesd. But I'm not clear on exactly what I was supposed
> to do. I renamed the existing yumupd.py to yumupd.py.tmp, and then copied the
> file yum-updatesd.py into the same directory (_without_ changing the name to
> yumupd.py) - is this correct?
No, you should've done "mv yum-updatesd.py /usr/share/yum-cli/yumupd.py"
Okay, now the puplet icon doesn't appear anymore, so it seems fixed for me as
Works great here as well. Thanks for the fix.
It seems to be fixed because pup returns the same number of updates as puplet.
THe other question is: is the icon supposed to be visible when there are no
updates? It was visible for me and after I ran pup, updated the system and hit
refresh it disappeared. I alco ran the command Nicholas suggested:
[jsikorski@fcdesktop ~]$ dbus-send --system --print-reply --type=method_call
--dest=edu.duke.linux.yum /Updatesd edu.duke.linux.yum.CheckNow
method return sender=:1.1 -> dest=:1.12
string "check queued"
Is this the expected behaviour?
yum-3.0.1-2.fc6 has been pushed for fc6, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.