How do I troubleshoot `bluebuild switch`
I downloaded the blue95 installer and loved it, wanted to try the blue7 module. I ran the
just build for blue7 and it ran bluebuild switch -- the script said it was installing the new image but when I rebooted, the old image came back up. How might I go about diagnosing why it failed?6 Replies
I've not heard of
blue95 or blue7. What are you talking about? You can always add -vv for trace loggingthey're two images that utilize bluebuild to emulate classic windows UIs: https://github.com/winblues/blue95 and https://github.com/winblues/blue7
I think my question was more along the lines of "I don't even know where to look to establish chain of custody" if that makes sense
The
bluebuild switch command seems to happen without an error, but then when I reboot it still goes into the old image -- what does bluebuild switch actually do from a backend perspective so I can go check config files or logs to make sure whatever switch that needs to be flipped, is flipped, so the new image is executed?It builds the image, exports it as a tarball to
/etc/bluebuild/ and calls rpm-ostree rebase/upgradeok, great, so whatever's wrong is probably in how rpm-ostree is being called (or some other confounding factor of my install) -- I'll see if I can find more docs about rpm-ostree and see if it points to why I'm having an issue. Thank you!
you may also ask @ledif since they're the maintainer of blue95 and blue7 iirc
Blue95 is really the only image in the Winblues org (besides Vauxite) that is stable at the moment. The rest are kind of in an alpha state. Their READMEs are basically empty but maybe I should make it clearer that they aren't finished