like, if I could go back in time and give this to myself as my first linux ... the amount of sheer t
like, if I could go back in time and give this to myself as my first linux ... the amount of sheer toil and suffering I could save lol
Рif base is being archived I feel like main should be unsquashed, as in
Рyeah it's amazing, I can't wait to get my friends onto linux this way
C
Jwhat even is dpkg-reconfigure -a
Di'm pretty sure Linux is mainstream rn if distro like Silverblue exist 20 years ago
Jyou mean like ChromeOS is? 
Jok testing the build chain on the new repo, everything is working as expected so far
Jwhich means the template we started on is self-sustaining fork-wise.
Jso that problem is solved other than people who need to figure out cosign when they fork
Jreview from someone please!
J
JDoesn't look like it's triggering a build though
Jyeah
JInvestigating
Jwhy are we removing the service units?
Jsettings look fine
Joh
Jlabel
JTHERE WE GO
JI removed whatever didn't come installed as an RPM
Jok so how are we going to do those?
JWe could do a few things, either A) have them exist in a separate repo like udev-rules, B) rename udev-rules into a generic RPM extras repo and have that be where we generate RPMs and directories for COPY invocations C) still have them as part of the main repo and add a .spec file which generates the RPM on the fly just like with the nvidia drivers
Jmarco told me about rpm building actions and I found a good amount of them, maybe a GH-hosted rpm repo is the best long term play
Jthen we can use it for stuff like this
JI think it's generally a good habit to have whatever addons we have be something that can be stored in the rpmdb. It becomes easy to track file lists and easy to add/remove with rpm-ostree, plus if there's ever an error due to a file conflict rpm-ostree will let us know
Jsure I get it
Jplus, if anyone is going to use this at work it has to have that
JI try to keep my most blatant cowboy stuff in my own image
Jwhen you think about it udev-rules is really like a bucket for config
Jublue-os/config might be an idea ...
Mthis isn't going to work
Mwe never fixed the matrix'd pr workflow
Mit's why we turned off 38 in the base
Mso the PR images won't actually publish (wont' affect builds on main though)
Jdoes that I mean I can cowboy?
Jstill require a review for now but let's keep going?
Myeah
Jno one's using it yet, we can call this day 0
Myes
Mto save time we should temporaily disable builds for PRs? or at elast the whole artifact publishing workflow
Jyour devops attitude, makes me all warn inside
Jyeah how we do that? we could have jstone just do it in this pr since he's editing the file anyway
Mif he wants to - cool, if not I can open a quick PR
JWhat's it doing differently from the nvidia PR process?
Ma lot - we worked around PR builds from works not working
Jalso is there a way to do a sudo like thing for mods so that our names aren't all red and in your face all the time? (for discord)
Jthat was amazing!
J@marcoceppi if you're going to PR it you can remove the label requirement unless you have other plans for that?
Myes
