boulder: Improve the workflow for updating recipes

[ermo]

Ikey Doherty I think we're going to need to bite a particular bullet here So right now it's daunting to update a stack, isn't it? Like, "I really can't be fucked" Might I suggest we plan to force me to add the relevant pieces we need for this weekend Such as bulk applying all available source updates and planning the build on a branch To make it less fucky Thatd be a great step imo ermo sure, as long as you decide for yourself to play with autobuild query src:. -F1/-R1 <pkg> prior to the work so you can see in how bad a way we are re. cycles currently Ikey Doherty Sure Tldr I hate checking release-monitoring manually Even more I hate wget&&sha256sum dance Then like a heathen copy pasting ermo sounds like we're essentially worse to use than Solus currently? Which ... ouch. Ikey Doherty If we do it properly we not only fetch, verify and check the hash, we store it in the boulder cache And update the yaml ermo that'd be awesomium I'm gonna land the small PR that does what I outlined above re. unconditionally setting manifest buildrelease to 0. (since it's ignored for now anyway) Ikey Doherty Aye OK so this and manpage are my p1 works to start back With this I also plan some basic repo audit support Missing / incomplete monitoring files etc Find unpublished builds Big boy time ermo do you need issues for it? or do you just want to keep your own list? Ikey Doherty Please Marked urgent and assigned Make me look bad. Yknow the drill. Game my brain. ND applied ermo *cracks fingers* well then