It's enabled by default. The primary issue is it fails to start due to gdm group not being present
It's enabled by default. The primary issue is it fails to start due to gdm group not being present for some reason
IStrange. Do you have your changes pushed to your branch?
RAll changes are in the
mainHave you tried the "Fedora Workstation" group instead of gnome-desktop?
II encountered problems with NetworkManager until I installed the Workstation group
JIf I don't have to make bluefin:lts because heliumOS already exists then that would be fine with me too lol
Jlike if you want to stake the claim for an end user consumable EL atomic images I don't think you'll have much competition, heh.
Jbut if you want to bring EL expertise to the team and do it all together, also always open to doing everything as a group heh.
II will continue improving HeliumOS, but I would like to collaborate more with you and the rest of ublue.
Jalways down for that! Has anyone from centos been checking out your stuff? I'd like to get this on shaun mccance's radar if you don't mind
IJoseph Gayoso brought it up in a CentOS Stream Matrix channel, so Shaun is aware
Jah ok, perfect.
II've been most active in https://matrix.to/#/#bootc:fedoraproject.org, which some here may want to join
You're invited to talk on Matrix. If you don't already have a client this link will help you pick one, and join the conversation. If you already have one, this link will help you join the conversation
JJGitHub
This PR contains the following changes:
Add pytest-based unit tests
Add Github Actions CI for unit tests
I can squash before merging :)
Closes #72
Add pytest-based unit tests
Add Github Actions CI for unit tests
I can squash before merging :)
Closes #72
JNICE!
J@imbev a longer support desktop from the Fedora world would be crazy to see. Would be interested to see what the balance looks like between new packages and the stability from staying on something old.
JShame that it didn't stay on CentOS Stream because it would have been awesome for those guys to have a downstream example that they would like to play with, but Alma's great too. And Alma is a downstream as well.
JOn the topic of bootc, I reached out this week to help them start figuring our how they want to market and position bootc and the bootc images. We'll see where they land but it's exciting. Lots of openness to the idea of bootc being an invitation for the community to build something with it.
ICentOS Stream and AlmaLinux are similar enough that I think it will be useful
Ibootc is much more approachable for downstream projects 
Jwhich i love so much
JWhat I would like to see is Fedora pick up more of the cloud native methodology that uBlue has if they don't already. But I know @Noel is looking at how that can work.
JMaybe it would be valuable to point folks from the atomic downstream community into the Fedora Atomic Desktops SIG specifically. Besides getting bootc over the line, I imagine that SIG is the next thing that is the most consequential for all of the atomic desktop downstreams. And I think Timothee would be grateful for the help.
GI'll take a look!
GI also am figuring we could use some integration testing as well, like loading up a
ublue-os/mainublue-update@Kyle Gospo does merging a change in ublue-os/packages auto kick off a COPR or do I need to press the button?
JI hit refresh a few times in the copr view so I'm assuming I have to hit the button
Kneed to press button
Jdone, neat.
Jmaybe someday
Gthe COPR build action uses this IIRC
Joh
Gjust needs to be resurrected
GAPI keys also need rotation
Jyeah was just thinking, it'd be neat to just have everything everyone uses in the packages repo and set to rebuild on merge, then we just dependabot all day instead of bothering kyle
Gyeah it'd be cool. I can take a look later at the action
Git was supposed to be able to automatically create a COPR, but I'm sure it's not hard to repurpose it to just trigger builds
GGitHub
GitHub Action to create copr repositories. Contribute to akdev1l/copr-build development by creating an account on GitHub.
GThis package automates that process so that the repository can add itself to a COPR project. It also allows you to trigger builds for the created package such that you can trigger builds from Github Actions instead of relying on SCM monitoring from COPR.
AI'll probably be helping with this lol
Jyou're welcome I threw a comment in the PR as i'm not sure about the original acceptance criteria
I threw a comment in the PR as i'm not sure about the original acceptance criteriaJcan you assign me the linked issue?
Jlooks like I can't
Jim guessing its cause im not in the org? idk what yalls procedure is for that, but my plan is to start contributing
JJthough you can just start sending PRs
Jbut generally speaking we run pretty flat and async, feel free to drop a review or PR where you find things, there's always lots to do, heh
Jim on it, boss
