https://qa.mandrakesoft.com/show_bug.cgi?id=759
------- Additional Comments From [EMAIL PROTECTED] 2003-02-14 16:03 ------- Someone had mentioned on the Cooker list to use skip.list as a work-around, so I guess they were wrong. :( It's just strange that I can go for weeks with no problem, and then some magic package comes along and causes this. Oh humm.... ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: REOPENED creation_date: description: I am pasting in the email I sent to the Cooker list as I have only received one response from MandrakeSoft employees so far. ------------------------------------------------------------- I noticed that urpmi now tries to figure out all the unresolved dependencies on your system just like how apt does. I think this is extremely annoying behavior and I wish I was disabled by default. Justification: I have an application, SuperFoo, installed. It has a dependency on IBM's Java Runtime Environment (JRE). I need to use Sun's JRE because IBM hasn't bothered to release one that likes gcc 3.2 yet. And I know from my usage that it works fine with Sun's JRE. SuperFoo is a proprietary application so I don't have the source for it. Having to repackage it every release to remove the stupid hard requirement on IBM-JDK is extremely annoying. So I can install SuperFoo with straight rpm -Uvh --nodeps. Life is good and I can use SuperFoo. Now being the good Cooker person that I am, I do 'urpmi --auto-select' to sync with the latest packages. The latest urpmi says "Hey, we have unresolved dependencies! I MUST uninstall SuperFoo!", even though SuperFoo has nothing to do with all the other packages that I will be updating. I hope you see where this is painful. Every time I want to update Cooker, it will try to uninstall SuperFoo even though there is no reason to. Previously I have bragged to Debian users that urpmi is smarter because it only concerns itself with the packages that are being installed/upgraded. Please tell me there is hope that urpmi can be made smart again? -------------------------------------------------------------- To this François Pons responded: Ok, I hope I will not hurt sensibility but urpmi doesn't care if unrelated dependencies are unresolved. *BUT* urpmi when resolving related dependencies (and related should be understanded in the very large part) it may add unresolved dependencies. -------------------------------------------------------------- So my question is why would this unrelated unresolved dependency be added? Or using the example from above, why does it want to remove SuperFoo which has an unresolved dependency on IBM-JDK even though nothing else that I am installing/upgrading has any requirement on IBM-JDK (or anything Java related for that matter). Thanks.
