Description of problem: rpmdrake shows only the i586 one of virt-manager, hiding the x86_64 one. urpmi correctly shows the x86_64 one that will be installed. Steps to Reproduce: 1. in menu, click add/remove programs 2. search for virt-manager 3. see only the i586 one 4. in a terminal, urpmq -i virt-manager 5. it correctly shows the x86_64 one
It is only when you search a package ? not when you browser with the categories ? only with this one ?
Assignee: bugsquad => thierry.vignaud
browsing is similar. (i noted that my filter was already set to ALL, ALL) i used rpmdrake to look at emulation tools to try and find again the virt-manager which i had installed already (the x86_64), it just wasn't there. what i did notice for instance is: virtualbox i586 (not installed) virtualbox-guest-additions x86_64 (installed) i donno if there's any order to this, i do see alot of i586, but in emulation, i guess it's only normal... dynamips is for example listed as x86_64 mednafen too mupen64plus too virtualbox-guest-additions x86_64 (installed) vpcs wine64 wine64-gecko those are the only ones in x86_64 in the emulation section, all the others are noarch or i586 some of these are likely only 64bit, maybe even all of these?
education section is a good example, as it has none from x86_64 listed. only using core/core32/nonfree/tainted release, no testing
(In reply to comment #1) > It is only when you search a package ? bind is another package which does not show x86_64 as a selection, only i586 is selectable. urpmi bind will install the bind-9.9.0-5.mga2.x86_64.rpm and rpmdrake will then show the x86_64 instead of the i586 package.
CC: (none) => junk_no_spamKeywords: (none) => USABILITY
Priority: Normal => release_blockerSummary: rpmdrake shows only i586 version of virt-manager package => rpmdrake shows only i586 version of packages
CC: (none) => jaanus.ojangu
'oxygen-gtk-1.2.2-2.mga2' and 'oxygen-gtk3-1.0.2-2.mga2', which got installed by default, exhibit the same behaviour (after removal with rpmdrake one have to use the terminal to install them again because the 64 bit versions of those will not reappear as available to install in rpmdrake). The associated libraries are available again in rpmdrake after removal, though.
CC: (none) => gruescubogdan
*** Bug 5111 has been marked as a duplicate of this bug. ***
CC: (none) => mwozniak00
Status: NEW => ASSIGNED
Fixed in git
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
there is a git? i thought soft was in svn? is there some doc regarding this? and also, personally, i prefer bugs to be kept open until confirmed fixed and pushed on BS...
in my git-svn. which I then dcommit-ed into svn.
oic, sorry to bother you about it
No problem. You can "+1" my freeze push request btw :-)
i guess that's not necessary anymore...