@adamw@fosstodon.org avatar

adamw

@adamw@fosstodon.org

Fedora QA team lead. If Fedora isn't working, it's probably my fault! he/him/his

This profile is from a federated server and may be incomplete. Browse more on the original instance.

adamw, to fedora
@adamw@fosstodon.org avatar

39 Beta is signed off and will be released on Tuesday Sep 19! https://discussion.fedoraproject.org/t/fedora-linux-39-beta-is-go/89893

adamw, to fedora
@adamw@fosstodon.org avatar

Heads up, if you're lucky enough to be running on a AMD board - you probably want to update the firmware to version 3.03 (recently made available). according to feedback, it solves several problems folks were running into. https://community.frame.work/t/amd-ryzen-7040-series-bios-3-03-and-driver-bundle-beta/38655

adamw, to fedora
@adamw@fosstodon.org avatar

: if you're having trouble reaching stuff - it's because we're being DDoSed. fun times. @nirik is on it, as always, as far as it's possible to be on it anyway...

adamw, to fedora
@adamw@fosstodon.org avatar
adamw, to random
@adamw@fosstodon.org avatar

"open source is free as in puppies" - @rbowen

adamw, to fedora
@adamw@fosstodon.org avatar

PSA: if you're trying to upgrade to 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.

adamw, to fedora
@adamw@fosstodon.org avatar

today:

  • ran a very long and complicated 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 staging instance to fedora 39 and latest openqa/os-autoinst builds, seems to be fine so far
adamw, to random
@adamw@fosstodon.org avatar

It's happening!

adamw, to fedora
@adamw@fosstodon.org avatar

hey folks! I'm floating the idea of possibly dropping client support from the Fedora release criteria (so it'd still be there, but we wouldn't be required to test it every cycle and block the release if it fails). I'm looking for input.

is it a feature of Fedora you value? is it important enough to spend significant time automating (or continuing to test manually)?

thoughts here, or at https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/VKTFTPD5SXYX7YLRU7LFVWKYKKJL5H56/ , or https://discussion.fedoraproject.org/t/fedora-server-front-page-revamp-looking-for-feedback/79037/9

thanks!

adamw, to fedora
@adamw@fosstodon.org avatar

Today:

  • waiting for the next unfortunately-timed news
  • still waiting
  • still waiting
  • nobody? Ok, the qa team would like to announce our new cryptocurrency-focused metaverse project
adamw, to random
@adamw@fosstodon.org avatar

Now at presents: A Week With @Conan_Kudo - activating the community to build cloud images

adamw, to fedora
@adamw@fosstodon.org avatar

yesterday and today: travel to ! I am here safely and will be presenting on the current state of automated testing in - that's and basically - at 3:30pm tomorrow in "Harbour 6". be there or...be somewhere else, it's up to you really! especially if you saw this talk one of the other three times I did it :D

https://flock2023.sched.com/event/de3fad0bd62299124e0ac852b71ee772

adamw, to random
@adamw@fosstodon.org avatar

today:

adamw, to random
@adamw@fosstodon.org avatar

writes long email
re-reads long email to try and edit it to be shorter
adds more sentences to it instead

adamw, to fedora
@adamw@fosstodon.org avatar

today in qa: i'm testing . I think I might be doing this wrong

adamw, to Bash
@adamw@fosstodon.org avatar

pop quiz! how, from a bash console, using GNU grep, do you grep for a string of four backslashes?

adamw, to random
@adamw@fosstodon.org avatar

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.

adamw, to fedora
@adamw@fosstodon.org avatar

today:

adamw, to random
@adamw@fosstodon.org avatar

today: did my talk at , I think it wasn't quite as good as at devconf.cz because I was pretty tired, but went well enough! I'll post a link to a recording when one is up somewhere. lots of attending talks (some good ones on CPE team status and rpminspect), hallway track, pub quiz...now to try and get some sleep

adamw, to python
@adamw@fosstodon.org avatar

today:

adamw, to random
@adamw@fosstodon.org avatar

new blog post (yes I still remember how, apparently) on devconf.cz and other things (mostly already covered here): https://www.happyassassin.net/posts/2023/06/20/devconfcz-2023-rawhide-update-test-gating-eln-testing-and-more/

mcdanlj, to fedora
@mcdanlj@social.makerforums.info avatar

I'm on 40, and I'm now seeing a lot of "No video with supported format and MIME type found" errors.

I don't have mozilla-openh264 installed, so I guess that might make sense? Let's fix that...

# rpm-ostree install mozilla-openh264<br></br>...<br></br>error: Could not depsolve transaction; 1 problem detected:<br></br> Problem: package noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64 from @System conflicts with openh264 provided by openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264<br></br>  - package openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264 obsoletes noopenh264 < 1:0 provided by noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64 from @System<br></br>  - package mozilla-openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264 requires openh264(x86-64) = 2.4.0-2.fc40, but none of the providers can be installed<br></br>  - conflicting requests<br></br># rpm -qa | grep noopenh264<br></br>noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64<br></br># rpm-ostree install --uninstall noopenh264 mozilla-openh264<br></br>error: Package/capability 'noopenh264' is not currently requested<br></br>

There's clearly something I don't understand here. I don't know how noopenh264 is installed but not requested and still causes a conflict. I must be alone in having this problem based on lack of bugs that I can find in RH's bugzilla.

I don't think I saw this problem on Silverblue 39, but I was using that for only a few days before rebasing on 40, and was previously on my "classic" Fedora 39 installation where it definitely wasn't showing up with the rpmfusion packages installed.

adamw,
@adamw@fosstodon.org avatar

@mcdanlj @garrett @notting that's an interesting idea, not sure I've heard it floated before...not sure who to pass it on to, maybe mcatanzaro or @siosm ?

adamw, to random
@adamw@fosstodon.org avatar

today:

  • 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
  • emerged, at least, with https://src.fedoraproject.org/rpms/inxi/pull-request/1 to fix downstream problems

In case anyone was reading along at home with popcorn, here's how that test matrix turned out...

adamw,
@adamw@fosstodon.org avatar

(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!)

tulpa, to fedora
@tulpa@fosstodon.org avatar

The fact that exists and provides a valuable service just proves that Atomic makes it too hard for sysadmins to customize their installs. Because what they are doing is mostly just changing which packages get installed in the base image.

adamw,
@adamw@fosstodon.org avatar

@tulpa this is broadly the point of https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable , which we've been working through for a while now.

qlp, to debian
@qlp@linh.social avatar

Debian users who are using testing, unstable or experimental may want to be wary of the compromised version of xz. This is tied to the same notification that went out for Fedora 41, some Fedora 40 and Rawhide users.

https://lists.debian.org/debian-security-announce/2024/msg00057.html

adamw,
@adamw@fosstodon.org avatar

@qlp
The issue was actually discovered by a Debian dev (thanks!) and certainly does affect any branch of Debian where 5.6.1 showed up.

So far the consensus seems to be that the exploit probably didn't work in 5.6.0, but you should still downgrade any 5.6.0 install for safety.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • thenastyranch
  • magazineikmin
  • cubers
  • InstantRegret
  • cisconetworking
  • Youngstown
  • vwfavf
  • slotface
  • Durango
  • rosin
  • everett
  • kavyap
  • DreamBathrooms
  • provamag3
  • mdbf
  • khanakhh
  • modclub
  • tester
  • ethstaker
  • osvaldo12
  • GTA5RPClips
  • ngwrru68w68
  • Leos
  • anitta
  • tacticalgear
  • normalnudes
  • JUstTest
  • All magazines