Hey folks. I wonder if we couldn't add in some (re)testing of upgrades after a release is 'go' but before it's actually released. We hit at least two issues I am aware of with f34 due to multilib. ;( first: pipewire.i686 is in the base x86_64 repo and users had/have it installed. pipewire.i686 is pulled into the x86_64 base repo by mutter (mutter.i686 is there and requires pipewire.i686). In any case it is not in the updates repo, so once an update of them is pushed (which it has been), upgrades fail due to the missing packages. I have modified the updates pungi config to whitelist pipewire for multilib and it's in f34-updates now. second: There's still an issue with iptables. See https://bugzilla.redhat.com/show_bug.cgi?id=1953178 basically the version in the base repo has a 'iptables' package. The one in updates Obsoletes this for a iptables-compat, but yet it's not doing things correctly as users are getting dnf errors. Anyhow, I think it might be good to perhaps schedule some re-resting of upgrades after the 0 day updates repo is populated to try and catch these and fix them before release day. We can't test this fully before there is an updates repo (I mean we kind of can with updates-testing, but it's not the exact same repo). kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
