I think there is a bug in VLC 1.1.11, and so I uninstalled it entirely, dependencies included, and selected vlc 1.1.9 from rpmdrake. But by doing so, rpmdrake says it also needs to install several dependencies, all for 1.1.11, instead of the dependencies for 1.1.9. This means I now have a mix of libraries for 1.1.9 and 1.1.11, which is probably not good. As discussed on IRC, selecting vlc in rpmdrake should require the exact same version for dependencies. Else it's a pain to downgrade as I'm trying to do right now.
Here is the output I get from rpmdrake when installing vlc 1.1.9: Les 5 paquetages suivants vont être installés : - libvlc5-1.1.11-0.1.mga1.tainted.i586 - libvlccore4-1.1.11-0.1.mga1.tainted.i586 - vlc-1.1.9-3.mga1.i586 - vlc-plugin-common-1.1.11-0.1.mga1.tainted.i586 - vlc-plugin-pulse-1.1.11-0.1.mga1.tainted.i586 So I chose 1.1.9 (not from tainted!), and it tries to install dependencies from 1.1.11 (from tainted!).
Note that tightening the requires in the main package, won't cause the lib packages to get uninstalled when you uninstall vlc; so vlc will be removed and when you try installing the older version you'll get: "The following package cannot be installed because it depends on packages that are older than the installed ones" so replacing a sticky situation with a somewhat less stick situation, at least the user will be warned there's something wrong... Of course this doesn't account for the tainted/core bit, but for that part, vlc from tainted will show up in the updates list when you update the system the next time.
What would be cool is if rpmdrake could remember which dependencies it installed, and asks the user if he wants to uninstall them too (assuming nothing else uses them). This would fix the problem you describe (and would also avoid having tons of useless installed RPM which are no longer needed because you removed an application).
(In reply to comment #3) > What would be cool is if rpmdrake could remember which dependencies it > installed, and asks the user if he wants to uninstall them too (assuming > nothing else uses them). This would fix the problem you describe (and would > also avoid having tons of useless installed RPM which are no longer needed > because you removed an application). That's what urpme --auto-orphans tries to do.
Assigning to vlc maintainer.
CC: (none) => stormiAssignee: bugsquad => shlomifSource RPM: (none) => vlc
(In reply to comment #1) > Here is the output I get from rpmdrake when installing vlc 1.1.9: > > Les 5 paquetages suivants vont être installés : > > - libvlc5-1.1.11-0.1.mga1.tainted.i586 > - libvlccore4-1.1.11-0.1.mga1.tainted.i586 > - vlc-1.1.9-3.mga1.i586 > - vlc-plugin-common-1.1.11-0.1.mga1.tainted.i586 > - vlc-plugin-pulse-1.1.11-0.1.mga1.tainted.i586 > > So I chose 1.1.9 (not from tainted!), and it tries to install dependencies from > 1.1.11 (from tainted!). That's strange. I see vlc-1.1.9 packages both in ftp://ftp.belnet.be/mirror/mageia/distrib/1/i586/media/tainted/release and ftp://ftp.belnet.be/mirror/mageia/distrib/1/i586/media/core/release . vlc-1.1.11 is in both ftp://ftp.belnet.be/mirror/mageia/distrib/1/i586/media/core/updates as well as ftp://ftp.belnet.be/mirror/mageia/distrib/1/i586/media/tainted/updates . Why don't you have the core/updates repository enabled?
Closing due to inactivity. I don't think it's a valid bug.
Status: NEW => RESOLVEDResolution: (none) => INVALID
It's a perfectly valid bug. Just see what I wrote in comment 0 and comment 1. rpmdrake selected the most recent version available, independently of whether I chose 1.1.9 or 1.1.11. I have all these repo enabled.
Status: RESOLVED => UNCONFIRMEDResolution: INVALID => (none)Ever confirmed: 1 => 0
(In reply to comment #8) > It's a perfectly valid bug. Just see what I wrote in comment 0 and comment 1. > rpmdrake selected the most recent version available, independently of whether I > chose 1.1.9 or 1.1.11. I have all these repo enabled. If you have all these repositories available, then I believe rpmdrake and urpmi should select the most recent version of VLC available and not assume you have downgraded to VLC-1.1.9 . If you do want to downgrade, then you're on your own. Please use the most recent version of VLC.
(In reply to comment #9) > If you have all these repositories available, then I believe rpmdrake and urpmi > should select the most recent version of VLC available and not assume you have > downgraded to VLC-1.1.9 . If you do want to downgrade, then you're on your own. > Please use the most recent version of VLC. I explained in bug 2267 why 1.1.11 was not acceptable, and if I select 1.1.9, then rpmdrake should satisfy this choice. I didn't downgrade anything, I simply chose 1.1.9 instead of 1.1.11.
Did vlc 1.1.12 resolve this one ?
(In reply to comment #11) > Did vlc 1.1.12 resolve this one ? I didn't try to reinstall 1.1.9.
I have try an indeed it's still present.
I still think it's a non-valid bug, as I explained.
(In reply to comment #11) > Did vlc 1.1.12 resolve this one ? This is not a vlc bug. It's due to rpmdrake displaying all versions of a package available in the enabled repositories, but no matter which is selected, only installing the version selected by urpmi, Either rpmdrake should only display the latest version available from enabled repositories, or rpmdrake and urpmi will have to be modified to allow selecting by version. Note that the most obvious solution of adding the --media parameter when selecting other then the latest version might invoke problems related to the infamous bug 2317. In my opinion, rpmdrake should either only display the latest available version for each package, or provide a clean method of downgrading to a prior version. The former is obviously much easier, but it means any user wanting to downgrade would have to do it manually, and add the packages to the skip.list.
CC: (none) => davidwhodgins
(In reply to comment #15) > (In reply to comment #11) > > Did vlc 1.1.12 resolve this one ? > > This is not a vlc bug. It's due to rpmdrake displaying all versions > of a package available in the enabled repositories, but no matter > which is selected, only installing the version selected by urpmi, > > Either rpmdrake should only display the latest version available > from enabled repositories, or rpmdrake and urpmi will have to be > modified to allow selecting by version. Note that the most obvious > solution of adding the --media parameter when selecting other then > the latest version might invoke problems related to the infamous > bug 2317. > > In my opinion, rpmdrake should either only display the latest > available version for each package, or provide a clean method > of downgrading to a prior version. The former is obviously much > easier, but it means any user wanting to downgrade would have > to do it manually, and add the packages to the skip.list. re-assigning to maintainer of rpmdrake and changing unconfirmed status to NEW
Status: UNCONFIRMED => NEWCC: (none) => marja11Assignee: shlomif => thierry.vignaudEver confirmed: 0 => 1Source RPM: vlc => rpmdrake
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
closing as this was on resolved in mga2 (rpmdrake only showing only the last version), and I guess nobody will backport the patch
Status: NEW => RESOLVEDResolution: (none) => FIXEDTarget Milestone: --- => Mageia 2
commit dc9950451a6c83815e2f680f9eaba6da31a18300 Author: Thierry Vignaud <thierry.vignaud@...> Date: Thu Jun 26 23:07:21 2014 +0200 Revert "(get_pkgs) only display latest updates, not all of them (mga#2258, mga#4534)" This reverts commit d600679cdaf402a0f97bbbd76e7fa04c06c5a37e. Rationale: it wreaks havoc (mga#12766) Conflicts: Rpmdrake/pkg.pm --- Commit Link: http://gitweb.mageia.org/software/rpmdrake/commit/?id=dc9950451a6c83815e2f680f9eaba6da31a18300 Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=4534 https://bugs.mageia.org/show_bug.cgi?id=12766 https://bugs.mageia.org/show_bug.cgi?id=2258
commit 235d51620b64f77632a697c0c93ba8a152cfaadd Author: Thierry Vignaud <thierry.vignaud@...> Date: Fri Jun 27 19:10:41 2014 +0200 Revert "Revert "(get_pkgs) only display latest updates, not all of them (mga#2258, mga#4534)"" This reverts commit dc9950451a6c83815e2f680f9eaba6da31a18300. Conflicts: NEWS --- Commit Link: http://gitweb.mageia.org/software/rpmdrake/commit/?id=235d51620b64f77632a697c0c93ba8a152cfaadd Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=2258 https://bugs.mageia.org/show_bug.cgi?id=4534