Hi folks! So as you may have read, F26 Beta was held up by a tricky bug which causes upgrades to hang in some situations: https://bugzilla.redhat.com/show_bug.cgi?id=1397087 https://bugzilla.redhat.com/show_bug.cgi?id=1394862 There are updates in F24, F25 and F26 at present which we hope should resolve this bug without causing other problems, but the code in question is quite sensitive so we want to be as sure as possible that it's good to go. It would be great if folks can help test. You should probably only test if you're confident in the old RPM database recovery trick - 'rm -f /var/lib/rpm/__db* ; rpm --rebuilddb' - and on systems which aren't *completely* mission critical. To test upgrading, please update to the newer libdb on the 'from' release first (F24 or F25), then run an upgrade *with the updates- testing repository enabled*: dnf system-upgrade download --releasever=26 --enablerepo=updates-testing Or if you want to avoid potential issues with other updates-testing packages, create a side repository with only the libdb-5.3.28-21.fc26 update: https://bodhi.fedoraproject.org/updates/FEDORA-2017-a4c41ecc27 in it, and enable *that* repository during the upgrade. Please check that libdb-5.3.28-21.fc26 is listed in the set of packages to be upgraded before running the upgrade, to ensure your test is valid. To make sure the patch doesn't cause other problems, please just install the updated libdb on F24, F25 or F26 and go about your normal business - maybe test installing, removing and updating more packages than usual. One of the previous attempts to fix this bug would cause RPM database corruption when an RPM scriptlet called rpm itself, so we're trying to catch other issues of this nature. If you do run into any problems, please report them in the bug reports and/or in reply to this mail. Thanks very much! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
