Hey folks! Just wanted to send out a heads-up for Rawhide users about some issues that have shown up in openQA testing. First, you may have found that trying to update to today's Rawhide fails like this: Error: Transaction test error: file /usr/lib/python3.11/site-packages/ptyprocess-0.7.0-py3.11.egg-info from install of python3-ptyprocess-0.7.0-2.fc38.noarch conflicts with file from package python3-ptyprocess-0.7.0-1.fc38.noarch That's https://bugzilla.redhat.com/show_bug.cgi?id=2164207 , we figured out the problem (thanks to Panu for getting to the root cause of it) and it is fixed in python-ptyprocess-0.7.0-3.fc38 , which should be in the next Rawhide compose. If you really can't wait you can update directly to that version from https://koji.fedoraproject.org/koji/buildinfo?buildID=2138649 , but you'd better watch out for issue #2... The second issue is that systems that update to systemd-253~rc1-1.fc38 seem to get stuck on boot. With Plymouth enabled you just see the splash screen. With it disabled (or by pressing esc) it seems to be stuck at "Stopped initrd-switch-root.service - Switch Root.". I'm still looking into this one, but it's happened to a lot of openQA tests and I was able to confirm it first try in a local VM, by installing from the 20230123.n.0 compose then updating systemd and rebooting. Fresh installs with the newer systemd seem to be OK, at least most openQA tests for the new compose passed - it seems to be only updating an existing install that has the problem, at least so far. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue