I'm override removing waybar and rpm-ostree is replacing it without me asking for it to
I'm override removing waybar and rpm-ostree is replacing it without me asking for it to
GSo there's no dependency on waybar itself, just that the sway spin uses it
TThen idk why I can't remove it before removing sway
GYou can just install sway on top of main/base
GThat's what I did
TI don't want sway but I don't want to replicate the utils sericea has myself
TWhat's weird is that waybar-hyprland should be marked as providing waybar
TSo idk why the original replace command I was doing was failing
TThe solver should just know it can do that replacement
TWell it's fixed now anyway
TWell the image builds at least
GYou should install Hyprland on top of base
TInstalling onto my machine results in
error: importing RPMs: creating importer: Processing file-overrides for package waybar-hyprland: Invalid absolute filepath 'waybar-hyprland-0.9.20.tar.gz'GUsing sericea as a base isn't a great plan
TProbably from the override command I ran locally earlier
GYou want an override replace.
TYes that's what I did
TOverride replace succeeded locally but didn't actually replace the package, likely for same reasons as the build failing before
Tsway-config-fedora requires waybar
Tthat was the issue
TI'll look at building from a clean base but I'll probably end up copying the majority of sericea's package list
GI use sway and I use different utils from sericea
GIn fact you can do everything with one program if you wanted to
KAll of the sources for these packages are available as well
KSo if starting from scratch is too hard you could simply build a modified version of that package locally or on copr
KAnd do a replace for that as well
TWell I have it fixed, i just had to do the swap later
TNow to figure out why discord ui has regressed to an unusable state on wayland
TI had it working before but now i can barely see what i'm typing
JEverything you need to know about securing the software supply chain.
JDOPE!
THell yeah! That should make some actions run a bunch faster (plus the security benefits of using wolfi!!!)
JGitHub
Improves upon the existing flatpak update service unit.
closes #14
closes #14
BThe implementation is fine. But I asked for community vote above, though I think it got lost in chatter.
BI'm indifferent about it. I was just trying to be helping with that issue for investigating
Jalright let's leave it open for a while then, no rush
W@MOD I didn't know who else to ping on this one. But could I get an answer on how to contribute back on some more key repos? I read through the documentation and they don't appear to talk about PRs and the like.
J
Wwow, I'm blind. My bad.
Kthen do as you said
Jor if you have a specific thing you wanna fix Just Do It(tm)
Jthe busted markdown in the "I Want To Contribute" section wouldn't be a bad start lol, I think it just needs to be indented more
Jyou could also make a good impact by PRing things you see in here into the docs since people don't do that
WI can definitely poke some holes in missing documentation during some downtime. The thing I wanted to fix is, quite frankly, a config thing in the yatfi.
Wits installing a now deprecated flatpak (optionally) was just gonna update it
WI'll fork again, and make a PR!
Jyeah fixing yafti helps everyone, always appreciated!
Wok, I thinnkkk I did this right, I'll be honest, I've never done a PR on github, its always been bitbucket, azure devops, some other git platform. And its also never been from a fork, always just a branch. So this is a first.
KOn GitHub you fork and then branch to have the same outcome
