Mailinglist Archive: opensuse-factory (753 mails)

< Previous Next >
Re: Fwd: Re: [opensuse-factory] Help Apper to survive (12.2)
  • From: Sven Burmeister <sven.burmeister@xxxxxxx>
  • Date: Mon, 20 Aug 2012 17:59:33 +0200
  • Message-id: <1361449.FjVuNY1rdA@linux-ly0d>
Am Montag, 20. August 2012, 17:24:56 schrieb Carlos E. R.:
It is a combination of blame between one click and apper - and by apper I
include all the frontends to package kit however they are called.

1) The user activates many repos, some duplicated, as a result of using one
click. 2) The user installs mixed updates from any repos, as a result of
using apper.

The result of this combination is a broken system.

That only confirms that you can break your system with zypper up or YaST as
well and there is nothing special to apper or packagekit. In fact at least
apper makes it harder to break dependencies than yast or zypper because you
get no dialogue that allows you to chose the dep breaking. And it confirms
that breaking the system is related to showing all no-vendor-change updates or
not, i.e. a back-end setting rather than a bug.

If packagekit and hence apper is told to show all no-vendor-change updates and
it does so, they work perfectly fine. How to set the back-end has nothing to
with packagekit etc. but is a simple matter of taking a decision. It is
exactly the same as the default settings in zypp's conf.

Another problem in multiuser environments is that not all users should have
the applet running, nor should they be prompted to do updates. This is a
thing for the admin user to decide. So it should be possible to limit which
users run it, perhaps by adjusting the permissions of the applets.

That argument misses the point. Simply because
a) most of the times there is no admin and not more than one user per system,
i.e. typical home user.
b) if there is an admin he already has the means to disable/configure via
policykit etc. per user.

To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups