if it was more of a generic tool, i think `ostree imager` would be descriptive enough 😛
if it was more of a generic tool, i think 
ostree imager would be descriptive enough 
Xthat's very cryptic, and usually an imager makes images, right?
Hok fine
Htouch base with ostree there /sXrebasing is a fine term but will be phased out with bootc switch so...
Hin all seriousness could be anything from rebaser to switcher
Xsomething related to switching would be better i think
XThings that are bothering me as a visual person:
- The rebase button is pretty hidden and feels like it's in the wrong place. It should probably be a primary color and not a background color. I would also place it just next, above, or below to the rebase command. Maybe the command should be hidden by default...
- The dropdowns are all different sizes and are maybe a bit too high. The space between the command and the dropdowns is too huge compared to the space with edges.
- The links to the image list and faq feel out of place, but I get they're probably not ready.
Ball ublue-os/main builds failed ... a network/dns issue on the builder machines... so I'm attempting a retry
BBBLooks like schedule maintenance on COPR servers
CYeah. I'm used to working in HTML and CSS rather than XML, so that's a large part of why "polish UI" was at the top of my to do list. I should be able to fix most or all of those things
CI want the rebase command and links to be present in some way, probably alongside some other info/links, but there are ways to hide those from the users who wouldn't get anything from them anyway
CA priority for me is to keep all this as compact and simple as possible so I am not the only one who can maintain it
EYup. Just encountered that trying to fix Bazzites builds
EThought it was my network connection for a minute there lol
ELooks like RPM Fusion is doing a bit of maintenance too. At least pkgdb appears to be down
Jwhere's that xkcd
J
Jbut it's maintenance
ELol
EIt's back
Dyeah there hasn't been a successful build for 8 days
C>no update for 8 days, the horror
vs: arch broke three different critical ways upstream in the last 8 days
or: ubuntu broke half a year ago because of a still two year old package
vs: arch broke three different critical ways upstream in the last 8 days
or: ubuntu broke half a year ago because of a still two year old package
CI like it here lol
CI don't mean to call out arch or ubuntu specifically, I just thought it was fascinating and worth noting that the lack of a (broken) update for a week is about the extent of things going wrong here
Dwow. glad I am using an immutable distro
CSame 
Hno veteran is going to say youre wrong though if they have used linux long enough
CI'd hope so, at least - mostly because we have the concrete evidence right there in the failed builds. I think I saw 3 different critical breakages Arch would have ingested in regular updates, and I imagine the glibc (library?) update would cause long-term issues for Debian/Ubuntu as apps update beyond system packages. Here, all three hit, and just.. never reached users, and we stay on the last stable update for a few days/weeks until a stable one builds successfully
Hhence why i liked the idea of bazzite and ublue
i do however keep around 1 computer with a normal system for you know, actual testing outside of the mutability when needed
i do however keep around 1 computer with a normal system for you know, actual testing outside of the mutability when needed
Cheh, yeah 
EI know. Used to frantically check for updates (especially for my custom ROM'd Android devices) over the years, and it's at the point where I am just so happy it all happens in the background. Last thing I want to see unless I'm fixing/testing something
CSame! I think it's good to occasionally contextualize the development work here with perspectives like this
Hi wouldnt worry about lack of builds succeeding unless its been like 3weeks to 1 month (with some exceptions if there is some super massive security flaw actively being exploited and its RCE)
CYep
EIt would be a lot different in my eyes if something like main wasn't building or akmods or insert whatever core repo here since literally everything branches from that and depends on it, but one week isn't the end of the world otherwise
EIf anyone has the time I'd really appreciate a couple reviews. Overlooked this
https://github.com/ublue-os/config/pull/165
https://github.com/ublue-os/config/pull/165
GitHub
The nix justfile was overwriting ujust instead of being copied over to the directory containing the rest of the justfiles
J@EyeCantCU I kicked off akmods, but I'm hitting the sack, someone will need to kick off main and then bazzite to get that fix
EThank you! I'll be here to kick them off
Blet me know if there's something else to help with
EAppreciate it, I think we're good for now
B
GitHub
adds missing incus-agent package
Bwhat is source of incus package?
Ba copr from gantoo
Swhat is ujust?
Ha helper script for just to just load the ublue default just files
think of it as a bunch of cli command shortcuts/recipes (similar to aliases but you can list all of them if you forget them)
think of it as a bunch of cli command shortcuts/recipes (similar to aliases but you can list all of them if you forget them)
SBut isn't just anyways installed?
Hit is
Sdamn this whole thing is such a mess
