Ah, I must have misunderstood your reuqest then. Sorry for that. Generally speaking an update entails *removing* one version of a package and *installing* a newer version of the same package. There is nothing that functionally sets apart an update from any other package installation or removal, which is why they all eventually get piped through the same dbus call. Technically of course one could sort of differentiate between install/remove and update on a very high level, but to a very limited extent which simply put is: you don't authenticate for as long as a the whole batch of available updates can be cleanly updated. As soon as an update requires any sort of interaction you need to authenticate to do anything. So this is pretty much not useful unless you can garuntee that updates never require the removal or installation of a new package which we cannot.
Also, with regards to security we do not ever update automatically in background unless the system was configured to do so and making this configuration in turn again requires an admin user to authenticate by password. So, I fear while it might be technically possible the cost-to-benefit ratio is not terrible good for such a feature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346234 Title: Allow running updates without authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqapt/+bug/1346234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
