[Rpm-maint] [rpm-software-management/rpm] make sure not to dereference NULL pointer (#106)

proyvind notifications at github.com
Wed Dec 7 13:31:29 UTC 2016

yes, most probably caused by different trigger implementation, gracefully handling it when upgrading to new package version. The correct file action decission could only be invoked correctly by supporting these, the omission of triggers executed in favour of rpm not segfaulting if trying to remove the package related to an upgrade etc.

So coming from the rpm5 environment, only to encounter this and preferring a non-fscked rpm.org environment after install from rpm5.

So the NULL check that prevents segfault rather than just omitting unsupported stuff at initial install from rpmm5 environment is much preferred.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20161207/810aa083/attachment.html>

More information about the Rpm-maint mailing list