Re: Testing request: libdb and F26 upgrades

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2017-06-05 at 12:34 +0200, Kamil Paral wrote:
> On Sun, Jun 4, 2017 at 6:44 PM, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx>
> wrote:
> 
> > 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.
> > 
> 
> I updated F25 to libdb-5.3.28-21.fc25 and while dnf worked fine,
> gnome-software stopped working and complained about a failure to open rpmdb:
> 
> Jun 05 11:51:33 f25 packagekitd[1040]: error: db5 error(5) from
> dbenv->open: Input/output error
> Jun 05 11:51:33 f25 packagekitd[1040]: error: cannot open Packages index
> using db5 - Input/output error (5)
> Jun 05 11:51:33 f25 packagekitd[1040]: error: cannot open Packages database
> in
> Jun 05 11:51:33 f25 packagekitd[1040]: BDB1537 //var/lib/rpm/__db.001:
> unable to read system-memory information: Input/output error
> Jun 05 11:51:33 f25 PackageKit[1040]: resolve transaction /190_aadbbbbd
> from uid 1000 finished with failed after 39ms
> Jun 05 11:51:33 f25 gnome-software-service.desktop[1475]: 09:51:33:0558 Gs
> failed to call gs_plugin_refine on packagekit-refine: Failed to load system
> repo: failed loading RPMDB
> 
> The issue disappeared after a reboot. Not sure whether that's
> expected/wanted.

Nope, this is one of those updates where everything should work...can
you add a comment to one of the bugs about that, and see what the devs
say? 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@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux