[zypp-devel] New Resolver::addUpgradeRepo to perform a dist upgrade restricted to certain repositories.
JFYI: libzypp-6.13.0 Resolver::addUpgradeRepo to perform a dist upgrade restricted to one (or more, if called repeatedly) repository. This should be suitable for zypper dup --repo foo (or --name foo) -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
hi,
On Mon, Aug 3, 2009 at 9:52 AM, Michael Andres
JFYI: libzypp-6.13.0 Resolver::addUpgradeRepo to perform a dist upgrade restricted to one (or more, if called repeatedly) repository.
This should be suitable for
zypper dup --repo foo (or --name foo)
i thought 'dup' was to be across all enabled repos ... i'm unclear as to how 'dup' restricted to a given repo is, then, different than 'up' restricted to a particular repo. can you perhaps clarify use case? thanks! -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Monday 03 August 2009 19:10:04 PGNet Dev wrote:
hi,
On Mon, Aug 3, 2009 at 9:52 AM, Michael Andres
wrote: JFYI: libzypp-6.13.0 Resolver::addUpgradeRepo to perform a dist upgrade restricted to one (or more, if called repeatedly) repository.
This should be suitable for
zypper dup --repo foo (or --name foo)
i thought 'dup' was to be across all enabled repos ... i'm unclear as to how 'dup' restricted to a given repo is, then, different than 'up' restricted to a particular repo.
can you perhaps clarify use case?
The main difference between 'dup' and 'up' is that 'dup' does not consider the installed packages version or vendor. Dup performs as if you were doing a fresh installation. The installed system just defines the amount of packages, but the packages origin is mostly determined by the repository priorities. Thus 'dup' is allowed to downgrade and change vendor. While 'up' just looks for newer versions and tries to stay with the installed vendor. Unfortunately Michael (mls) is on vacation, maybe he'd be able to explain better. If you e.g. decide to follow some development repo, you usually want to replace your installed packages with versions from that repo. You could assign a high priority to that repo and perform a plain 'zypper dup', but this might change much more than you actually want. And unlike zyppers current '--repo' implementation, which AFAIK just disables all other repos (Jano may correct me), the other repos say visible and the solver may use them to resolve dependencies. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Michael Andres wrote:
JFYI: libzypp-6.13.0 Resolver::addUpgradeRepo to perform a dist upgrade restricted to one (or more, if called repeatedly) repository.
Can you explain how is this different from not loading the unwanted repos? I suppose in that it still can satisfy some deps from the other repos if needed? -- 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)---
On Tuesday 04 August 2009 09:35:35 Jano Kupec wrote:
Michael Andres wrote:
JFYI: libzypp-6.13.0 Resolver::addUpgradeRepo to perform a dist upgrade restricted to one (or more, if called repeatedly) repository.
Can you explain how is this different from not loading the unwanted repos? I suppose in that it still can satisfy some deps from the other repos if needed?
Yes. Michael (mls) mentioned this in several bugreports that this approach should give better results. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Michael Andres wrote:
On Tuesday 04 August 2009 09:35:35 Jano Kupec wrote:
Michael Andres wrote:
JFYI: libzypp-6.13.0 Resolver::addUpgradeRepo to perform a dist upgrade restricted to one (or more, if called repeatedly) repository. Can you explain how is this different from not loading the unwanted repos? I suppose in that it still can satisfy some deps from the other repos if needed?
Yes. Michael (mls) mentioned this in several bugreports that this approach should give better results.
OK, i just wanted to make sure that this is *the* thing mls had in mind. I'll add --from for this - in the future all installing commands should get this option (install already has it). So that we have these two in zypper: --repo - only load this repo --from - install/upgrade from this repo, but satisfy deps from elsewhere if needed -- 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)---
participants (3)
-
Jano Kupec
-
Michael Andres
-
PGNet Dev