Bug 114465 - YaST2 marks RPMs from not selected base selections for deletion
Summary: YaST2 marks RPMs from not selected base selections for deletion
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Beta 4
Hardware: Other All
: P5 - None : Major
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-31 16:22 UTC by Thorsten Kukuk
Modified: 2006-04-06 13:53 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Yast2 logfiles and conflicts.txt (53.48 KB, application/x-gzip)
2005-08-31 16:23 UTC, Thorsten Kukuk 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Kukuk 2005-08-31 16:22:50 UTC 
What I did:
Install any SuSE Linux Distribution (I tested 9.3 and 10.0Beta3) with only
Minimal+X11, but add RPMs from the KDE and other selections.

YaST2 detects the following selections as installed during the update later:
Minimal+X11
Kde-Desktop
Office
LDAP
C/C++ development

Which looks nearly like what I choose manually.

Try to make a normal update to SL10.0Beta4, don't change any defaults! (Yes,
normally I always change defaults, but this time not). You will get a bunch
of conflicts.

It seems that YaST2 marks this installed RPMs for deletion, which are part
of the default base selection, but not of Minimal+X11:
autofs, bootsplah*, compat, dos2unix,  dosfstools, fetchmail, filters,
ghostscript-x11 and much more.
Comment 1 Thorsten Kukuk 2005-08-31 16:23:31 UTC 
Created attachment 48337 [details]
Yast2 logfiles and conflicts.txt
Comment 3 Andreas Jaeger 2005-09-01 13:19:12 UTC 
Why are those files deleted at all?  This should not happen.
Comment 4 Jiri Srain 2005-09-02 08:20:36 UTC 
I have no clue why they got marked to be deleted. I even couldn't reproduce 
the bug. 
 
Michael, can you hint me from the package manager's logs?
Comment 5 Michael Andres 2005-09-12 11:54:08 UTC 
If a selection is deleted, all the packages in the selection (which are not
mentioned in some other installed selection) are deleted. What would you expect
to happen, if a selection is tagged to delete?

The conflicts arise, because the solver is not allowed to undo changes made by
YaST or user. The selection handling code tags the packages to delete, so the
solver is not allowed to automaticaly revert this. 

--
It's not that simple to change, beacause we can't simply allow the solver to
overrule any application_delete. We had to introduce a 2nd level of
application_requests. One for modules, and one for selections. Then we could
allow the solver to overrule selection requests, but not request from modules.

But evaluation of request had to be changed as well, because once the solver
would overrule a selection request, the information that a selection wants the
package to be deleted is lost.
Comment 6 Christoph Thiel 2006-04-06 13:53:47 UTC 
Let's close this bug and reopen it, if this is happening with 10.1 & libzypp.