Bug 1804720
| Summary: | repomanage tool is not working correctly with modules in AppStream | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Roman Bobek <rbobek> |
| Component: | dnf | Assignee: | amatej |
| Status: | CLOSED ERRATA | QA Contact: | Luca Berton <lberton> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.1 | CC: | amatej, henson, james.antill, kwalker, lberton, mdomonko, packaging-team-maint, paul, pkratoch |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | 8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | dnf-plugins-core-4.0.17-2.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-04 01:52:37 UTC | Type: | Bug |
| 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: | |||
| Bug Blocks: | 1825061 | ||
|
Description
Roman Bobek
2020-02-19 14:06:34 UTC
I agree with the proposed AC and test and also with the note, modular metadata has to be present in order to work properly with modular packages (Maybe we could also include that in the AC and test scenario specification, but not sure if necessary). PR: https://github.com/rpm-software-management/dnf-plugins-core/pull/394 tests: https://github.com/rpm-software-management/ci-dnf-stack/pull/825 Removing needinfo since it was answered in Comment #2. I think the fix for this introduces a new problem. The repomanage plugin creates a new temporary repo "repomanage_repo" for the directory to be managed, and that gets cached like a regular repo. Typically, repomanage is used to prune directories of old packages, but the cache can remember packages that were there previously and were removed by a previous run of repomanage, so when repomanage is run again it outputs the names of the packages from the cache that are no longer present. I think the plugin needs to disable this caching behaviour. I see, thanks for the heads up. I will try to address the problem as part of https://bugzilla.redhat.com/show_bug.cgi?id=1890314. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (yum bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:4510 (In reply to Paul Howarth from comment #11) > I think the fix for this introduces a new problem. The repomanage plugin > creates a new temporary repo "repomanage_repo" for the directory to be > managed, and that gets cached like a regular repo. Typically, repomanage is > used to prune directories of old packages, but the cache can remember > packages that were there previously and were removed by a previous run of > repomanage, so when repomanage is run again it outputs the names of the > packages from the cache that are no longer present. > > I think the plugin needs to disable this caching behaviour. Turns out the bug I mentioned is unrelated, but I have created a fix here: https://github.com/rpm-software-management/dnf-plugins-core/pull/414 (In reply to amatej from comment #15) > (In reply to Paul Howarth from comment #11) > > I think the fix for this introduces a new problem. The repomanage plugin > > creates a new temporary repo "repomanage_repo" for the directory to be > > managed, and that gets cached like a regular repo. Typically, repomanage is > > used to prune directories of old packages, but the cache can remember > > packages that were there previously and were removed by a previous run of > > repomanage, so when repomanage is run again it outputs the names of the > > packages from the cache that are no longer present. > > > > I think the plugin needs to disable this caching behaviour. > > Turns out the bug I mentioned is unrelated, but I have created a fix here: > https://github.com/rpm-software-management/dnf-plugins-core/pull/414 Thanks. Currently, I've been working around this by using repomanage --setopt=metadata_expire=1 |