most people use COPR and then just copy them into the image
most people use COPR and then just copy them into the image
Jthis has been annoying me all morning
Jhahahah
Jbut I think the practical answer is Bazzite has a more complicated user to cater to and it's easier for them to deal with the maintenance cost because it's better than a reviewer saying "it's missing this part vs. competitors."
Jwhere as I am trying to burn everything down with as little compromises to the design as I can get away with
Htrue, bazzites needs sometimes require stuff to be layered directly vs just running in distrobox/brew or whatever.
Hwe do go for flatpaks where we can though!
RThat's pretty fair
I'm glad I'll be able to keep using ublue
I'm glad I'll be able to keep using ublue
KYou can also build them locally in a fedora distrobox
KAnd then layer the result
KAssuming it doesn't work in distrobox in the first place
PNegativo still have 555 in his repo, no way to lock on it?
Dwhy would we downgrade to 555 with 560 out?
P560 is not out, it is in beta.
@Dylan 555 was pinned down for a reason. From my understanding it was supposed to be unppined after 560 official release. But mix of 555 and 560 module/driver happened and there was no other choice.
@Dylan 555 was pinned down for a reason. From my understanding it was supposed to be unppined after 560 official release. But mix of 555 and 560 module/driver happened and there was no other choice.
PBut maybe I don't understand the whole situation clearly.
DSounds like it should have been packaged as nvidia-beta so things didn't automatically update
PYeah, but unfortunately Negativo shipped it like this in his repository.
Hfirst rpmfusion now negativo 
KClearly the best repo to use is https://developer.download.nvidia.com/compute/cuda/repos/fedora39
K(/s, ofc)
ZIsnt there a way to make a snapshot of negativo rpm? So we dont end up dealing with bleeding-edge versions
Mupdate size has been much better. Significantly smaller
Mif the build is recent enough it's literally just the one small layer being redownloaded. Just much better on not having to download a multi gig layer at the end
Jyeah I did a cosmic update in a vm yesterday and it was like 350MB
RBeen trying to figure out how we can pin Negativo17 drivers to the non-beta ones, and I cannot figure it out.
Lots of package conflicts
Lots of package conflicts
Jah nuts I was on cosmic-base, had to do a rebase to just cosmic, so no savings on that one
ROur cosmic installations seem to be lagging behind quite a bit. The PopOS ISO has many more options in the settings pages for some reason, like being able to change the dock
MPretty much our cosmic image is whatever is packaged in the copr.
RAh. The cosmic-settings COPR build has been failing for over a week. An issue with the .desktop file
Jrepo's pretty much ready to go, I labelled a few incoming issues so the issue bot can warm up, should be good to go now
IGreetings, I created a PR for cosmic variant. It should add the ublue-os:config files to the cosmic image. Hope it works. Can someone start the build process, please?
Rwoah, this is big
Rrechunking is eventually coming to all ublue images I'm hoping?
Myeah. Trying to find the bugs
Rgood stuff
RGitHub
Thank you for contributing to the Universal Blue project!
Please read the Contributor's Guide before submitting a pull request.
Please read the Contributor's Guide before submitting a pull request.
Rpretty small PR
KSmaller updates too, The absolute minimum was previously 2 GB
Ralso, that command desperately needs a check to warn users not to use this on faulTPM vulnerable cpus
KAnd I just had a 400 MB update on testing
MIt should already have config. It builds from our main images
RRthis is much higher priority than the other one
Rthe vast majority of amd cpu users shouldn't be using tpm whatsoever
IThe current cosmic image only includes one udev rule. I edited the PR. This should include all other udev rules from ublue-os:config.
Rit's missing the policy file in /usr/share/containers/policy.json
maybe it just hasn't pulled this commit in yet?
https://github.com/ublue-os/config/commit/bfd1b6836006ef2c83c2dd3949f6e8d04bc0354d
maybe it just hasn't pulled this commit in yet?
https://github.com/ublue-os/config/commit/bfd1b6836006ef2c83c2dd3949f6e8d04bc0354d
R:thonk:
IIt is also missing a bunch of udev rules. Only one is included.
IInteresting. The official guide is outdated. The readme of ublue-os:config describes two ways to add the udev files. Both do not build. I am closing my PR.
IMultiple files from ublue-os:config seem to be missing in the cosmic image.
RThis is probably due to storing files in /usr/etc in ublue-os/main and using the rechunk action in cosmic
