Hey folks!
So we have F30 and F31 updates that need testing:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-02ee4b1a1c (F30) https://bodhi.fedoraproject.org/updates/FEDORA-2020-717d521d35 (F31)
These are intended to fix problems when upgrading to F32 caused by modules doing stuff they shouldn't; they do this by resetting all modules as part of the upgrade. We need folks to test that upgrading to F32 after installing these updates works OK.
To test, *first* install the updates on F30/F31, *then* run an upgrade to F32 with `dnf system-upgrade` (see https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ). Of course, since F32 is pre-Beta ATM, don't do this on important or production systems unless you're really sure you want to run a pre- release on them!
If the upgrade works OK and you don't see any module-related weirdness, please +1 the update. If the upgrade has issues, don't -1 the update right away as the issues might be unrelated to it; please post here and we'll try and figure out the problem.
Thanks!
On Wed, Mar 11, 2020 at 5:47 AM Adam Williamson adamwill@fedoraproject.org wrote:
Hey folks!
So we have F30 and F31 updates that need testing:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-02ee4b1a1c (F30) https://bodhi.fedoraproject.org/updates/FEDORA-2020-717d521d35 (F31)
These are intended to fix problems when upgrading to F32 caused by modules doing stuff they shouldn't; they do this by resetting all modules as part of the upgrade. We need folks to test that upgrading to F32 after installing these updates works OK.
To test, *first* install the updates on F30/F31, *then* run an upgrade to F32 with `dnf system-upgrade` (see https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ). Of course, since F32 is pre-Beta ATM, don't do this on important or production systems unless you're really sure you want to run a pre- release on them!
If the upgrade works OK and you don't see any module-related weirdness, please +1 the update. If the upgrade has issues, don't -1 the update right away as the issues might be unrelated to it; please post here and we'll try and figure out the problem.
Thanks!
Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
Fedora 30 with RPM fusion repos enabled throws an GPG key error. Removal of RPM fusion repos and all the packages upgrades F30 to F32 just fine.
Adam Williamson composed on 2020-03-10 17:15 (UTC-0700):
So we have F30 and F31 updates that need testing:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-02ee4b1a1c (F30) https://bodhi.fedoraproject.org/updates/FEDORA-2020-717d521d35 (F31)
These are intended to fix problems when upgrading to F32 caused by modules doing stuff they shouldn't; they do this by resetting all modules as part of the upgrade. We need folks to test that upgrading to F32 after installing these updates works OK.
To test, *first* install the updates on F30/F31, *then* run an upgrade to F32 with `dnf system-upgrade` (see https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ). Of course, since F32 is pre-Beta ATM, don't do this on important or production systems unless you're really sure you want to run a pre- release on them!
If the upgrade works OK and you don't see any module-related weirdness, please +1 the update. If the upgrade has issues, don't -1 the update right away as the issues might be unrelated to it; please post here and we'll try and figure out the problem.
I tried pulling the 31 to 32 trigger, but see this: ... vim-minimal Resetting modules: dwm
Transaction summary ... Install 19 Upgrade 1169 Downgrade 33
Total download size: 909M DNF will only download...
On 3/11/20 12:28 AM, Felix Miata wrote:
I tried pulling the 31 to 32 trigger, but see this: ... vim-minimal Resetting modules: dwm
Transaction summary ... Install 19 Upgrade 1169 Downgrade 33
Total download size: 909M DNF will only download...
That looks fine to me, where do you think the problem is?
Samuel Sieb composed on 2020-03-11 00:41 (UTC-0700):
Felix Miata wrote:
I tried pulling the 31 to 32 trigger, but see this: ... vim-minimal Resetting modules: dwm
Transaction summary ... Install 19 Upgrade 1169 Downgrade 33
Total download size: 909M DNF will only download...
That looks fine to me, where do you think the problem is?
From Adam's description I thought no modules were supposed to get reset, and I don't know what module dwm is about.
On Wed, Mar 11, 2020 at 8:49 AM Felix Miata mrmazda@earthlink.net wrote:
From Adam's description I thought no modules were supposed to get reset, and I don't know what module dwm is about.
The reverse. All modules are getting reset during upgrade, that's intended.
On Wed, 2020-03-11 at 15:25 +0100, Kamil Paral wrote:
On Wed, Mar 11, 2020 at 8:49 AM Felix Miata mrmazda@earthlink.net wrote:
From Adam's description I thought no modules were supposed to get reset, and I don't know what module dwm is about.
The reverse. All modules are getting reset during upgrade, that's intended.
Confirmed, sorry if my description was unclear! If you see modules getting reset, that means it's working as intended =)