Jthis failure confuses me
Tits trying to build a non-existent spec
Tso it fails quietly
Tthen it fails cuz the build didnt run
Tits super dumb
Till add a check to make sure the specs that it tries to find actually exist so we dont get this weird error
Jok so can we just merge this or is it a systemic problem?
Junderstood
Tnothing wrong with your PR
Tcan be merged just fine
JJone more
Tlooks like it just needs a rebase
JTseems to be a small update, we might want to check out the commit changes between those
T@Kyle Gospo ?
Tany idea if this one blows up bazzite?
Jhttps://github.com/ublue-os/packages/pull/232 ugh man I thought we handled this last month
J
Toh man that also reminded me, all the bazzite spec files dont have the fancy renovate stuff
J@M2 can I get a final eyeball on this one? ^
MYeah that one is fine
Jwhat's the tldr on the key management on this?
Jdid we do the due diligence in 1password?
Mnew public key is in repo
Jor did we jorge it? 
Mbackup key is only stored in 1password and is not loaded into github secrets
Jok I'll put that in the issue and merge
Jta
MI believe we did that already as well
Mwe held off on merging because.... we wanted to make sure it works. But I guess we all just left comments
Mbut p5, ledif, and I are all doing this in our images
Joh you think we'll get a ton?
Tabsolutely, we just need to wire renovate up
Jthough we should fix that one red thing so when we get slammed we can at least merge stuff lol
Till just fix the gh actions issues n stuff
T@M2 https://github.com/ublue-os/packages/pull/309 EPEL build seems to fail cuz of some missing deps but this looks great
J7 PRs done. Nice.
Tmore to come!
Tsoon
JLET'S GOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
I
KShould be fine
Jthe red tho
T
Thuh no idea why this is failing
Jhttps://github.com/ublue-os/packages/pull/242 any idea why these are doubling up? are we rewriting things so it's doing other hashes? never seen that before
Tits counting merge commits as the same commit
Jok maybe it's a config, I can dig this up