Bug 544466

I think zypp should not report locked patches as needed patches.

Doable if the applet refers to ui::Selectable::isNeeded(). Thomas?

The applet doesn't directly use libzypp. As far as I know zypper reports only needed patches in its xml output. Perhaps packagekitzypp generates the list in a different way.

Hello,

some more informations, maybe they are helpful:

I use KDE3, but kupdateapplet from KDE4 (since there is no version for KDE3?)
I had the following packages installed:
- kde4-kupdateapplet-0.8.34-2.1
- kde4-kupdateapplet-packagekit-0.8.34-2.1

I now installed also kde4-kupdateapplet-zypp-0.8.34-2.1 and changed the backend in the configuration of kupdateapplet to ZYpp-Modul (instead of PackageKit-Modul).
But then I have troubles when I use my regular user (message like "applet error: ...  execute as root 'zypper refresh'" appears and nothing works) and with user root it's the same problem as with PackageKit-Modul.

I don't now much about the kupdateapplet. Anyway, the error message tells that the repositories metadata on the server have changed. Most probably because new packages and/or patches are available. Those new metadata have to be downloaded, but this can not be done as 'ordinary' user.

@Peter: Until the applet does it automatically, you had to login as 'root' and 
call 'zypper refresh' to update the metadata. This should make the error disappear, but it does not solve the taboo-patch-problem. 

@Thomas: It looks like the applet does not invoke zypper as 'root'. This is nothing lzypper/libzypp can fix. Maybe you can help here?

Hello Michael,

it makes no big difference when I use kupdateapplet as root or normal user.

When I use the PackageKit-Modul, I have to login as root or give the root password when I start to install the patches and then I have the taboo-patch-problem.

When I use the ZYpp-Modul, it's not possible to use a normal user (then I have the "applet error") and when I login as root, it's then the taboo-patch-problem.

So the result is, it's possible for me to install patches but the taboo-patch-problem still persists.

Peter, this is known bug when using the zypper (ZYpp-Modul) backend (bug 420606). But from your report it seems the packagekit backend has the same problem. So this should be fixed at the zypp implementation for the packagekit.

@Scott: I suppose this has to be fixed in PackageKit: backend/zypp-utils.cpp:
  ...
   // check if patch is needed 
   if((*it)->candidateObj ().isRelevant() 
      && !((*it)->candidateObj ().isSatisfied())) {


1) Minor: Broken, satisfied and !relevant are mutual exclusive. And you can directly ask the Selectable (no need to pick the candidate first):

   // check if patch is needed
   if ( (*it)->isBroken() ) {


2) That's probably also the location where to exclude locked patches:

   // check if patch is needed
   if ( (*it)->isBroken() && ! (*it)->status() == zypp::ui::S_Taboo ) {

Hello,

Just a short 'update'.
I upgraded now to openSUSE 11.2, but it's still the same behavior like above.
So I changed product and component of the bug (hope this isn't a bad idea...)

Cheers

Peter

*** Bug 460972 has been marked as a duplicate of this bug. ***

In openSUSE 11.3, the update applet still tries to update locked packages (i.
e. installed packages that are marked as protected in Yast Software Management)
but marking patches as taboo in Yast Online Update works (patches marked as
taboo are not shown in the update applet).

As I understand, this means that each time a new version appears in the update
repository, the user must decide whether to accept the update even if s/he
refused the previous version update. Maybe this is good enough because a new
update might not have a problem that was present in a previous update.

It might be a good idea to add an option to update applet GUI to let some
updates be disabled (i. e. marked as taboo), so that the user does not have to
figure out that s/he has to mark the update as taboo in Yast Online Update. (In
case of critical updates, the applet might give some warning dialog asking
whether you really want to block the update.)

*** Bug 570357 has been marked as a duplicate of this bug. ***

Kupdateapplet was removed from current releases.