Wez does build rpms for each release hosted on GitHub, so I could just cheat by layering it. But sin

Wez does build rpms for each release hosted on GitHub, so I could just cheat by layering it. But since I am considering a build for work focused use with some other things, it wouldn't hurt to include Wezterm

ragectlOP•5/14/23, 2:56 PM

I asked about the packages on Matrix and a few minutes later he'd replaced Fedora35 with Fedora38

Rragectl Wez does build rpms for each release hosted on GitHub, so I could just cheat by ...

Arcitec•5/14/23, 2:59 PM

If you're interested, GitHub (Microsoft) will build your OS images daily according to your specification and host it for free on the same container registry that uBlue uses. It involves forking https://github.com/ublue-os/startingpoint on GitHub, ~~then set https://github.com/Arcitec/os/tree/firstboot-refactor as an extra remote and pull all of its changes (they'll be in the main repo later but for now you gotta do it manually).~~ Edit: Those changes are merged so you only need the main repo now.

After you have that, I suggest creating a new branch called something unique, like rage-osrage-os, set that as your main branch in GitHub's repo settings.

Now just start editing recipe.ymlrecipe.yml to list the packages you want to include/exclude, and editing yafti.ymlyafti.yml to configure your own "on-login package installer".

ragectlOP•5/14/23, 3:00 PM

Oh, one thing I haven't tested on my uBlue install on my laptop earlier was the YubiKeys and U2F working for things like GDM and sudo. Does anyone use that?

Arcitec•5/14/23, 3:00 PM

The reason for branching is so that you can easily fast-forward mainmain to upstream anytime, and then rebase your own rage-osrage-os branch onto main peridically to get improvements.

ragectlOP•5/14/23, 3:00 PM

I think I saw some rules added to support it, but I haven't tested

Rragectl Oh, one thing I haven't tested on my uBlue install on my laptop earlier was the ...

Arcitec•5/14/23, 3:01 PM

Yeah there's device rules installed for that but I don't use it personally

Rragectl Wez does build rpms for each release hosted on GitHub, so I could just cheat by ...

j0rge•5/14/23, 3:01 PM

you can also just add it as your day to day terminal but leave the stock terminal there

j0rge•5/14/23, 3:01 PM

I use gnome-terminal as my host

j0rge•5/14/23, 3:01 PM

and then blackbox flatpak for distroboxes

AArcitec If you're interested, GitHub (Microsoft) will build your OS images daily accordi...

ragectlOP•5/14/23, 3:02 PM

we do have Enterprise account for work, so we could always run it under our own if we really had to. But making it available would also be useful

AArcitec If you're interested, GitHub (Microsoft) will build your OS images daily accordi...

xyny•5/14/23, 3:02 PM

After you have that, I suggest creating a new branch called something unique, like rage-osrage-os, set that as your main branch in GitHub's repo settings.

Here's a job for you: write down the reasoning and instructions for that (and related activities) and PR on the website.

Xxyny > After you have that, I suggest creating a new branch called something unique, ...

Arcitec•5/14/23, 3:03 PM

For uBlue's website or for startingpoint's readme?

AArcitec The reason for branching is so that you can easily fast-forward `main` to upstre...

xyny•5/14/23, 3:03 PM

Didn't think of that. I've been using git merge commits with manual merges to handle getting updates.

Arcitec•5/14/23, 3:03 PM

Hehe. It's easier to rebase between branches yeah.

Rragectl we do have Enterprise account for work, so we could always run it under our own ...

Arcitec•5/14/23, 3:04 PM

You can definitely self-host the build and container images, but it requires changing the .github.github directory's workflow actions to something you self host.

AArcitec For uBlue's website or for startingpoint's readme?

xyny•5/14/23, 3:04 PM

The docs website, yes. The page make-your-own (or whatever) has more general instructions for creating custom images and all the repo setup stuff. Startingpoint's readme is more about startingpoint's configuration.

ragectlOP•5/14/23, 3:04 PM

Rebase with fast forward is really useful for forks

Xxyny The docs website, yes. The page make-your-own (or whatever) has more general ins...

Arcitec•5/14/23, 3:04 PM

