Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installonly packages are not handled correctly when more architectures #1283

Open
j-mracek opened this issue Feb 28, 2024 · 0 comments
Open
Labels
Priority: MEDIUM Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take

Comments

@j-mracek
Copy link
Contributor

j-mracek commented Feb 28, 2024

Installing of secondary architecture for kernel-core result in problem. The issue was discovered during review of #1261.

Reproducer on vanilla system (one kernel-core.x86_64 installed and upgrade available):
Install kernel-core.i686 (requires to add i386 fedora repository)

# dnf --repofrompath=test,https://sdsd.com --setopt=test.metalink='https://mirrors.fedoraproject.org/metalink?repo=updates-30&arch=i386' install kernel-core-0:5.0.9-301.fc30.i686 --nogpgcheck --setopt=installonly_limit=2

upgrade kernel-core (requires to add i386 upgrade repository)

# dnf --repofrompath=test,https://sdsd.com --setopt=test.metalink='https://mirrors.fedoraproject.org/metalink?repo=updates-released-f30&arch=i386' --nogpgcheck --setopt=installonly_limit=2 upgrade kernel-core

Result:

Error: 
 Problem: The operation would result in removing the following protected packages: kernel-core
(try to add '--skip-broken' to skip uninstallable packages)

Expected:
Both kernel-core packages will be upgraded

The issue is caused by a different logic in libsolv where packages are handled per architecture (correct behavior) and our logic that handles over limit packages where it handle them per name.

Solution sort same_name_subqueue and related queue by name and architecture.

Issue for DNF - rpm-software-management/dnf#2058

@ppisar ppisar added Priority: MEDIUM Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take labels Feb 28, 2024
@ppisar ppisar added this to DNF team Feb 28, 2024
@github-project-automation github-project-automation bot moved this to Backlog in DNF team Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: MEDIUM Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take
Projects
Status: Backlog
Development

No branches or pull requests

2 participants