On Wed, 2018-09-12 at 06:27 +0000, Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Sep 11, 2018 at 12:26:09PM -0700, Adam Williamson wrote: > > Hi folks! > > > > Around the time DNF 3 landed in Rawhide (hence F29), we had quite a few > > folks on these lists reporting issues, including crasher bugs. Many of > > these seemed somehow related to the DNF history database. They also > > were not easy to isolate and fix. > > > > We're now close to the F29 Beta release, but we don't have a great > > sense of how many people are still having these problems with DNF 3.2 > > or 3.3. > > > > Can anyone who is still struggling with DNF crashes on *basic* > > operations on F29 or Rawhide please reply, and provide a few details on > > what you're seeing and any workarounds or fixes you've found? > > I filed https://bugzilla.redhat.com/show_bug.cgi?id=1627694 yesterday. > The gist is that dnf stopped having locking around the rpm operation, > so it'll fail if two operations are invoked concurrently. Before it'd > very nicely do the downloads in parallel and then run the actual installations > sequentially. I think this is a huge regression in usability. Thanks. Doesn't really look like a Beta blocker, though. > I also saw some "TransactionItem not found" messages, but this has already > been reported extensively. On what operation? We have: https://bugzilla.redhat.com/show_bug.cgi?id=1625259 for encountering them on downgrade or 'history undo' type operations. If you hit one on upgrade or install, that'd be worse. Thanks! -- 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 Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
