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

Mock seems broken on c9s #1475

Closed
praiskup opened this issue Sep 28, 2024 · 0 comments · Fixed by #1476
Closed

Mock seems broken on c9s #1475

praiskup opened this issue Sep 28, 2024 · 0 comments · Fixed by #1476
Assignees

Comments

@praiskup
Copy link
Member

Per report in:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-acc9bfc977

INFO: Using 'dnf4' instead of 'dnf'
WARNING! WARNING! WARNING!
You are building package for distribution which uses DNF. However your system
does not support DNF. You can continue with DNF4, which will likely succeed,
but the installed chroot may look a little different.
  1. Please consider --bootstrap-chroot option, or
  2. install DNF on your host system.
@github-project-automation github-project-automation bot moved this to Needs triage in CPT Kanban Sep 28, 2024
praiskup added a commit to praiskup/mock that referenced this issue Sep 28, 2024
When package_manager = dnf, 'dnf4' is to be selected and used when
bootstrap chroot is disabled.

Fixes: rpm-software-management#1475
praiskup added a commit to praiskup/mock that referenced this issue Sep 28, 2024
When package_manager = dnf, 'dnf4' is to be selected and used when
bootstrap chroot is disabled.

Fixes: rpm-software-management#1475
praiskup added a commit to praiskup/mock that referenced this issue Sep 28, 2024
When package_manager = dnf, 'dnf4' is to be selected and used when
bootstrap chroot is disabled.

This was not detected by test-suite; my bet is that we do tests with
testConfig=fedora-40-x86_64 which is already dnf5 and we have dnf5
installed on the testing machines.  I'm trying to modify one test-case
to test DNF4 chroot explicitly.

Fixes: rpm-software-management#1475
@praiskup praiskup self-assigned this Sep 28, 2024
praiskup added a commit to praiskup/mock that referenced this issue Sep 30, 2024
When package_manager = dnf, 'dnf4' is to be selected and used when
bootstrap chroot is disabled.

This was not detected by test-suite; my bet is that we do tests with
testConfig=fedora-40-x86_64 which is already dnf5 and we have dnf5
installed on the testing machines.  I'm trying to modify one test-case
to test DNF4 chroot explicitly.

Fixes: rpm-software-management#1475
praiskup added a commit to praiskup/mock that referenced this issue Sep 30, 2024
When package_manager = dnf, 'dnf4' is to be selected and used when
bootstrap chroot is disabled.

This was not detected by test-suite; my bet is that we do tests with
testConfig=fedora-40-x86_64 which is already dnf5 and we have dnf5
installed on the testing machines.  I'm trying to modify one test-case
to test DNF4 chroot explicitly.

Fixes: rpm-software-management#1475
xsuchy pushed a commit that referenced this issue Sep 30, 2024
When package_manager = dnf, 'dnf4' is to be selected and used when
bootstrap chroot is disabled.

This was not detected by test-suite; my bet is that we do tests with
testConfig=fedora-40-x86_64 which is already dnf5 and we have dnf5
installed on the testing machines.  I'm trying to modify one test-case
to test DNF4 chroot explicitly.

Fixes: #1475
@nikromen nikromen moved this from In Progress to Done in CPT Kanban Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant