If we're going to use packages repo... we need to actually keep it up to date
If we're going to use packages repo... we need to actually keep it up to date
RCan we add all approvers as reviewers? I don't get notified about any of these
Jyeah it's our biggest pain point right now, agreed.
Jthe devpod flatpak is almost done
J@Robert this sbom run on lts took like 3 minutes?
Jthat was way slower before
RGDX took 7 minutes... Think this was the main one causing problems
Jah right!
Jwell, other than that this is smoooooooth.
RBut if by "before", you're referring to 6 months ago, when we first tried SBOMs, then yes! It was 30ish minutes
Jheheh
JI think once we have a semi permanent ampere box to ssh to that we should be fine
MRight now attestation is the next challenge. I'm wondering if there is a limit to the sbom size for attaching?
MMy smaller images are working fine. But the larger ones the push to the registry is failing
JCan we start an sbom/attestatoin thread? I got a few nibble at kubecon for people looking to help
RJok so instead of using the github board when I get back I'm going to just write the update in hackmd and we'll put all of those items in there so we can double up
Jthen that will be our transparecy report for the cycle
JJcan I get a review?
J
Tits that damn safe-to-run tag
Tlets just remove that 
Till revert the thing and pr it
Tcuz this is causing more trouble than not
JToh nope
Tthat one was cuz you didnt bump the spec
Jhttps://github.com/ublue-os/packages/pull/300 this one is dangling too
Tso the action didnt know how t obuild it
JI didn't know I had to bump the spec
Tneed to fix the conflict here
Till actually do that right now, lemme just revert the thing
Tno worries its counter intuitive
Tgotta find some automated way of doing it
TTthere ya go
Tall the renovate ones should be fine i think
Tlets see
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
J