Bug 893445
Summary: | yum -C search whatever return error | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Patrik Kis <pkis> |
Component: | yum | Assignee: | James Antill <james.antill> |
Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | james.antill, jzeleny, ksrot, zpavlas |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 669746 | Environment: | |
Last Closed: | 2013-07-19 08:19:49 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: | |||
Bug Depends On: | 903631 | ||
Bug Blocks: |
Description
Patrik Kis
2013-01-09 11:00:56 UTC
The problem is that: 1) since commit 0f03409 (Tue Dec 13 15:43:30 2011) users always have their own cachedir (even when -C is in use) 2) The -C option instructs Yum NOT to attempt any modification of the cachedir. As a result, preloading from root to user cachedir does not work when user runs "yum -C .." I wrote a patch to fix (some cases of) this, but it's not upstream. It's also questionable whether it's a bug or not. See this thread: http://lists.baseurl.org/pipermail/yum-devel/2012-June/009298.html Yeh, not much has changed since that thread. In theory we can change .cache = 1 to mean "no network activity" and declare all past API usage of cachedir=<system>, cache=1 as broken/bad ... but we should really have done that sooner. From what I can see all current yum-utils scripts "behave" and wouldn't trigger this problem. Maybe putting the access() check from the thread: http://lists.baseurl.org/pipermail/yum-devel/2013-June/010175.html ...into a property (cached) and using that to say "can't modify" instead of cache=1 would be quick and have no downsides (push it and se^W run ;). Reviewed the dependency on #903631 and assessed it to be a duplicate. *** This bug has been marked as a duplicate of bug 903631 *** |