https://bugzilla.novell.com/show_bug.cgi?id=704123 https://bugzilla.novell.com/show_bug.cgi?id=704123#c3 Haro de Grauw <bin@harodegrauw.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bin@harodegrauw.net --- Comment #3 from Haro de Grauw <bin@harodegrauw.net> 2011-09-24 22:39:36 UTC --- Hi, I also noticed the same thing. Example situation today: Currently installed: timidity 2.13.2-266.1-x86_64 vendor openSUSE Available update: timidity 2.13.2-266.1-x64_46 vendor openSUSE-Education Available update: timidity 2.13.2-266.1-x64_46 vendor obs://build........ All repositories at default priority (99). When I click "All packages --> Update if newer version available", the version from BuildService is selected, with vendor change. Option "Allow vendor change" is unchecked in YaST and untouched in zypp.conf. When running "zypper list-updates" the same update is also selected so it appears to be a zypper problem. Other situation: Currently installed: frozen-bubble 2.2.0-11.1-x86_64 vendor openSUSE Available update repo#1 frozen-bubble 2.2.0-26.1-x86_64 vendor obs://build.... Available update repo#2 frozen-bubble 2.2.0-26.1-x86_64 vendor obs://build.... In this case, the same update package (wrong vendor, but twice the SAME vendor) is available from two different repositories. Neither YaST nor zypper propose the update, so the problem seems to arise specifically when an update is available from two distinct (wrong) VENDORS. Hope this helps, greetings to all three. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.