I'm running into weird behavior where some packages are not available for install during the dnf module of blue-build, but are part of fedora's repos and are installable via rpm-ostree. An example of such a package is

polkit-qt6-1-devel

(a dependency of a copr package I maintain). When I try and install it directly, I get

l/crafti-hyprland-rpm-prerelease-track:latest_linux_amd64 => No match for argument: polkit-qt6-1-devel

and when I try to add a package that depends on it, I get

[16:14:36 g.i/c/crafti-hyprland-rpm-prerelease-track:latest] => 11.87  Problem 2: conflicting requests
[16:14:36 g.i/c/crafti-hyprland-rpm-prerelease-track:latest] => 11.87   - nothing provides libpolkit-qt6-agent-1.so.1()(64bit) needed by hyprpolkitagent-0.1.3-5.fc44.x86_64 from copr:copr.fedorainfracloud.org:craftidore:hyprland-prerelease-track
[16:14:36 g.i/c/crafti-hyprland-rpm-prerelease-track:latest] => 11.87   - nothing provides libpolkit-qt6-core-1.so.1()(64bit) needed by hyprpolkitagent-0.1.3-5.fc44.x86_64 from copr:copr.fedorainfracloud.org:craftidore:hyprland-prerelease-track

Adding

allow-erasing

does not solve the error, it seems the package genuinely doesn't exist as far as bluebuild is concerned. But as stated before, I can install it with rpm-ostree just fine. - [x] I have searched this forum for answers to this question - [x] I have read the docs on the dnf module, in case it was answered there

message has been deleted

Base image I've been testing with is

quay.io/fedora-ostree-desktops/base-atomic

the dnf module calls dnf5 under the hood

That did not reproduce the behavior, and when I had a minimal dnf module entry, that worked as well, the issue only occured when I added to my existing list of packages. I've narrowed things down a bit, and this may be working-as-intended behavior, but if you specify:

yaml
type: dnf
install:
  packages:
    - repo: copr:copr.fedorainfracloud.org:customer-user:custom-repo
      packages:
        - somepackage

and that package depends on packages from the normal fedora repos, that package won't be found and the install will fail.

oh yeah it sets the repo in the install command in that case, i think

I was specifying the copr because it had name collisions with another copr. But in this particular case I could also disable the other copr, so that's what I've done.

message has been deleted