Mailinglist Archive: opensuse-factory (753 mails)

< Previous Next >
Re: Fwd: Re: [opensuse-factory] Help Apper to survive (12.2)
Hash: SHA1

On 2012-08-20 17:10, Sven Burmeister wrote:
Am Montag, 20. August 2012, 07:55:44 schrieb DenverD:

then they show up in the forums with blood-shot eyes and 10, 15 or 25
enabled and
refreshed repos that apper/package kit is serving death from...asking why
they can no
longer boot, or . . .

And its not apper's fault.

So what you want is to revert the decision to show all non-vendor-change
updates. After
that you will have the request to show them again. Once you allow to add
third party repos
they might also contain security-relevant updates, hence showing them does
make some

The only solution I see is to provide a GUI-option to switch the behaviour.

If you want to prevent users from screwing-up their system apper is not the
piece of
software to look at. You will have to restrict one-clicks-installs, zypper up
and YaST's
non-YOU update functionality.

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
2) The user installs mixed updates from any repos, as a result of using apper.

The result of this combination is a broken system.

Another problem in multiuser environments is that not all users should have the
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.

- --
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 "Asparagus" at Telcontar)
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla -

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

< Previous Next >