[opensuse] what is the difference between zypper dup and yast switch system packages
This came up as I was trying to upgrade KDE, but it is more about the functionality of yast and zypper, so I am posting it in this list instead of the KDE list. I just upgraded my laptop to 12.2, and I wanted to afterwards upgrade to KDE 4.9. So I added the KDE 4.9 repositories for 12.2 and as I write this I am using yast to download the upgrade. I thought about doing it with zypper like I did last time when I was using 12.1, but I decided to try yast this time. So this time I went to yast, selected the KDE repositories I had enabled, and then clicked on the option "switch system packages to this repository." Now what I have learned is that when you do a zypper dup, you can either use the "--from" option" or the "-r" option to specify the repositories you are using. According to man zypper: --from <alias|name|#|URI> Restricts the upgrade to the specified repositories (the option can be used multiple times) only, but can satisfy dependen- cies also from the rest of enabled repositories. -r, --repo <alias|name|#|URI> Work only with the repository specified by the alias, name, number, or URI. This option can be used multiple times. So when I have used zypper dup in the past, I have used the --from option. So here is the question. When you upgrade via yast by switching system packages, is it the same as using the --from option with zypper, the same as using the -r option with zypper, or is it something different? -- G.O. Box #1: 12.1 | KDE 4.8.5 | AMD Phenom IIX4 | 64 | ATI Radeon HD 3300 | 16GB Box #2: 12.1 | KDE 4.9.1 | AMD Athlon X3 | 64 | nVidia C61 GeForce 7025 | 4GB Laptop: 12.2 | KDE 4.8.4 | Core i7-2620M | 64 | Intel HD Graphics 3000 | 8GB learning openSUSE and loving it -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I don't know what happend to this, But it seems my reply didn't make it to the list the 1st time... It would appear that on Sep 27, George Olson did say:
So here is the question. When you upgrade via yast by switching system packages, is it the same as using the --from option with zypper, the same as using the -r option with zypper, or is it something different?
1st, pardon me for not responding sooner. But I've only just recently installed an OpenSuSE system again on my laptop. And I've been spending more time with the forum than this list. And only just noticed your unanswered post. I decided to respond anyway because I've just been on the receiving end of a *_LOT_* of help with regard to "zypper dup" from forum gurus who seem to think this is better done with yast... The 1st thing you should know is that while "zypper dup" is a wonderful tool for changing from one release to another {like 12.1->12.2 or 12.x ->Tumbleweed etc...} It is not recommended for routine updates. (I guess it can really hose your system) I'd recommend you read how they patiently tried to talk me out of doing a "zypper dup" They explained a lot of what your asking... http://tinylink.in/YJI But whether you read that or not, may I strongly suggest that before you run "zypper dup" on a running system, do first back up your system partition(s) with clonezilla or something. That way if they are right and "zypper dup" is more risky than ubuntu's "apt-get dist-upgrade", and your system gets borked. You'll still be able restore what you had via the backed up partition(s) Have fun with it... -- JtWdyP -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/21/2012 12:25 AM, JtWdyP wrote:
I don't know what happend to this, But it seems my reply didn't make it to
But whether you read that or not, may I strongly suggest that before you run "zypper dup" on a running system, do first back up your system partition(s) with clonezilla or something. That way if they are right and "zypper dup" is more risky than ubuntu's "apt-get dist-upgrade", and your system gets borked. You'll still be able restore what you had via the backed up partition(s)
Have fun with it...
Thanks for the reply. I looked over the forum, and it seems like the gist of it is that zypper dup is dangerous when done just as a plain zypper dup, but the post does not seem to reflect much on the use of the different options with zypper dup. I have upgraded to KDE 4.9 several times on a few different machines using zypper dup and the --from option, and they have all gone very well. I have also done the upgrade using yast change system packages, and I did not feel like there was much difference. It seems that as long as you have your repositories set correctly, they are basically the same thing. I have not done a backup when I did that, but now after reading your post I think I will make a backup image before I do a zypper dup again, just to make sure I don't destroy my system. Thanks for the tip! -- G.O. Box #1: 12.2 | KDE 4.9.1 | AMD Phenom IIX4 | 64 | ATI Radeon HD 3300 | 16GB Box #2: 12.2 | KDE 4.9.1 | AMD Athlon X3 | 64 | nVidia C61 GeForce 7025 | 4GB Laptop: 12.2 | KDE 4.9.1 | Core i7-2620M | 64 | Intel HD Graphics 3000 | 8GB learning openSUSE and loving it -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
It would appear that on Oct 21, George Olson did say:
Thanks for the reply. I looked over the forum, and it seems like the gist of it is that zypper dup is dangerous when done just as a plain zypper dup, but the post does not seem to reflect much on the use of the different options with zypper dup.
Yeah, that's what I found to...
I have upgraded to KDE 4.9 several times on a few different machines using zypper dup and the --from option, and they have all gone very well. I have also done the upgrade using yast change system packages, and I did not feel like there was much difference. It seems that as long as you have your repositories set correctly, they are basically the same thing.
Now that sounds interesting. (I'm usually more comfortable with **cli methods than gui ones... ** That is as long as I can find good examples to remind me how...) I suspect your right about the --from option. But I'm not sure how well it would warn you about potentially broken dependencies. I do know that if yast doesn't like what a "switch" to some repo will do to your system you get a list of choices like uninstalling something, or uninstalling something else, Or canceling the switch operation... Course, if I practice what I preach and back-up 1st... I might even try that next time. But since you've used it, I'd like to ask if I understand how it worked. I happen to run E17 as my primary desktop. In that Forum thread one of the Forum gurus recommended that I switch first to the E17 repo, and then to packman. Now if I did this with "zypper dup --from" I should expect that when I "--from"ed the E17 repo, Then all installed packages that match the ones in the E17 repo would have their vendor change to E17's vendor. And that any installed packages that had different version numbers would be up/down graded using the E17 repo. Along with any other changes that version specific dependencies of other installed packages may require???????? And I'd get a list of proposed changes with one chance to say "no" right? Then when I repeated the process with the packman repo, I should expect that {assuming I didn't crash and burn} any installed packages that happened to have versions in both the E17 AND the packman repos, would now have the vendor set to packman?? Does that match your experience with it?
I have not done a backup when I did that, but now after reading your post I think I will make a backup image before I do a zypper dup again, just to make sure I don't destroy my system.
Thanks for the tip!
Yeah backing up has got to be the smartest, most recommended step prior to any system changing event {planned or otherwise} AND failing to backup has to be the dumbest, most commonly made mistake {by both the smartest and dumbest people alike} It's hard to get around to making the regular backups that I know I should do. So whenever I'm about to do anything risky, I try to imaging how much work it would take to update a system restored from the old dusty backup I took ages ago. That is usually enough to get me to grab an usb drive with some room on it... Nuff said! -- | --- ___ | <0> <-> | ^ JtWdyP | ~\___/~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/22/2012 01:57 AM, JtWdyP wrote:
It would appear that on Oct 21, George Olson did say:
Thanks for the reply. I looked over the forum, and it seems like the gist of it is that zypper dup is dangerous when done just as a plain zypper dup, but the post does not seem to reflect much on the use of the different options with zypper dup.
Yeah, that's what I found to...
I have upgraded to KDE 4.9 several times on a few different machines using zypper dup and the --from option, and they have all gone very well. I have also done the upgrade using yast change system packages, and I did not feel like there was much difference. It seems that as long as you have your repositories set correctly, they are basically the same thing.
Now that sounds interesting. (I'm usually more comfortable with **cli methods than gui ones... ** That is as long as I can find good examples to remind me how...) I suspect your right about the --from option. But I'm not sure how well it would warn you about potentially broken dependencies. I do know that if yast doesn't like what a "switch" to some repo will do to your system you get a list of choices like uninstalling something, or uninstalling something else, Or canceling the switch operation...
Course, if I practice what I preach and back-up 1st... I might even try that next time.
But since you've used it, I'd like to ask if I understand how it worked.
I happen to run E17 as my primary desktop. In that Forum thread one of the Forum gurus recommended that I switch first to the E17 repo, and then to packman. Now if I did this with "zypper dup --from" I should expect that when I "--from"ed the E17 repo, Then all installed packages that match the ones in the E17 repo would have their vendor change to E17's vendor. And that any installed packages that had different version numbers would be up/down graded using the E17 repo. Along with any other changes that version specific dependencies of other installed packages may require????????
And I'd get a list of proposed changes with one chance to say "no" right?
Yes, zypper always gives you the same kind of options that yast gives. It lists them out and then one by one it gives you the options of changing a package, ignoring because of broken depencies, etc. I don't know about the other package managers that are available like yum and rpm, because I have never used them. I really prefer zypper and have become pretty comfortable with it. If you use the --from option with zypper dup, according to the manual as I understand it, zypper will grab any dependencies from other enabled repositories if it needs to. However it will not do a distribution upgrade from those extra repositories, but only what is listed after --from. If, however, you use the -r option with zypper dup, zypper will only grab dependencies from the repositories listed after -r, and so it will be more likely to have some dependency conflicts because not all the repositories will be available with zypper dup.
Then when I repeated the process with the packman repo, I should expect that {assuming I didn't crash and burn} any installed packages that happened to have versions in both the E17 AND the packman repos, would now have the vendor set to packman??
Does that match your experience with it?
That is the way I would interpret it. It should switch everything to the packman repos excepting any dependencies that are not available from packman, and any new dependencies that are not available from packman it should be able to grab from the other repos. Good luck! -- G.O. Box #1: 12.2 | KDE 4.9.1 | AMD Phenom IIX4 | 64 | ATI Radeon HD 3300 | 16GB Box #2: 12.2 | KDE 4.9.1 | AMD Athlon X3 | 64 | nVidia C61 GeForce 7025 | 4GB Laptop: 12.2 | KDE 4.9.1 | Core i7-2620M | 64 | Intel HD Graphics 3000 | 8GB learning openSUSE and loving it -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
George Olson -
JtWdyP