http://qa.mandrakesoft.com/show_bug.cgi?id=4013
------- Additional Comments From [EMAIL PROTECTED] 2003-20-06 01:53 ------- Like in comment #1, it is very hard to have an exact testcase, as it appears from time to time. Maybe a little correction, though... After I hit Cancel button, it is not any package that shows up this "stale" dependencies, but only if I click on a package that needs a dependency (be it different one) as well. I run into this problem when *updating* packages (from Cooker), I am not sure about install. Example: 1. I select package A (installed) for update, which requires newer version of package B (installed). A prompt saying I need a newer version of package B displays, I click Cancel. 2. Now I want to update a package C for which I meet all conditions. OK, works, I can select it. 3. Now I want to update a package D that requires a newer version of package E (installed). If I went through step one, a dialog pops up telling me that I need a newer version of both E and B, which is wrong. If I either restart rpmdrake or install already selected packages, the list of dependencies gets reset (cleared) and I can perform step 3 as expected, i.e. it tells me that I need a newer version of package E only, as expected. It is an obscure bug, I know, but very annoying. I just updated to the latest Cooker (rpmdrake, perl-URPMI, urpmi), even newer version than in your comment, but now the package update selection is even more funny, which is so obvious that it will be fixed in the next development release :-) -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- 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: NEEDINFO creation_date: description: When I choose a package to update in rpmdrake, and some other packages need to be installed as well, a popup window describing these packages will pop up. If I select Cancel (I don't want to install these), the original package I chose in rpmdrake is unselected as well. So far so good. >From this time, though, ANY package I select for update needs THE SAME DEPENDENCIES as well, regardless the package. The dependencies stay in memory, somehow, and will not get cleared until I actually install something successfully or restart rpmdrake.
