Description of problem: The following has been done with yum: $ rpm -qa --qf="%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" |grep snmp net-snmp-utils-5.4.1-7.fc8.x86_64 net-snmp-libs-5.4.1-6.fc8.x86_64 net-snmp-5.4.1-6.fc8.x86_64 Expected results: same versions.
I can't reproduce it with yum. It always updates all net-snmp-* packages, unless I tell it to update net-snmp-utils package only - and then I get what I want, updated net-snmp-utils and nothing else. I do not see anything wrong here. Do you use any unusual setup, like 3rd party repos, which provide net-snmp packages? Or how did you manage to install/update net-snmp-utils-5.4.1-7?
no, if I just try to update net-snmp-libs, I'd expect it to update everything that depends/links against it - and vice versa. why would you like to get mixed versions configuration as there are no qurantees that it would work?
(In reply to comment #2) > why would you like to get mixed versions configuration as there are no > qurantees that it would work? It's guaranteed by library soname. If an update of net-snmp-libs would break dynamic linking, I am quite sure the updated libraries would have different soname and all dependencies would get updated by yum. But if the ABI does not change, there is no need to update everything, if you explicitly ask to update just one package. You just get what you ask for - one package updated. Using your argumentation, if e.g. glibc gets updated, would you expect to update whole system to last version? You should use "yum update", without additional arguments, to update everything.
yep, that makes sense.
I reconsidered the bug - in some cases (e.g. security updates) it would be better to update all net-snmp subpackages, not only the one explicitly required. There can be changes which are not reflected by soname bump.
net-snmp-5.4.1-8.fc8 has been submitted as an update for Fedora 8. http://admin.fedoraproject.org/updates/net-snmp-5.4.1-8.fc8
net-snmp-5.4.1-8.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.