-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Andres wrote:
On Wednesday 01 April 2009 19:48:05 Elmar Stellnberger wrote:
You're not getting all the bug reports like "zypper dup is downgrading all my packman packages to opensuse"... ... but a well downgraded system will work better and contain fewer errors! Of course, that should not happen. When selecting a different than the standard installation source when installing via YaST the packages should become locked in order to be updated from the same source only. Is this not the way things work?
There's a slight difference between zypper up and zypper dup
Assume: priority(packman) < priority(openSUSE)
'up' tries to update installed packages with respect to the packages architecture and vendor. An already installed packman package will stay packman, but it will not migrate installed openSUSE packages to packman, nor will it use packman for new packages also available in openSUSE.
'dup' is free to change architecture and vendor, and even able to dowgrade packages. It will try to adjust all packages according to the repository priorities. Thus and already installed packman package may even be downgraded to openSUSE.
(mls may correct me if this is not exact)
There should not be any problem in continually drawing a user defined set of packages from another possibly lower prioritized source like Packman?
Unless you use 'zypper dup'. And maybe most trouble originates from this.
If you want to follow some development, like KDE4, people assign a high priority and use 'zypper dup', because it will bring in all the KDE4 packages.
But unfortunately 'zypper dup' may also remove packages from low priority repos. So 'dup' is not exactly what you want, but all you have.
Maybe 'zypper dup' should be deprecated and replaced by some command that simply 'dup's one repo:
zypper follow-repo KDE4 // raise KDE4 prio and update the packages.
As per earlier discussion, i plan to add --from <repo> option to several commands, including dup. zypper dup --from repo1 --from repo2 ... would make a dup on those repos, while still having the rest of the repos loaded to satisfy dependencies. OTOH, the existing --repo option only loads the given repos and disregards the rest completely (which works, as long as you don't need to satisfy deps from the other repos). - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAknUs3wACgkQgEhGpmN+6QG9nQCdGC/Y6qKda75Vwuz04H8zU9f6 BWUAn0k/BGXnJ/Cnmgi0O3KbhQGAYire =rltl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org