https://bugs.kde.org/show_bug.cgi?id=488388
--- Comment #3 from Adam Williamson <ad...@happyassassin.net> --- On a quick look, it seems like PK does actually provide an interface for this which g-s is using. g-s sets an `untrusted_question` attribute on some class (there is too much obfuscation for me to bother figuring out what kind of class it is exactly, god I hate C): https://gitlab.gnome.org/GNOME/gnome-software/-/blob/4ca259f74911d39ccf5c93b4c0e323b62819623d/plugins/packagekit/gs-packagekit-task.c#L194 it seems like the other end of that isn't in gnome-software, but in PackageKit, unless I'm misreading: see https://github.com/PackageKit/PackageKit/blob/e5df9e89e5841f102cd1f5587aaf987083e32562/lib/packagekit-glib2/pk-task.c#L881 . It occurred to me you can get the "just go ahead" behaviour by implementing a "question" callback which isn't interactive, it just says everything's fine, and sure enough, there seems to be an implementation within PK itself which does this: https://github.com/PackageKit/PackageKit/blob/e5df9e89e5841f102cd1f5587aaf987083e32562/lib/packagekit-glib2/pk-task-wrapper.c#L50 . I don't know if it's possible to do this *only* in the case that the repo config has `gpgcheck=0`, though, or something like that. I don't know the exact contours of when PackageKit would trigger this 'untrusted_question' mechanism vs doing something else. -- You are receiving this mail because: You are watching all bug changes.
