Bug 367057

Don, apart from the problem of there being an undesired solver run, maybe you could make your life easier using "checkinstall" to make real RPMs from your freshly compiled Apache (and whatever other packages you build yourself) and then create a real repository with those RPMs? That should integrate smoothly with the online update.

Stefan,

Thanks,

I do.  In general, in order to increase performance and reduce attack vectors, I only compile with the very minimum options necessary to run the applications in my environment.  SuSE tends to compile with the maximum reasonable set for the widest compatibility.

Previous verify runs ran cleanly, but this update modified one of the dependent packages to require a new feature that was available in the SuSE apache, but not in mine.  But instead of giving a message so that I could stop the update, investigate, recompile my version etc;  it just 'updated' my version to the SuSE version.

With the second example, the problem was not that I was using packages installed outside of the RPM system, but that I had uninstalled a number of packages that were install with the 'minimal system install', but that I did not want on my system.  The update logic decided that since I was missing part of the 'package group' and because there were several conflicts, that it would just go ahead and resolve the conflicts by deleting the rest of the group -- which was, basically, the entire operating system.

For example, I uninstalled required libraries that, although required for some applications, were for features that I will never use, and, in fact, do not want to be used.  The only risk should be a potential program crash if that function somehow managed to get called, not that the update logic would unilaterly uninstall the applicaton. 

I suggest to ask user, inform about the situation with the pacakgemanager-related updates. If user decides to continue, just apply the result from the selector, otherwise go back to the selector asking user to review the problem.

OK, now, please help me someone (adding Martina) with the popup text informing user about the situation. First proposal:

"There are patches for package management available requiring restart of YaST.
They should be installed in the first place and all other patches after the rest
art.

You selected some other patches to be installed now.
                                                                                Continue with installing user selection?"

[Continue][Cancel]

Clicking Cancel opens package selector again. Hey, maybe the whole check and the warning should go inside the package selector, shouldn't it?

The wording should not suggest that 'I' selected the packages but rather that the system automatically selected them.

There is already similar wording when you are using the software management function instead of the online update:

Automatic Changes
In addition to your manual selections, the following packages have been changed to resolve dependencies:

If I do not like the automatic changes, I can taboo them.

(In reply to comment #17 from Don Hughes)
> The wording should not suggest that 'I' selected the packages but rather that
> the system automatically selected them.

No, this is intentional. Such popup will be shown exactly when _user_ selected something different than proposed.

I know this is different to your original problem, it is actually differet part of the process. There were several private comments until now where we were discussing this.

Done in yast2-online-update-2.16.12.