akdev we missed a couple issues in my
@akdev we missed a couple issues in my PR
https://github.com/ublue-os/main/pull/310 I feel like thats a pattern for me... do something pretty good and working with good testing the first time... ⭐ Try to improve it a bit more... don't test quite as well... merge it... it's broken 😢 ...
https://github.com/ublue-os/main/pull/310 I feel like thats a pattern for me... do something pretty good and working with good testing the first time... ⭐ Try to improve it a bit more... don't test quite as well... merge it... it's broken 😢 ...
p5 bsherman akdev Bigpod EyeCantCU 1 4
@_p5 @bsherman @akdev @Bigpod @EyeCantCU @KyleGospo Your inbox is about to explode with permission updates, you are now "Approvers" and over the next few hours/days I'll be removing individual accounts for all the repos and just adding this team. This was blocking one of our biggest goals, I'd like to merge this tonight so last call on governance. +1's and comments in the thread and I'll explain how all the other repos will work.
``` fedora fedora 38 x86 64 silverblue
``` fedora:fedora/38/x86_64/silverblue
Version: 38.20230819.0 (2023-08-19T00:42:32Z)
Commit: 1e0a8d426c680e8ececaeb458f1796015c4755452cd4f8184d42ca43be23dbb0
GPGSignature: Valid signature by 6A51BBABBA3D5467B6171221809A8D7CEB10B464
Diff: 1 removed, 2 added...
ARM Enablement
https://pagure.io/fedora-asahi-remix-ostree/tree/f39 - I have put the stuff I am doing with fedora asahi remix on this repo
supergfxctl
so, just for reference, this is what i suspected... the copr repo file is getting set to disabled before the install command runs, which we can see here
```
Installing: supergfxctl-5.1.1-0.x86_64 (copr:copr.fedorainfracloud.org:lukenukem:asus-linux)
+ cat /etc/yum.repos.d/jhyub-supergfxctl-plasmoid.repo...
Installation - Universal Blue
Thanks the report... this is mentioned on the website's ISO install docs under "Secure Boot"
https://ublue.it/installation/#secure-boot but you provide some nice step-by-step details which should be added there and in a FAQ section which does not currently exist.
I am starting to think the MOK importer is pretty similar across different machines and UEFI implementations, so that's good for providing more detail.
...
It realy doesnt make sense at this point
It realy doesnt make sense at this point to build everything from scratch ourself as the point is for us to build uppon what fedora image based distros provide, there would also be not much of a benefit to us going from scratch
I ll kick off main and then nvidia just
I'll kick off main and then nvidia, just to test again formally,
Incorporate front panel 3.5mm fix for Realtek sound cards & laptop multiple speakers setup
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
...
though it does require changes for the
though it does require changes for the nvidia.just and custom.just to be made in config ... but i think that's probably not a concern.I commented on the PR regarding that. The inclusion of the NVIDIA config in the "main justfile config RPM" kinda makes sense in a lot of ways. The issue is the
custom.just, it's currently holding anything added by startingpoint + anything the person making a downstream image wants to add to it (they fork startingpoint and add their own stuff to custom.just), so we can't include that one in the main config repo....just running the install it complains
just running the install it complains about
unknown device before the test starts. Is that expected?For example I m still not quite sure
For example I'm still not quite sure whether akmods (xone, v4l2loopback,...) should be included in main or be their own image.
Here is the new structure meant to
Here is the new structure, meant to ensure people can't break images when switching flavors, and also ensuring that the user always runs the latest, intended script for that distro.
Wait whats your spec looking like right
Wait, whats your spec looking like right now? You should
%global the variable first in the top section and then use that variable later.System-wide uBlue Location
Has there been any prior implementation or discussion about a place to store uBlue-related files that need to exist on the system, in an immutable, shared location?
There is a now need to fix an issue in uBlue-startingpoint's "autostart" script. It's currently being copied into every user folder once and then never again. Meaning that future fixes never get applied to it. It's very rigid.
I've got a solution but need a systemwide location to store the code in a shared location for all users....