SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After each update done with "zypper up" there is a not-so-much-clear urge to perform "zypper dup" Do I have to issue the "zypper dup" command manually? Are there adverse consequences if I refrain from doing so?
You should read the man page on the zypper command. The "dup" does a distribution upgrade...the "up" only does the current packages. The "dup" for Tumbleweed is (in my opinion) better, since you have the benefit of the Tumbleweed rolling release. Otherwise, you'll stay where you are on a lot of things. Adverse?? Probably not. The "dup" puts in the new, tested snapshot of EVERYTHING, including any changes in repository.
After each update done with "zypper up" there is a not-so-much-clear urge to perform "zypper dup"
That message is presented to remind you that zypper up on a Tumbleweed installation is officially unacceptable system maintenance. Each TW version, as often as daily, with daily being the continual target, is considered a release of a new distribution, hence application of the term "rolling", and selection of the name, for a weed that the wind rolls into a wad that tumbles across flatlands. Thus, distribution upgrade is the only official path to maintaining a fully upgraded state. Fully upgrading is also possible via YaST, but not via zypper up, which updates existing packages, but does not remove obsolete packages, and does not add new packages.
Quote:
Do I have to issue the "zypper dup" command manually?
It can be scripted by those proficient with scripting and various tasks one might associate with the duping process.
Quote:
Are there adverse consequences if I refrain from doing so?
There will be eventually if you refrain long enough, possibly on your first boot subsequent to a zypper up.
That message is presented to remind you that zypper up on a Tumbleweed installation is officially unacceptable system maintenance. Each TW version, as often as daily, with daily being the continual target, is considered a release of a new distribution, hence application of the term "rolling", and selection of the name, for a weed that the wind rolls into a wad that tumbles across flatlands. Thus, distribution upgrade is the only official path to maintaining a fully upgraded state. Fully upgrading is also possible via YaST, but not via zypper up, which updates existing packages, but does not remove obsolete packages, and does not add new packages.
It can be scripted by those proficient with scripting and various tasks one might associate with the duping process.
There will be eventually if you refrain long enough, possibly on your first boot subsequent to a zypper up.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.