Description of problem: I have apache installed as well as apache-modules version 2.2.17-5.2mga1. While attempting to apache-mod_userdir. After being presented with three options, each the same with different version numbers I first tried to select select version 2.2.17-5.1mga. A pop-up error dialog comes up stating: Sorry, the following package cannot be selected: - apache-mod_userdir-2.2.17-5.1.mga1.i586 No further reason is given. If I try to select version 2.2.17-5.2.mga1.i586 I get a pop-up error with the following message: Sorry, the following package cannot be selected: - apache-mode_userdir-2.2.17-5.2.mga1.i586 (due to unsatisfied apache-modules[==2.217-5.2.mga1]) On the other hand if I quit rpmdrake and attempt to select version 2.2.17-5.2.mga1.i586 without first selecting the wrong version of version of the package then I may select it and install it. That ends the bug report. Now for the feature request: Notably "urpmi apache-mod_userdir" simply selects the correct package and installs it. It would be nice if the gui knew (or gave some hint, such as highlighting) what urpmi would select when several versions are available. Version-Release number of selected component (if applicable): 5.26.10-1.mga1.src.rpm How reproducible: Very easy to reproduce the error. Steps to Reproduce: 1. urpme apache-mod_userdir if already installed. 2. run rpmdrake 3. search userdir 4. Attempt to select the wrong package. 5. Dismiss the Error dialog. 6. Attempt to select correct package and your presented with an error dialog.
apache-mode_userdir-2.2.17-5.2.mga1.i586 (due to unsatisfied apache-modules[==2.217-5.2.mga1] Looks like a missing dot in the apache-modules version requirement
That maybe a typo on my part but I am not sure, for various reasons I had to type the error messages by hand.
Yes, you could be right, Sophie shows it as apache-modules = 2.2.17-5.2.mga1 http://sophie.zarb.org/distrib/Mageia/1/i586/media/core-updates/by-pkgid/91bcc03faaa6d4b2045a6e4b182eba47/deps What is the result of.. rpm -qa | grep apache-modules
This could be a bug in rpmdrake. $ rpm -qa | grep apache-modules apache-modules-2.2.17-5.2.mga1 Clicking to install apache-mode_userdir-2.2.17-5.2.mga1 is no problem. If you first click on apache-mode_userdir-2.2.17-5.1.mga1 then it gives an error.. Sorry, the following package cannot be selected: - apache-mod_userdir-2.2.17-5.1.mga1.i586 Which is correct. If you then try to install apache-mode_userdir-2.2.17-5.2.mga1 it gives a similar error.. Sorry, the following package cannot be selected: - apache-mod_userdir-2.2.17-5.2.mga1.i586 (due to unsatisfied apache-modules[== 2.2.17-5.2.mga1]) So this doesn't appear to be anything to do with apache but more to do with rpmdrake.
copy/paste errors in comment 4 Should be apache-mod_userdir not apache-mode_userdir.
CC: (none) => alien, thierry.vignaud
CC: (none) => eeeemail
Reply to Comment #3... The result is: [nmichalo@localhost Math]$ rpm -qa | grep apache-modules apache-modules-2.2.17-5.2.mga1
can this be just an out of date hdlist? in any case, i don't think this is apache related...
CC: alien => (none)
Problem still there, and indeed not apache related I use LibreOffice 3.3.3.1-0.1.mga1 I can select libreoffice-help-nn-3.3.3.1 without any problem. After deselecting that package and choosing libreoffice-help-nn-3.3.2.2, I get: > Sorry, the following package cannot be selected: > - libreoffice-help-nn-3.3.2.2-14.mga1.x86_64. Which is correct, of course. Deselecting that one, and selecting version 3.3.3.1 again, now gives: > Sorry, the following package cannot be selected: > - libreoffice-help-nn-3.3.3.1-0.1.mga1.x86_64 > (due to unsatisfied libreoffice-core[== 3.3.3.1-0.1.mga1]) assigning to maintainer
CC: (none) => marja11Assignee: bugsquad => thierry.vignaud
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
I think rpmdrake in mga2 only shows the latest update so this may not affect it.
yes closing as wontfix, since I guess nobody will backport the patch to 1.
Status: NEW => RESOLVEDResolution: (none) => WONTFIXTarget Milestone: --- => Mageia 2