https://bugzilla.novell.com/show_bug.cgi?id=685890 https://bugzilla.novell.com/show_bug.cgi?id=685890#c7 --- Comment #7 from Daniel Pecka <nettezzaumanaa@gmail.com> 2011-04-08 12:47:49 UTC --- okay, reproduced on 11.3 with added repo-oss from 11.4: # zypper lr | grep oss 7 | oss114 | oss114 | Yes | No 9 | repo-non-oss | openSUSE-11.3-Non-Oss | Yes | Yes 10 | repo-oss | repo-oss | Yes | No # zypper -vv up .blahblah.. 1187 packages to upgrade, 155 new, 34 to remove, 2 to change arch. Overall download size: 964.3 MiB. After the operation, additional 385.5 MiB will be used. Continue? [y/n/?] (y): n ^^ but i think that's the incorrect behaviour and shuld be changed. Some repos like packman don't provide repository with separate updates so up() has big sense there because it's desirable to check in repo where particular package is from if there is higher version. this could happen for buildservice i suppose. my proposals are: - change up() behaviour to handle as listed above with vendors/repos - chain somehow in patch() repo+his_update_repochild eg you'll be able then have added more repos from one vendor providing similar content and theirs updates like: repo-oss-$foo, update-$foo repo-oss-$bar, update-$bar regards, daniel -- 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.