Universal Blue•12mo ago•

33 replies

Centralizing COPRs

j0rgeOP•1/18/25, 5:20 PM

Hey @ssweeny - was looking at your s76 PR

j0rgeOP•1/18/25, 5:20 PM

what do you think about centralizing your COPR builds in like ublue-os/packages or something?

j0rgeOP•1/18/25, 5:21 PM

Was thinking that we need to get our third party repos under control. We could just have you building out of our repo with the right perms, etc.

bsherman•1/18/25, 5:25 PM

A bit of context from my perspective... we haven't made a big deal about it, but generally, we've been trying to keep all the COPR stuff centralized.

More specifically, if we have COPR built packages, we want them "at least" coming from "trusted" COPR repos, but preferably from ones which multiple ublue team members can manage.

bsherman•1/18/25, 5:26 PM

I think we are mostly there now...except for @Kyle Gospo's repos, but I believe there's a plan to get those pulled in. He's obviously "trusted" but we want better team support.

j0rgeOP•1/18/25, 5:27 PM

Also do we know?

j0rgeOP•1/18/25, 5:27 PM

I bet there's some we don't know

j0rgeOP•1/18/25, 5:28 PM

https://github.com/search?q=org:ublue-os%20copr&type=code

bsherman•1/18/25, 5:28 PM

I think @ssweeny 's S76 repos are similar.

But I'm not sure we yet have a good model for this exact situation.

The SPEC files are in a clean github repo and respective COPR...

Maybe we move the system76-io-akmodsystem76-io-akmod repo from ssweeny to ublue-os, but give @ssweeny write access to it?

And create a dedicated system76 COPR under ublue-os so @ssweeny can assist with that too.

j0rgeOP•1/18/25, 5:29 PM

is it having one copr per thing?

j0rgeOP•1/18/25, 5:29 PM

aka managing multiple coprs?

j0rgeOP•1/18/25, 5:29 PM

I suppose we can't just do one with everything can we?

bsherman•1/18/25, 5:30 PM

we can do one package per COPR repo, or we could have the system76 packages in an existing COPR repo and ssweeny probably wouldn't be able to "push build"

tulip•1/18/25, 5:32 PM

hello everyone!

Jj0rge I suppose we can't just do one with everything can we?

tulip•1/18/25, 5:33 PM

i believe we can, but the way we handle packages on bluefin/aurora makes it so any package that is on the coprs will be prioritized over the fedora-repos' ones

tulip•1/18/25, 5:34 PM

i think we should do something like we do on achillobator, explicitly disabling and enabling only when ur actually meaning to use the copr

j0rgeOP•1/18/25, 5:34 PM

oh yeah for sure

Jj0rge https://github.com/search?q=org:ublue-os%20copr&type=code

bsherman•1/18/25, 5:34 PM

anything in bluefin/aurora/bazzite is on those "products"

for the moment, i'm mostly discussing things which impact all

eg, akmods and main

j0rgeOP•1/18/25, 5:34 PM

gotcha

bsherman•1/18/25, 5:35 PM

let's scope this thread... i'm just trying to discuss getting the system76 akmod PR merged and consolidating akmods/main COPRs for now

ssweeny•1/18/25, 6:21 PM

@j0rge I'm happy to host them wherever the project wants

j0rgeOP•1/18/25, 6:22 PM

\o/

ssweeny•1/18/25, 6:22 PM

I just made my own COPR for convenience

j0rgeOP•1/18/25, 6:22 PM

ok welcome to the team blah blah lol

ssweeny•1/18/25, 6:22 PM

https://tenor.com/view/this-means-so-much-annie-murphy-alexis-alexis-rose-schitts-creek-gif-20805205

Tenor

j0rgeOP•1/18/25, 6:23 PM

ok so follow up when this lines up we can just one line enable in the downstream images right?

bsherman•1/18/25, 6:25 PM

my proposal in PR comment here: https://github.com/ublue-os/akmods/pull/290#issuecomment-2599817435

j0rgeOP•1/18/25, 6:26 PM

we get the rpm into bluefinrorazitte and then boom, easy announce

ssweeny•1/18/25, 6:29 PM

I need permission to create repos in ublue-osublue-os to transfer mine over

ssweeny•1/18/25, 6:30 PM

I promise not to go mad with power

j0rgeOP•1/18/25, 6:32 PM

one sec

j0rgeOP•1/18/25, 6:33 PM

actually can we do it the other way? we're out of org licenses

j0rgeOP•1/18/25, 6:34 PM

oh nm I think I can do this

j0rgeOP•1/18/25, 6:35 PM

ok invite sent

Centralizing COPRs

Similar Threads