https://bugzilla.novell.com/show_bug.cgi?id=734152 https://bugzilla.novell.com/show_bug.cgi?id=734152#c1 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Severity|Normal |Enhancement --- Comment #1 from Michael Andres 2011-12-02 13:04:16 CET --- Yes. Ideally we could remember the original repo a package came from as a custom header entry in the rpm database. But rpm does not support something like this. So we don't know easily where a package was installed from. For installed packages zypper shows 'System Packages', unless the very same version is available in some other repo. But 'System Packages' does not mean the package is discontinued or orphaned. It just says that the exact same version is no longer available in any other repo. Discontinued or orphaned means that there also is also no update candidate in any other repo. I'm keeping this as request to enhance guessing of an installed packages origin. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=734152 https://bugzilla.novell.com/show_bug.cgi?id=734152#c3 --- Comment #3 from Michael Andres 2011-12-05 16:51:35 CET --- - If you want to install a specific version of a package you can call: 'zypper install [--force] ' 'zypper install --force zypper-1.5.3-3.2.x86_64' or 'zypper install [--force] --from <repo> <package>'

i don't how it's internally resolved at this moment in libzypp but zypper apparently recognizes a source repository of particular package, or isn't it

An 'update candidate' is a package with same arch, same vendor and higher version than the installed one. 'vendor' is different from 'repository'. The vendor is a string in the rpm package header, filled in by the person/institution who built the package. While a repo is just a collection of packages, often but not necessarily all from the same vendor. No matter to which repos a package is copied, the package vendor will always stay the same. The vendor protection assures that packages installed from vendor e.g. obs://build.opensuse.org/KDE are updated by packages from the same vendor only. No matter which repos or media are used to distribute the package. 'zypper dup' and 'zypper dup --from $repo' are the intended commands to allow switching from one vendor to another by softly enforcing the use of packages provided by a specific $repo. There is also a way to 'allow' vendor changes for commands like 'zypper up'. Actually you do not allow vendor changes, but you can define which vendor strings should be treated as 'the same vendor'. (see also http://doc.opensuse.org/projects/libzypp/HEAD/pg_zypp-solv-vendorchange.html) A vendors.d entry like vendors = suse,opensuse,obs://build.opensuse.org/KDE would allow opensuse and obs://build.opensuse.org/KDE packages to replace each other without considering this being a vendor change. -- 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.