If its one major flaw I see in openSUSE is dist upgrading it is rather difficult compared to some other distros like Ubuntu, or even something like SolydXK.
If you dont know what you are doing dist upgrading openSUSE can be a real pain, especially the need to download a new image or manually editing all the repositories.
The terminal is not that ideal too, even zypper dup wont do dildly unless you manually edit the sources (or go tumbleweed) to the latest version.
Its always been something I felt held this distro back from reaching its full potential, and one should not have to go enterprise to get this kind of functionality.
I expect it is possible to write a simple script that would update the repos to the next version. It would mark all current repos as “disabled”, and provide the upgrade repos as “enabled”. There are probably ways that the script could inquire at the opensuse site to get the correct repo list. (James will probably come up with a bash script to do this, if he doesn’t already have one). You could probably file a request at “OpenFATE” for such a command.
That would make upgrading simpler.
For “Tumbleweed”, I’m inclined to think it best for people to not even try “Tumbleweed” unless they have at least the competence to manually change the repos appropriately.
This distro is not meant to be “like Ubuntu or…”. You are starting out with a flawed assumption, like it or not. 
Downloading a new image is the safest and cleanest way way to install a new release. That could apply to most distros.
If you don’t like the terminal, edit the sources with YaST, then zypper dup in terminal.
MadmanRB wrote:
>
> If its one major flaw I see in openSUSE is dist upgrading it is rather
> difficult compared to some other distros like Ubuntu, or even something
> like SolydXK.
> If you dont know what you are doing dist upgrading openSUSE can be a
> real pain, especially the need to download a new image or manually
> editing all the repositories.
> The terminal is not that ideal too, even zypper dup wont do dildly
> unless you manually edit the sources (or go tumbleweed) to the latest
> version.
> Its always been something I felt held this distro back from reaching its
> full potential, and one should not have to go enterprise to get this
> kind of functionality.
>
>
I wouldn’t want openSUSE offering me an upgrade through the same channel
as update/patches because if i absent-mindedly click on upgrade
without backing up my data and if upgrade fails then
i would be in a lot of trouble.
Also many people don’t want to upgrade their openSUSE until the
installed version doesn’t reach end of life.
–
GNOME 3.10.1
openSUSE 13.1 (Bottle) (x86_64) 64-bit
Kernel Linux 3.11.6-4-desktop
I never would teke responsability for managing a system when I haven’t the install medium (DVD in our case) lying on a shelf. I must be able to install even if everything else (including the network) fails.
On 2013-11-29 08:56, MadmanRB wrote:
>
> If its one major flaw I see in openSUSE is dist upgrading it is rather
> difficult compared to some other distros like Ubuntu, or even something
> like SolydXK.
Nay.
The way it is now is wonderful.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
I was being exemplary not literal though
A script would be nice, something like that would do nicely, or a ymp.
If I knew how I would do it but I have zero to none programming skills.
A script:
#!/bin/bash
sed -i 's/12\.3/13\.1/g' /etc/zypp/repos.d/*
zypper dup
This of course only works for upgrading 12.3 to 13.1, doesn’t check if all your repos exist for 13.1, and doesn’t check that you have all standard repos.
Well it is at least something along the lines of what I think openSUSE needs.
I mean its a great distro I just wish that version jumping was easier thats all.
There is YaST Wagon for that. But it’s not included anymore in openSUSE and you also had to change the repos manually.
See here:
Wagon - openSUSE
https://features.opensuse.org/310405
The instructions for running an upgrade are very straightforward; I simply copied them from SDB:System upgrade - openSUSE and pasted each line (four in all) into my console.
I had to respond to a few prompts but the instructions were always easy to follow and I ended up with as smooth an upgrade as I could have imagined (and, yes, I did download and burn a live CD beforehand just in case it did not work).
Yes I accept that. My point really is that openSUSE intentionally differentiates itself from other distros, like ubuntu for example, that make it easier for users taking their first steps with linux. Those distros will try to make the experience as seamless as possible, inevitably by taken some decisions away from the user.
I believe openSUSE prefers to leave more decisions and automation to the user, e.g choice of ways to install a new release, upgrade alternatives versus clean install. That way the user investigates and tries out different methods, learning more about the necessary decisions and the pitfalls. Given challenges, new users become advanced users.
The more users learn, the more likely they are to contribute to the project and community, and there are lots of different ways to do it. The project always needs more contributors.
consused, there is a way to accomidate the OP and still have it the way most of us like it. A script could do that as nrickert suggested is totally feasable. One could package it as an rpm. An option could be included so that it would ask if the user would like to do a rolling update release.
I, personally, take issue with some of the replies I have seen here. The OP, from what I read, isn’t asking so much as to why we don’t, and certainly not looking for excuses or “reasons” why it isn’t done. Having said this, again, this is something I take issue with. I don’t speak for the moderators or the rest of the forum staff. I think my signature explains my feelings on the issue.
On 2013-11-29 22:36, wolfi323 wrote:
>
> MadmanRB;2603611 Wrote:
>> A script would be nice, something like that would do nicely, or a ymp.
>> If I knew how I would do it but I have zero to none programming skills.
>
> A script:
>
> Code:
> --------------------
> #!/bin/bash
> sed -i ‘s/12.3/13.1/g’ /etc/zypp/repos.d/*
> zypper dup
> --------------------
>
> This of course only works for upgrading 12.3 to 13.1, doesn’t check if
> all your repos exist for 13.1, and doesn’t check that you have all
> standard repos.
Careful, because you have to disable all the other repos, like packman.
As it is, it can be dangerous.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Out of curiosity, why is that?
I did a similar upgrade like this, although a slightly different and I had no issues whilst all the gstreamer and other packages were upgraded nicely from Packman as it all worked just ‘fabulously’.
Yes, leaving Packman enabled should work without problems. You’ll have to change the repo URL to the newer version for that as well, of course.
But having arbitrary repos added can give trouble, as usual. On distribution upgrade there is no protection against vendor change.
Correct, and that’s exactly the main problem.
How should any automatic distribution upgrade tool know, which of the 1000s of repos are safe and which are not.
I merely wanted to demontrate that it is not hard and painful to do the actual upgrade.
A safer version of the script:
#!/bin/bash
zypper mr -da
zypper ar http://download.opensuse.org/distribution/13.1/repo/oss/ repo-oss
zypper ar http://download.opensuse.org/distribution/13.1/repo/non-oss/ repo-non-oss
zypper ar http://download.opensuse.org/update/13.1/ repo-update
zypper ar http://download.opensuse.org/update/13.1-non-oss/ repo-update-non-oss
zypper dup
This diables all repos and adds the 4 standard ones for the new version.
Now change that to take the new version as parameter and you have a minimal universal upgrade script… 
You could change “zypper mr -da” to “rm /etc/zypp/repos.d/*” if you want to, then all repos will be removed instead of just disabled. (adding a repo with a name that already exists may not be possible, even if that repo is disabled)
On 2013-11-30 13:36, wolfi323 wrote:
>
> Miuku;2603828 Wrote:
>> Out of curiosity, why is that?
>>
>> I did a similar upgrade like this, although a slightly different and I
>> had no issues whilst all the gstreamer and other packages were upgraded
>> nicely from Packman as it all worked just ‘fabulously’.
> Yes, Packman should work without problems.
It is not the tested path by the developers. Zypper posts a severe
warning when you do it. If it works, you were lucky.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
While I liike all the nice scripts shown here, IMHO the problem with this or any other script is that you can not let them loose on the uninitiated. They will use it with e.g. parameter 14.2 long after the devs decided to change the word “distribution” in the path to “distro”, or a more recent change, add a repo (the update-non-oss). The devs will feel free to do so without further notice because they will reckon this as being internal to what they offer. As usual, it is easier to write a script then to maintain it and keep it up-to-date.