today's embarrassing workflow confession: I just now switched to using git remote add instead of manually editing .git/config, which I've been doing for I think about a decade at this point
spent the entire day down a vast rabbit hole of ancient Fedora/EL release perl packaging stuff, trying to help a project which really didn't care to be helped. I should've taken a hint and quit sooner, but I am bad at stopping in the middle of things. Oh, well
(yes, I did manage to get a CentOS 6 system installed, on a network, and configured with working yum repos for the base system and EPEL. I was surprised too!)
caught up with shutdown email backlog (not too bad)
committed some updated #fedora#openqa needles I created over the shutdown but just left lying uncommitted on the prod server, did another small test fix
cleaned up the discussion thread on my big Bodhi PR a bit so it's easier to review (I hope)
updated openQA and os-autoinst packages to latest git
generated a big needle cleanup commit for openQA, put it on stg for testing
@adamw Yeah, he tends to go straight through like he's speed running it where for me, the side quests are often more important than the main story. I'm not a die hard completionist, but I'll often try to as long as it stays interesting.
today: more epic battling with the bodhi container development environment. fought ipsilon (fedora's identity...thingy) in a no-holds barred battle and eventually emerged victorious: now the dev env has a kinda 'real' identity layer, you can log in as different users with different capabilities, and be logged out.
this required me to write, uh, four patches (so far) for ipsilon. but it was the last big thing!
now i just need to tidy it all up, add some wrapper commands, and finally submit it.
PSA: if you're trying to upgrade to #fedora 39 early from 38, you may find it fails right now due to a file conflict in firmware packages. this is because F38's linux-firmware has got ahead of F39's. we can't fix it right away because of the F39 release freeze. it should be solved in a day or two. otherwise you can enable updates-testing, but of course that makes the upgrade a bit more risky.
ran a very long and complicated #fedora 39 go/no-go meeting, unfortunately we had to slip another week, sent out announcements and updated schedule and calendar
a bit of testing and bug reproduction
filed a stable push request, will probably request a new candidate compose soon
upgraded #openqa staging instance to fedora 39 and latest openqa/os-autoinst builds, seems to be fine so far
note the quote: "Cisco also said that the hacker’s ability to install malicious firmware exists only for older company products. Newer ones are equipped with secure boot capabilities that prevent them from running unauthorized firmware, the company said."
the #podman thing looks small, but it's quite a cool collaboration with upstream: what it (should) mean is that we catch when a change in something else, e.g. systemd, breaks something important in podman (more than we did already, by doing some functional testing of podman). upstream is excited about it, let's hope it works out well.
lots more trying to get #fedora#openqa update tests working post-F39 branching; I think I have it in a good state now, and gating is enabled for #rawhide again. All tests should pass for Rawhide updates, for F39 updates the desktop_background tests will fail as we don't have F39 backgrounds yet, I have dropped these from the gating policy for now
got sysadmin-main powers. somebody has made a terrible mistake somewhere
@funnelfiasco@adamw I need to watch it. It's "based in" the city I now live in, even though it wasn't actually filmed here. The 1966 Batman movie, however, was filmed here and I think of it every time I go by Stearn's Wharf.
Adam West voice: "Some days you just can't get rid of a bomb!"