Description of problem:
I started "dnf update" command and then realized I wanted to change something. I quickly hit Ctrl+C wishing to interrupt it while downloading packages. I wasn't quick enough and dnf started installing before I pressed it. Three packages were updated in the meantime and then dnf responded to Ctrl+C and interrupted the operation. The result is that my system was immediately in inconsistent state - some packages were duplicated (newer package versions were installed but the older ones were not yet removed). I was able to deal with that but it could've been much worse. For example if I hit Ctrl+C, perhaps by accident, in the middle of the operation, when tens of operations were already performed.

Why does dnf respond to Ctrl+C during critical operations? It makes sense to respond to it during depsolving, downloading, etc. But I believe it should not handle the signal during installation.

Version-Release number of selected component (if applicable):
dnf-2.6.3-1.fc26.noarch