Yeah. I read on reddit that we got 84% of the popular vote though, so I'm just sayin fuck the jury a
Yeah. I read on reddit that we got 84% of the popular vote though, so I'm just sayin fuck the jury and we won.
XIt's a shame Loreen got a win a second time with a much worse song.
XIg they want Eurovision in Sweden next year as it's also Abba's 50 year anniversary.
RI think I saw @j0rge do that in one of his videos 
Rit's on there, but the website will tell you it's only intended for people to have a first loo, because it doesn't allow some of the configuration
R
RSee the note on that section
RThe flatpak is provided primarily for ease of trying out wezterm with low commitment, and you are encouraged to use native packages for your system once you're ready to get the most out of wezterm.
AI agree, Loreen's song is the typical bland modern pop stuff. Your song was hilarious. And it won the people's vote. 
AOh okay, but perhaps they're talking about some rare functionality that you aren't using. Try it and see if it works. 
Terminals on Flathub are no big problem; they just need to be aware of Flatpak env and call
Terminals on Flathub are no big problem; they just need to be aware of Flatpak env and call flatpak-spawn --host <name of shell binary> to spawn a shell that runs entirely unsandboxed. While the terminal GUI itself is sandboxed. So most terminals work perfectly in Flathub. If you really need it natively then I can help you get started with making a custom uBlue OS.RWez 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
RI asked about the packages on Matrix and a few minutes later he'd replaced Fedora35 with Fedora38 
AIf 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
Now just start editing
After you have that, I suggest creating a new branch called something unique, like
rage-osNow just start editing
recipe.ymlyafti.ymlOh, 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?
AThe reason for branching is so that you can easily fast-forward
mainrage-osI think I saw some rules added to support it, but I haven't tested
AYeah there's device rules installed for that but I don't use it personally
Jyou can also just add it as your day to day terminal but leave the stock terminal there
JI use gnome-terminal as my host
Jand then blackbox flatpak for distroboxes
Rwe 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
XAfter you have that, I suggest creating a new branch called something unique, like, set that as your main branch in GitHub's repo settings.rage-os
Here's a job for you: write down the reasoning and instructions for that (and related activities) and PR on the website.
AFor uBlue's website or for startingpoint's readme?
XDidn't think of that. I've been using git merge commits with manual merges to handle getting updates.
AHehe. It's easier to rebase between branches yeah.
AYou can definitely self-host the build and container images, but it requires changing the
.githubThe 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.
RRebase with fast forward is really useful for forks 
AYeah, sounds good. I'll add it to my todos and can add do that sometime next week.
Rthat's also something we do for a few public GitHub Actions already. Having an Action to update Action versions 
AHehe. 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.
AThere 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.
Jublue-os/forge is a self hosting setup, more eyes there appreciated!
AI 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.
AI use it for gpg/u2f/webthn and it works fine
Ahaven't done the work to integrate it into pam
Ait should work the same as regular fedora tho https://docs.fedoraproject.org/en-US/quick-docs/using-yubikeys/
X
Bi 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
https://github.com/bsherman/ublue-custom/blob/main/Containerfile#L27
AThat'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...
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...
AHah that's a very nice idea! Thanks for sharing! https://github.com/bsherman/ublue-custom/blob/main/github-release-install.sh
Thanks for sharing! https://github.com/bsherman/ublue-custom/blob/main/github-release-install.shXWell you can use just plain html in markdown, but it's not nice. And extending MkDocs would probably be possible too.
XI kinda like it just being a png though, because it's easily shareable,,, and I can make it in Figma.
XThose 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.
APNG 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.
BI'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
AI checked the last two PRs, they both look ready to me.
Bthank 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
AYep! While we wait... I am working on improving the way people fork
A:
While we wait... I am working on improving the way people fork startingpointA:
- Mark the GitHub workflow as "only build the
branch".main - Users fork the
repo.startingpoint - They turn it away from "template" mode into regular repo mode.
- They create a branch called
and link it toupstream-main
.upstream/main - They perform their own edits in
.main - They periodically sync
and then rebase their ownupstream-main
ontomain
to get the latest template improvements.upstream-main
- Mark the GitHub workflow as "only build the
branch".build - Users fork the
repo.startingpoint - They turn it away from "template" mode into regular repo mode.
- They link
tomain
for easy syncing. Although they can do that effortlessly via the GitHub web UI with one click since that's doable by default.upstream - They create a
branch and perform their own edits there.build - They periodically sync
and then rebase their ownmain
ontobuild
to get the latest template improvements.main
buildtemplatemain
S@j0rge is busy gaming if the discord status is right lol.
Sbut 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.