https://qa.mandrakesoft.com/show_bug.cgi?id=759
[EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2003-02-13 20:57 ------- I hit this again. [root@tp screem-0.6.0]# urpmi --auto-select The following packages have to be removed for others to be upgraded: SameTime-client-1.51-19 (due to unsatisfied IBMJava2-SDK *) do you agree ? (Y/n) If I put SameTime-client in skip.list and it still didn't ignore it. I think * is an indication that something caused urpmi to look outside it's normal scope. Here is a list of the packages urpmi wants to upgrade this time: To satisfy dependencies, the following packages are going to be installed (41 MB): coreutils-4.5.7-1mdk.i586 coreutils-doc-4.5.7-1mdk.i586 drakconf-9.1-0.19mdk.i586 drakxtools-9.1-0.29mdk.i586 drakxtools-newt-9.1-0.29mdk.i586 glibc-2.3.1-8mdk.i586 glibc-devel-2.3.1-8mdk.i586 grpmi-9.1-6mdk.i586 harddrake-ui-9.1-0.29mdk.i586 ldconfig-2.3.1-8mdk.i586 libhermes1-1.3.2-8mdk.i586 libltdl3-1.4.3-1mdk.i586 libscrollkeeper0-0.3.12-2mdk.i586 libtool-1.4.3-1mdk.i586 mandrake_desk-9.1-1mdk.noarch perl-Crypt-SSLeay-0.49-1mdk.i586 rpmdrake-2.1-6mdk.i586 scrollkeeper-0.3.12-2mdk.i586 suspend-scripts-1.0-1mdk.noarch timezone-2.3.1-8mdk.i586 The only thing that jumps out at me is that suspend-scripts is a new package which probably obsoletes apm-scripts. ------- 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.