how to update 42.1 to 42.2?

#I’m sorry for my bad English
i use opensuse 42.1 and use those repos for update

~> zypper repos 
#  | Alias                               | Name                                    | Enabled | GPG Check | Refresh
1 | Frameworks5                         | Frameworks5                             | Yes     | (r ) Yes  | No   
2 | QT5_1                               | QT5                                     | Yes     | (r ) Yes  | No    
3 | home:wolfi323                       | home:wolfi323                           | Yes     | (r ) Yes  | No       
4 | kernel:standard                     | kernel:standard                         | Yes     | (r ) Yes  | No    
5 | openSUSE:Leap:42.1                  | openSUSE:Leap:42.1                      | Yes     | ( p) Yes  | No     
6 | packman                             | packman                                 | Yes     | (r ) Yes  | No    
7 | repo-non-oss                        | openSUSE-Leap-42.1-Non-Oss              | Yes     | ( p) Yes  | No     
8 | repo-oss                            | openSUSE-Leap-42.1-Oss                  | Yes     | ( p) Yes  | No     
9 | KDE:Extra                           | KDE:Extra                               | Yes  
10| repo-update                         | openSUSE-Leap-42.1-Update               | Yes     | (r ) Yes  | No     
11| repo-update-non-oss                 | openSUSE-Leap-42.1-Update-Non-Oss       | Yes     | (r ) Yes  | No  

how can i upgrade opensuse 42.1 to 42.2 ?
if i want upgrade 42.2 Should I disable unofficial repos?

As 42.2 is not yet released, there is still no “official” documentation about this.

But you may assume that it will not differ much from other upgrades to the next level.

if come official release ans stable 42.2. i want upgrade 42.2 Should I disable unofficial repos?

To begin with, I repeat that this is pure speculation based on the past. No guarantee for the future.

When you do an online upgrade, you normaly disable/remove non-standard repos. Then you change the standard repos to those of the new releease (often by editing the version part of their pathes from e.g. 41.1 to 41.2). Then follows an

zypper dup

I then would first add the 42.2 Packman repo and do a

zypper dup --from <id of the Packman repo>

Then add the 42.2 versions of other extra repos (if they exist) and install what you need from them. When there are no 42.2 versions of the thos extra repos packages, you either might test if they still function or remove them. It is up to you.

Others may have aadditional or other advice though. :wink:

Of course, anyone can do whatever they want with their system, but I’m wondering if upgrading so soon after you have got your present system stabilised, after all the troubles you had previously, is a wise thing to do. You might not know it, but 42.2 won’t be released until next month, and is still in some sort of Beta level. And even though it’s only a month before release, it is still unstable (per all the comments by those testing it out). My suggestion is to wait for the release, watch the forum for problems, and then when you are confident that most of the bugs are ironed out, then upgrade.

But again, it IS your system.

All the best.

Not without issues, when I have a look at the repolist. It lacks URL’s for the repos so f.e. KDE:Extra could be any of the many.

The list makes me feel you’re trying to have your own Tumbleweed, but without the openQA testing.

Thank you so much for your help

  1. Download the Leap 42.2 Network Installation .iso (after Leap 42.2 has been officially
    released) from the usual source: <>. 1. Burn the Network Installation .iso to a CD-RW or CD-ROM.
  2. Boot the CD and perform the upgrade. Documentation is here: <>

If you have sufficient Network quota/bandwidth and the ability to burn DVD media, then you could choose the “normal” for a lot of people method of using the 4.7GB DVD which is also suitable for USB sticks.

Instead of upgrading to 42.2 before it is released why not download it, put it on a usb or dvd and test it with virtualising software. This way you’ll be keeping the stability of openSUSE and maybe helping out by raising any bugs you encounter with the devs. Of course if you just want more up to date distro then Tumbleweed would be perhaps better?? You could even dual boot tumblweed and regular openSUSE!!