http://bugzilla.novell.com/show_bug.cgi?id=544524
User bitdealer@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=544524#c5
Stephan Kleine
we have the Vendor and the key domain bind together since some weeks. Means the vendor is set based on where the key comes from.
Right. That improves the situation compared to one vendor for all repositories but still is far from perfect cause of zypps retarded package handline that relies on vendors.
If you want to create bugs, than please assign them to the project owners.
The bug is, IMHO, the current configuration of OBS that uses the same key / vendor for more than one repository which then makes it impossible to say "I want package X from repo A but not from B" if A & B use the same key / vendor. Also, do you really think that filing bugs against most of the non home repos so their owners request an unique key makes more sense than simply switching some default config for newly created projects and then iterating over the project tree to change it for existing ones? I humbly dare to disagree. Last but not least I fail to see what your problem might be with using unique keys per repository? You have to accept it once per key (which costs like 2 seconds more time) but therefore you have the peace of mind that your package isn't switched to some random other repository that happens to use the same key in which another, newer, version might show up that you do NOT want to install. So, what problem do you see with using unique keys per repository? As in what prevents your from switching over from the current setup to unique keys to prevent zypps vendor stickiness from screwing one over? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.