This works as I would expect it to.

My test case was htop I first removed it, installed it with apper, downgraded it with dnf, then upgraded it with the system-tray updater (im a KDE user)

Under all circumstances the file had the correct reason in /var/lib/dnf/yumdb/h/*/reason and as a result showed up under sudo dnf history userinstalled and was not wanted to be removed by sudo dnf autoremove

Sorry, meant to give karma as well after a copy-paste but forgot

works for me

seems to be working fine, including offline update. "userinstalled" flag is now correctly set.

Works great for me. PackageKit no longer marks installed packages for autoremove.

After carrying out a dnf --enablerepo="updates-testing" libhif the testcase criteria in the bug still failed, a dnf needs-restarting didn't show any processes needing a kick though (to be fair I didn't check lsof).

After a reboot of the system the test cases pass with installs by pkcon directly (or the command-not-found plugin) showing the correct user/dep reason in /var/lib/dnf

Unfortunately dnf history isn't displaying the results of packagekit actions, but at least the autoremove issue is solved by this update.

@jhogarth: This is not supposed to fix anything else than the bugs specified, so no, dnf history is not touched by packagekit. But autoremove issues are supposed to be fixed (not retroactively, though). And yes, you need to restart packagekit or reboot computer for the changes to take effect.

Looks good to me.

It seems that the autoremove issue is solved

Fixed the issue with dnf removing stuff installed with GNOME Software for me