So... rpmtsCheck() should be performed once with the transaction lock held, and
additionally we should check that conditions haven't otherwise changed in the
meanwhile. Including but not limited to packages that are to be erased didn't
go away.
Getting it all done and right is a non-trivial thing, but we could start with a
large hammer that flags the transaction invalid if *anything* in the rpmdb
changes between creation and running the set.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1214#issuecomment-637394018
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
