I'm sorry to admit that I've been running my personal build up until now. I'd like to switch over to using modules, but have I hit a problem in the packaging?
$ sudo dnf module install sway/full Last metadata expiration check: 0:00:10 ago on Wed 03 Jul 2019 09:47:06 PM EDT. Unable to resolve argument sway/full No match for package sway Unable to resolve argument sway/full No match for package swaybg Unable to resolve argument sway/full No match for package swayidle Unable to resolve argument sway/full No match for package swaylock Error: Problems in request: broken groups or modules: sway/full, sway/full, sway/full, sway/full
I've purged my locally built RPMs, so I'm at a loss as to what could be the issue. I've looked at the sway.yaml file in the modules repo and it looks fine, though I have never done anything with modularity before.
If I add on --skip-broken, mako and rofi will install.
It's very possible I've gotten my system in a weird/bad state, but I'd really expect dnf module reset sway to get things back into working order.
On Wed, Jul 3, 2019 at 10:03 PM Jeff Peeler jpeeler@redhat.com wrote:
I'm sorry to admit that I've been running my personal build up until now. I'd like to switch over to using modules, but have I hit a problem in the packaging?
Replying to myself (this time in plain text), I figured out the issue and the problem was on my end. I had forgotten that I put an exclude line in dnf.conf to ignore wlroots and sway... Turning on debugging showed me the issue: dnf -d=10 module install sway/full.