Bug 912165
| Summary: | [kernel] dnf distro-sync and the kernel package | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Heldwin <heldwin> |
| Component: | dnf | Assignee: | Ales Kozumplik <akozumpl> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | akozumpl, barthes.benoit, heldwin, ignatenko, jzeleny, marianne, mls |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-05 06:46:15 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: | 905209 | ||
| Bug Blocks: | 871892 | ||
|
Description
Heldwin
2013-02-18 01:32:49 UTC
Hello, the support for installonly packages (such as kernel) in DNF is not in a good shape yet and this bug revealed yet another issue. Thanks for reporting. *** Bug 920370 has been marked as a duplicate of this bug. *** Ales, please provide a solver testcase ;) I know I know. My plan is to fix the number-of-installed-kernels bug and then try to reproduce it in DNF. Who knows maybe it's gone now with all the libsolv fixes. Hello, can this still be reproduced with dnf-0.4.9? Several installonly fixes went in in the meantime. Hello, The problem is I am now on F20, and didn't check dnf too often. With dnf 0.4.9-1.fc20, if I try with the deactivation of updates-testing made by the package fedora-release-20-1 (and manual reactivation after that), I get in a distro-sync loop with a switch of repo fedora/updates-testing, and can test a little dnf. So far, it doesn't seem to do that for this version of dnf. can test on f19 also. > With dnf 0.4.9-1.fc20, if I try with the deactivation of updates-testing
> made by the package fedora-release-20-1 (and manual reactivation after
> that), I get in a distro-sync loop with a switch of repo
> fedora/updates-testing, and can test a little dnf.
I am not sure if I follow here: what do you mean by 'distro-sync loop'?
I mean by activating/deactivating the fedora-updates-testing repo, maybe calling it a loop isn't appropriate :) * distro-sync on the fedora repo, that do about 149 downgrades because I was on updates-testing, and deleteting the last kernel after that (I am on the previous one) * getting back to the updates-testing repo using distro-sync * doing the same with yum to compare (just doing it as a test on 1 machine, fully backuped) But it doesn't try to grab an old kernel anymore (deleting or not the last kernel) At this time, it also seems to have the exact same number of packages to downgrade/upgrade between yum and dnf (In reply to Heldwin from comment #8) > > At this time, it also seems to have the exact same number of packages to > downgrade/upgrade between yum and dnf DNF and yum use different depsolvers so sometimes DNF offers different (some would say more correct) results. That is not a bug unless shown specifically that a wrong package was distro-synced or that DNF refuses to distro-sync a certain package.(In reply to Heldwin from comment #8) > But it doesn't try to grab an old kernel anymore (deleting or not the last > kernel) I will close this bug per this comment. If DNF distro-sync doesn't work for you the way it should please reopen this bug, with debugdata/ attached. [1] http://dnf.baseurl.org/2013/11/25/reporting-depsolving-bugs/ |