The idea is about an easy way to allow users to make upgrades (e.g.: changing from one major version like 15.0 to version 15.1) using a GUI and as easy as they can in Ubuntu.
Something like a notification with a button to perform the upgrade with just one-click, instead of having to deal with the terminal, that frights some new users and gives them the sensation of an outdated system.
In short, this would perform the following actions:
- Notify there is a new version of openSUSE, asking if the user wants to upgrade.
- If the user accepts it should make a "zypper --releasever=15.3 dup" (after password...)
- And finally make a computer reboot
This could be integrated in Yast or in Discover.
This, i believe would bring good User benefits such as:
- encourage users to keep their distro in it's lastest version, even if they don't understand much about computers!
- bring them a greater experience in openSUSE since they will have access to stable and newest features and also many other improvements.
- it will end with the disadvantage of one of the most mentioned Ubuntu features.
- it would look more modern
We also, already, had a few implementations in this areas:
- openSUSE Wagon - now deprecated
- Yast-Migration Module - SLE specific that might be able to be adapted
I don't believe there would be much work to this and the benefits would be great... :)
This should be applied to Tumbleweed as well. My idea for tumbleweed being: An option - off by default - to enable auto-upgrade without confirmation.
Would be good to have this feature without the need to register the system anywhere (unlike SUSE).
After some search i discovered someone already had this idea a long time ago (since at least 2012). So I borrowed some text (with a few upgrades) from the OpenFATE feature ( https://features.opensuse.org/313441 ).
Related Links:
https://bugzilla.opensuse.org/show_bug.cgi?id=1201144
https://bugs.kde.org/show_bug.cgi?id=451849
https://hackweek.opensuse.org/21/projects/implement-gnome-softwares-distribution-upgrade-in-leap
Looking for hackers with the skills:
This project is part of:
Hack Week 14 Hack Week 15 Hack Week 16 Hack Week 17 Hack Week 18 Hack Week 19 Hack Week 20 Hack Week 21 Hack Week 22
Activity
Comments
-
-
-
almost 8 years ago by maverick74 | Reply
Yes, i believe it would make a lot of sense. As long as it's not mandatory, of course.
It could be the default configuration, but if one (really) wants to take the risk it should be able to do live upgrades as well.
(Anyway, isn't this the default behavior already? When one does a "zypper dup" it first downloads all the packages and only then performs the upgrade)
-
over 7 years ago by maverick74 | Reply
I've been thinking about this and i would like to add that this applied to Tumbleweed would also be gold (my idea for tumbleweed being actually an option - off by default - to enable auto-upgrade without confirmation).
-
-
about 7 years ago by maverick74 | Reply
I just found this: https://progress.opensuse.org/issues/20910
Not sure if this is related, however...
-
-
over 6 years ago by lnussel | Reply
I'd actually like to get Leap into SCC so we can reuse the existing yast migration module, ie no separate code to maintainer for openSUSE. The part about notifying the user of a distro upgrade would still need to be implemented somehow eg via packagekit and the updater applets.
-
over 5 years ago by maverick74 | Reply
Hi. Are there any good news on this for 15.1?
(or any news at all?)
Reply to maverick74
Hi. Are there any good news on this for 15.1?
(or any news at all?)
# A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image  This is a user link @hans This is a project link hw#some-cool-title
-
-
over 5 years ago by JonathanKang | Reply
This can be implemented in GNOME Software and PackageKit.
Several zypp backend method are missing in PackageKit to preform related actions.
GNOME Software can upgrade the system with just a few clicks(this works in Fedora, which has proper PackageKit support).
-
over 5 years ago by maverick74 | Reply
I think Discover also supports it, as well as YaST thru the Online Migration module...
I really don't think there would be much work to do on this, specially when compared to other projects, but after a few years we still don't have this feature in openSUSE, which i believe is a last-missing-block. Still, no one picks this up :(
-
over 5 years ago by fschnizlein | Reply
Hi I added recently added Leap support to SCC and I thought would be a nice to have the migrations also there. Since SCC already supports complex migrations from one to another product adding migrations for Leap shouldn't be a huge problem. I think this could be done as a hackweek project.
-
over 5 years ago by maverick74 | Reply
That's GREAT!!!
2 questions, however:
1.Is Tumbleweed also supported? 2.Are we required to register or is it available without registration?
-
over 5 years ago by ikapelyukhin | Reply
Registering openSUSE to SCC is kinda meh unless you actually plan to migrate it to SLES. However, I think it would be relatively trivial to re-implement the migration API endpoint as a stand-alone daemon working on localhost.
-
-
over 5 years ago by fschnizlein | Reply
How about implement it like this:
- Provide a API (which requires no authentication at all) which lists all possible migrations for a given openSUSE
CPEThis could be provided for example by SCC and proxied to the opensuse.org domain - Add support for this to the SUSEConnect library which is already used by
zypper migrationandyast2-migration - Update/Write a good documentation for the openSUSE wiki
Why I would do it like this:
The infrastructure with the data is already their and maintained. Implementing another way, might be faster and more easy but I'm a little bit afraid, nobody is maintaining the new solution. On the other hand SCC is already in place. With adding Leap -> SLES migration the openSUSE products are already in the system, adding the migration path from Leap -> Leap or Leap -> Tumbleweed is no much more effort and @lnussel already has to make sure new versions get added. By using the already existing client solutions like
yast2-migrationandzypper migrationwe get two client applications which server both a GUI migration application and a already workingzypper plugin.What do you think? @maverick74 and @ikapelyukhin?
-
over 5 years ago by maverick74 | Reply
I love the idea! :)
I have just one question: in the tumbleweed case, could it be used to upgrade (say for e.g.:) from Tumbleweed 20190616 -> Tumbleweed 20190618 ?
-
over 5 years ago by fschnizlein | Reply
From my point of view both versions are in the end the same product release. I would just create Tumbleweed without dates as product and allow users to migrate from Leap to Tumbleweed and not from one snapshot to another.
-
over 5 years ago by maverick74 | Reply
It does make sense the way you put it!
I'm totally in agree with your idea! :)
-
-
-
over 5 years ago by maverick74 | Reply
@fschnizlein Let me ask another question:
In the Leap case, will user get notified that a new version is available?Or that is not in the scope of this project?
Thank you. Happy hackweek :)
- Provide a API (which requires no authentication at all) which lists all possible migrations for a given openSUSE
-
over 5 years ago by ikapelyukhin | Reply
I've put together opensuse-migration prototype -- it's a bit rough around the edges, but it does what I expect it to do. Give it a try, tell me what you think (via email or Github issues) :D
-
almost 5 years ago by maverick74 | Reply
Just an update:
ikapelyukhin approach did not have any GUI and there is none planed.
Also, i don't know if his implementation ever moved into the https://github.com/openSUSE/ namespace or if it just ended up being achieved.
@ikapelyukhin , can you please bring some more light into the subject about the state of the project? Tks
-
almost 5 years ago by lkocman | Reply
There is a brand new tool to migrate any rhel-like system to RHEL. Perhaps you could inspire there. https://www.redhat.com/en/blog/convert2rhel-how-update-rhel-systems-place-subscribe-rhel?sccid=701f2000000tyBtAAI&fbclid=IwAR0WsT4yFNi3ovbpStKkmfTEgCxtqRiX-wJ-Sp0GMeN2QqVS5cAdSY7E
Also have a look at the app migration (the web part)
https://www.redhat.com/en/blog/whats-new-red-hat-application-migration-toolkit-42-including-oraclejdk-openjdk-migration
-
almost 5 years ago by Pharaoh_Atem | Reply
I've actually gotten pretty far in implementing something like this using
dnf system-upgradewhenrpm-repos-openSUSE-Leapis installed.Steps to try it:
- Install the
rpm-repos-openSUSE-Leappackage - Install
dnfanddnf-plugin-system-upgrade - Run
dnf system-upgrade --releasever 15.2 download - Run
dnf system-upgrade reboot
Alternatively, you can install
rpm-repos-openSUSE-Tumbleweedand use that to upgrade from Leap to Tumbleweed. - Install the
- Install the
rpm-repos-openSUSE-Leappackage - Install
dnfanddnf-plugin-system-upgrade - Run
dnf system-upgrade --releasever 15.2 download - Run
dnf system-upgrade reboot -
over 3 years ago by maverick74 | Reply
Things have gotten even simplier and now we just need just to run
zypper --releasever=15.3 ref
zypper --releasever=15.3 dup
But there's still no official notification about new versions neither a Wizard GUI fot the upgrade...
-
over 3 years ago by ancorgs | Reply
Maybe interesting for you: https://github.com/yast/yast-online-update-configuration/issues/25
-
over 3 years ago by cdywan | Reply
Is there a plan for this hackweek? What's the current status? I love the idea of easy upgrades but there's so many different projects mentioned in comments...
-
over 3 years ago by maverick74 | Reply
Nah... there has been a couple of iniciatives about this - some closer to the original idea, others not that quite. But there's never has been anything done that has been accepted into the main project.
That's why i keep this thing open...
Things have improved over (this many years) however.
We are now able to use a simple "zypper releasever=15.3 dup" that will upgrade the repos and perform the upgrade - which is nice but...
We still have no Notification when there's a new version available and no way to perform it without getting our fingers into the terminal.
And that's the major idea: something like Ubuntu/Windows/MacOS that, when a new version of the OS is out, the user get's notified and with a simple button click (and password, naturally) he can perform the upgrade to the new version without having to type into the Terminal/konsole...
-
over 3 years ago by maverick74 | Reply
Also, in case you missed it, ikapelyukhin put up a good implementation of this (with no GUI or notification at the time, however)... but interest from the openSUSE team was apparentely...... none... :(
-
-
over 2 years ago by m_vanderwulp | Reply
> We are now able to use a simple "zypper releasever=15.3 dup" that will upgrade the repos and perform the upgrade
Well, that "releasever" system is broken in the 15.3 to 15.4 upgrade ... see my description of step 6 at https://en.opensuse.org/SDB:SystemupgradetoLeap15.4#6.Refreshwiththenew_repos:
This is caused by the relocation of some repos as follows:
http://download.opensuse.org/repositories/network/openSUSELeap15.3/
http://download.opensuse.org/repositories/network/15.4/
I wonder what the reason was for this incompatible repo location change?
BTW, also step 5 in that document can not be automated.
-
over 2 years ago by maverick74 | Reply
It's broken?!
My upgrade worked just fine the the only machine i have with Leap...
(and yes... step 5 is a manual-thing, but... maybe that could already come as default, no?)
-
-
almost 2 years ago by FabioMux | Reply
Unfortunately, things are not as easy as a simple
zypper --releasever=15.3 ...because repository paths can change and third-party repositories might not be enabled at the time.That's why I spent some time building the script
zypper-upgraderepofirst and later the small interactive scriptzypper-upgradedistroto guide step by step through the needed operations to perform a smoother upgrade.They are already available in my repository
Some references about the projects:
- https://freeaptitude.altervista.org/projects/zypper-upgradedistro.html
- https://freeaptitude.altervista.org/articles/upgrading-opensuse-leap-with-zypper-upgradedistro.html
- https://github.com/fabiomux/zypper-upgradedistro
- https://freeaptitude.altervista.org/projects/zypper-upgraderepo.html
- https://freeaptitude.altervista.org/articles/upgrading-opensuse-with-zypper.html
- https://github.com/fabiomux/zypper-upgraderepo
-
over 1 year ago by maverick74 | Reply
I could not read the entire thing as i should (sorry... it's a lack of time!) and while the idea is about a GUI, your approach is also very interesting.
But from what i could understand we need 2 scripts
- the zypper-upgraderepo and
- the zypper-upgradedistro
is that right? (or did i miss something?)
If we really need two: Why can't it be a one-script procedure?
-
over 1 year ago by FabioMux | Reply
There are two scripts only to keep the two concerns separated and better isolate and fix the issues later.
So you can - upgrade/check/update the repositories URLs using only zypper-upgraderepo and do the rest by yourself; - upgrade your distro using zypper-upgradedistro, which makes use of the former script under the hood to achieve part of the job.
That way, once it is perfected, we might evolve into a GUI (I was thinking of a Yast module) the zypper-upgradedistro script, which just reflects the steps listed on the official wiki, without rewriting, but integrating the job done by zypper-upgraderepo as an external library.
Reply to Pharaoh_Atem
I've actually gotten pretty far in implementing something like this using dnf system-upgrade when rpm-repos-openSUSE-Leap is installed.
Steps to try it:
Alternatively, you can install rpm-repos-openSUSE-Tumbleweed and use that to upgrade from Leap to Tumbleweed.
# A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image  This is a user link @hans This is a project link hw#some-cool-title
Similar Projects
New migration tool for Leap by lkocman
Update
I will call a meeting with other interested people at 11:00 CET https://meet.opensuse.org/migrationtool
Description
SLES 16 plans to have no yast tool in it. Leap 16 might keep some bits, however, we need a new tool for Leap to SLES migration, as this was previously handled by a yast2-migration-sle
Goals
A tool able to migrate Leap 16 to SLES 16, I would like to cover also other scenarios within openSUSE, as in many cases users would have to edit repository files manually.
- Leap -> Leap n+1 (minor and major version updates)
- Leap -> SLES docs
- Leap -> Tumbleweed
- Leap -> Slowroll
- Leap Micro -> Leap Micro n+1 (minor and major version updates)
- Leap Micro -> MicroOS
Hackweek 24 update
Marcela and I were working on the project from Brno coworking as well as finalizing pieces after the hackweek. We've tested several migration scenarios and it works. But it needs further polishing and testing.
Projected was renamed to opensuse-migration-tool and was submitted to devel project https://build.opensuse.org/requests/1227281
Repository
https://github.com/openSUSE/opensuse-migration-tool
Out of scope is any migration to an immutable system. I know Richard already has some tool for that.
Resources
Tracker for yast stack reduction code-o-o/leap/features#173 YaST stack reduction