Yeah, sounds good. I'll add it to my todos and can add do that sometime next week.

AArcitec You can definitely self-host the build and container images, but it requires cha...

ragectlOP•5/14/23, 3:06 PM

that's also something we do for a few public GitHub Actions already. Having an Action to update Action versions

Rragectl that's also something we do for a few public GitHub Actions already. Having an A...

Arcitec•5/14/23, 3:07 PM

Hehe. I have been thinking of self-hosting uBlue too. But GitHub doesn't seem to mind hosting 90 days of <large> container revisions for now.

Arcitec•5/14/23, 3:09 PM

There is also an option to pay for GHCR (Github) which doesn't sound too bad if they start charging for the storage. It will probably remain cheap if they decide to add a fee.

j0rge•5/14/23, 3:12 PM

ublue-os/forge is a self hosting setup, more eyes there appreciated!

Arcitec•5/14/23, 3:15 PM

I had totally forgotten about forge! It's a very smart idea, to have an easy selfhost process. I guess GHCR is too easy to use to pass up now though.

Rragectl Oh, one thing I haven't tested on my uBlue install on my laptop earlier was the ...

akdev•5/14/23, 3:15 PM

I use it for gpg/u2f/webthn and it works fine

akdev•5/14/23, 3:16 PM

haven't done the work to integrate it into pam

akdev•5/14/23, 3:16 PM

it should work the same as regular fedora tho https://docs.fedoraproject.org/en-US/quick-docs/using-yubikeys/

xyny•5/14/23, 4:17 PM

https://github.com/ublue-os/website/pull/233

GitHub

feat: add diagram of different editions / images by EinoHR · Pull R...

ublue-os/main#130

Rragectl Wez does build rpms for each release hosted on GitHub, so I could just cheat by ...

bsherman•5/14/23, 5:08 PM

i add wezterm to my custom images... not proposing you use my image, but i've got a helper script to make it easier to install an RPM direct from a github releases page

https://github.com/bsherman/ublue-custom/blob/main/Containerfile#L27

Xxyny https://github.com/ublue-os/website/pull/233

Arcitec•5/14/23, 6:29 PM

That's a really nice initiative.

Too bad that there isn't an easy way to make CSS / div grids in markdown, so that we could generate that entirely in HTML...

Bbsherman i add wezterm to my custom images... not proposing you use my image, but i've go...

Arcitec•5/14/23, 6:30 PM

Hah that's a very nice idea!

Thanks for sharing! https://github.com/bsherman/ublue-custom/blob/main/github-release-install.sh

AArcitec That's a really nice initiative. 🙂 Too bad that there isn't an easy way to make...

xyny•5/14/23, 6:33 PM

Well you can use just plain html in markdown, but it's not nice. And extending MkDocs would probably be possible too.

xyny•5/14/23, 6:33 PM

I kinda like it just being a png though, because it's easily shareable,,, and I can make it in Figma.

xyny•5/14/23, 6:35 PM

Those logos are customized to fit the colors inside the same main Figma frame, but it would have to be done separately if it wasn't a image.

Xxyny I kinda like it just being a png though, because it's easily shareable,,, and I ...

Arcitec•5/14/23, 7:50 PM

PNG is definitely the easiest solution. Anything else would require the ability to use CSS styles to create something like https://www.fedoraproject.org/workstation/ and that's just so much work.

bsherman•5/14/23, 9:14 PM

I've got some PRs needing approval:

2.5Gbit USB udev rules https://github.com/ublue-os/config/pull/36
standardize path and justfile refactoring https://github.com/ublue-os/config/pull/42
nvidia justfile removal after config PR 42 https://github.com/ublue-os/nvidia/pull/101

Bbsherman I've got some PRs needing approval: - 2.5Gbit USB udev rules https://github.com/...

Arcitec•5/14/23, 9:17 PM

I checked the last two PRs, they both look ready to me.

AArcitec I checked the last two PRs, they both look ready to me. 🙂

bsherman•5/14/23, 9:18 PM

thank you, I definitely appreciate the feedback you've been giving to get this stuff done, but now I need PR approval from someone with commit in those repos

Bbsherman thank you, I definitely appreciate the feedback you've been giving to get this s...

