Bug 1709453
| Summary: | Re-emergence of a old (unreported?) bug: Modular dependency problems | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | rh.bugzilla |
| Component: | dnf | Assignee: | Jaroslav Mracek <jmracek> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 30 | CC: | dmach, jmracek, jrohel, mblaha, mhatina, packaging-team-maint, pkratoch, rpm-software-management, vmukhame |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | dnf-4.2.8-1.fc30 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-09-06 12:31:02 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: | |||
|
Description
rh.bugzilla
2019-05-13 15:43:06 UTC
I have tried replacing my os-release with an f30 version of the https://huhuidong.wordpress.com/2018/12/19/modular-dependency-problems-conflicting-requests-fedora-29/ solution. As expected it did not help. This seems to be a related to : https://bugzilla.redhat.com/show_bug.cgi?id=1656509 I have upgraded from f29 but this error did **not** start appearing until some time after upgrade. Sadly the bug report doesn't seem to be helpful in getting out of it; even though someone has tried to close the report as fixed! Just realised that I followed the instructions that were on the https://fedoraproject.org/wiki/DNF_system_upgrade . These instructions included a reference to the modules version in the "dnf system upgrade" command and it has subsequently been removed. I used "sudo dnf system-upgrade download --refresh --releasever=30 --setopt='module_platform_id=platform:f30'" as instructed. Starting to think this is a red herring and something changed (badly) at the repo end. Seems to be down to modules and Rawhide interaction. Once I disabled the rawhide repo - from which I only enable access to one package, btrfs-tools, in the ".repo" file - the issue disappears. If this bug is feature of Rawhide - the developers test area - how do we put faith in the whole concept of modularity within Fedora stable? http://fedora.12.x6.nabble.com/Trying-a-upgrade-from-29-to-30-tp5083088p5083115.html provides the clue for me to try turning the rawhide repo off. ** CLI BEGINS ** $ cat sudo cat /etc/yum.repos.d/fedora-rawhide.repo <snip> [rawhide] name=Fedora - Rawhide - Developmental packages for the next Fedora release failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/rawhide//Everything/$basearch/os/ metalink=https://mirrors.fedoraproject.org/metalink?repo=rawhide&arch=$basearch enabled=0 metadata_expire=6h repo_gpgcheck=0 type=rpm # gpgcheck=1 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch # skip_if_unavailable=False skip_if_unavailable=True # Added from https://dnf.readthedocs.io/en/latest/conf_ref.html#conf-ref-label includepkgs=btrfs-progs <snip> Why did this problem only just reappear recently - (long) after my successful upgrade to f30? That must mean that the Rawhide repo metadata was "good" at one stage (and for a while) with f30 The behavior is a consequence of https://github.com/rpm-software-management/libdnf/commit/add998a2afabead4beaeeb91727a5389d7d5a859. I create a patch (https://github.com/rpm-software-management/dnf/pull/1446) that change application of excludes/includes. It will resilt that excluded packages will be not used for detection of Platform ID I also create a test for it - https://github.com/rpm-software-management/ci-dnf-stack/pull/580 Thank you @Jaroslav I enabled the repo (package) again. And wait for it to come through! FEDORA-2019-40235845dc has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-40235845dc dnf-4.2.8-1.fc30, dnf-plugins-core-4.0.9-1.fc30, dnf-plugins-extras-4.0.5-1.fc30, libdnf-0.35.2-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-40235845dc FEDORA-2019-40235845dc has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-40235845dc dnf-4.2.8-1.fc30, dnf-plugins-core-4.0.9-1.fc30, dnf-plugins-extras-4.0.5-1.fc30, libdnf-0.35.2-1.fc30, swid-tools-0.8.6-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-40235845dc FEDORA-2019-40235845dc has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-40235845dc dnf-4.2.8-1.fc30, dnf-plugins-core-4.0.9-1.fc30, libdnf-0.35.2-1.fc30, swid-tools-0.8.6-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-40235845dc dnf-4.2.8-1.fc30, dnf-plugins-core-4.0.9-1.fc30, libdnf-0.35.2-1.fc30, swid-tools-0.8.6-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. |