Bug 449989
Summary: | yum-versionlock doesn't work against package obsoletes? | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | James Ralston <ralston> |
Component: | yum-utils | Assignee: | James Antill <james.antill> |
Status: | CLOSED ERRATA | QA Contact: | Jan HutaĆ <jhutar> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | CC: | borgan, jhutar |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-20 22:05:56 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James Ralston
2008-06-04 16:33:32 UTC
# /etc/yum/pluginconf.d/versionlock.list # # List of pacakge versions you want to lock # # Format: NAME-VERSION-RELEASE, same as outpuf of # rpm -qa --qf '%{name}-%{version}-%{release}\n' It's mostly a limitation, the way versionlock works is that it finds all the available packages matching your "versionlocked name" and then excludes all the ones with a different version. Looking for obsoletes against the name, and then excluding those, would solve this problem. As a workaround you should be able to exclude the obsoleting package. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Ah... yum-versionlock is more like a yum-neverupdate, then. While I can --exclude the obsoleting packages if I run yum by hand, the main problem I am trying to solve is yum-updatesd's continual yammering. (There's a certain irony here: RHEL 5.2 provided a much-improved yum-updatesd (one that can actually send notifications for us now, because it no longer requires localhost to run an SMTP server on port 25), but thanks to the circular obsoletes chain, I'm about to turn it off again.) If it wouldn't be a huge performance hit, I think versionlock should also look for obsoletes against the listed packages, and exclude any packages that obsolete the listed packages. I think this behavior is more in line with user expectations... You know you can put "exclude=blah" in your yum.conf? ... yum-updatesd will respect that too. I think the latest upstream versionlock should fix this now (it has a follow_obsoletes option) ... can you try that? http://devel.linux.duke.edu/gitweb/?p=yum-utils.git;a=commit;h=b280cc1e1d5874d91c117549ec741f7fed9a1232 This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Is the latest upstream yum-versionlock packaged anywhere? The latest in Rawhide is yum-versionlock-1.1.14-4.fc10, from 2008-05-29. The diff in comment 7 looks like it needs something pretty close to upstream to apply... An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0227.html |