Arcitec•5/14/23, 9:20 PM

Yep!

While we wait... I am working on improving the way people fork startingpointstartingpoint and I'm not sure which path is cleaner, so let's hear opinions:

A:

Mark the GitHub workflow as "only build the mainmain branch".
Users fork the startingpointstartingpoint repo.
They turn it away from "template" mode into regular repo mode.
They create a branch called upstream-mainupstream-main and link it to upstream/mainupstream/main.
They perform their own edits in mainmain.
They periodically sync upstream-mainupstream-main and then rebase their own mainmain onto upstream-mainupstream-main to get the latest template improvements.

Mark the GitHub workflow as "only build the
```
build
```
```
build
```
branch".
Users fork the startingpointstartingpoint repo.
They turn it away from "template" mode into regular repo mode.
They link mainmain to upstreamupstream for easy syncing. Although they can do that effortlessly via the GitHub web UI with one click since that's doable by default.
They create a
```
build
```
```
build
```
branch and perform their own edits there.
They periodically sync mainmain and then rebase their own
```
build
```
```
build
```
onto mainmain to get the latest template improvements.

I think I like the

build

build

idea (B) because the naming is more deliberate and clear. Syncing via web UI also becomes possible. I kinda wish startingpoint's main branch was named templatetemplate instead of mainmain.

Switches•5/14/23, 9:21 PM

@j0rge is busy gaming if the discord status is right lol.

Switches•5/14/23, 9:22 PM

but took a look at them and they make sense to me, the changes make it much cleaner imo and more traceable if any problems did arise.

AArcitec Yep! 🙂 While we wait... I am working on improving the way people fork `starting...

Arcitec•5/14/23, 9:25 PM

Seeing it point by point like that made it easier to decide... I think a dedicated

build

build

branch makes the most sense. It also allows us to move away from mainmain to rename the main branch to templatetemplate in the future.

Switches•5/14/23, 9:29 PM

I think the naming comes down to the actual build process, we did change the name of the Kinoite builds at one point and it went a little wonky... not sure the issue is something that can fixed this side. It's like they have a "required" way of doing things (just my take on it though).

SSwitches I think the naming comes down to the actual build process, we did change the nam...

Arcitec•5/14/23, 9:30 PM

Yeah those "required names" are specified inside the .github/.github/ directory's workflow files. This is about making it easier to work with the ublue-os/startingpointublue-os/startingpoint repo, for people who decide to clone it and make their own uBlue images.

Switches•5/14/23, 9:30 PM

Ahh right, not looked into it myself, just going from past experience as it were lol

Arcitec•5/14/23, 9:33 PM

Yeah it's all very interlinked in the main and nvidia repos.

Bbsherman I've got some PRs needing approval: - 2.5Gbit USB udev rules https://github.com/...

j0rge•5/14/23, 9:44 PM

got em!

j0rge•5/14/23, 9:45 PM

oh I went in the wrong order though so I'll rekick off main/nvidia

Jj0rge got em!

Arcitec•5/14/23, 9:46 PM

Sweet beans!

Jj0rge got em!

bsherman•5/14/23, 9:46 PM

I think we were discussing "merge" vs "squash merge" the other day... i think it defaults to either last thing you did or last thing done on the repo, one of two...

because I noticed a main/nvidia PR merge was squashed but the recent config merges are not quashed

fiftydinar•5/14/23, 9:46 PM

Is it possible to fix 3.5mm front panel not working from Realtek sound card inside the ISO?

This is the fix:
https://discussion.fedoraproject.org/t/front-panel-headphone-jack-is-not-being-detected/78370/2

It doesn't work on installed system due to r/o path it needs to modify, /usr/ something, forgot which

Fedora Discussion

Front Panel Headphone Jack is Not Being Detected

Ok. I was able to fix this. 1 - install alsa-tools: $ sudo dnf install alsa-tools; 2 - open HDA Jack Retask: $ hdajackretask; 3 - at the top, verify if the right codec is selected in “Select a codec”. On my case, the right one is “Realtek ALC897”; 4 - on “options”, at the right, click on “Set model=auto” and “advanced override”; 5 - on “pin...