Python Conflicts Upgrading to Leap 15.0 from 42.3

Hi,

I am upgrading to Leap 15.0 from 42.3

I have 117 conflicts and they all seem to relate to Python:

 File /usr/lib/python2.7/site-packages/urllib3/util/wait.py  from install of
     python2-urllib3-1.22-lp150.4.1.noarch (openSUSE-Leap-15.0-Oss)
  conflicts with file from package
     python-urllib3-1.22-4.4.1.noarch (@System)


File /usr/lib/python2.7/site-packages/urllib3/util/wait.pyc
  from install of
     python2-urllib3-1.22-lp150.4.1.noarch (openSUSE-Leap-15.0-Oss)
  conflicts with file from package
     python-urllib3-1.22-4.4.1.noarch (@System)


File /usr/lib/python2.7/site-packages/urllib3/util/wait.pyo
  from install of
     python2-urllib3-1.22-lp150.4.1.noarch (openSUSE-Leap-15.0-Oss)
  conflicts with file from package
     python-urllib3-1.22-4.4.1.noarch (@System)


File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
Continue? [yes/no] (no):                

Can I continue?

Yes, that’s OK. You’ll install the Leap 15.0 Python packages.

But before you go ahead you should check that all of your enabled repositories are for leap 15, if you’ve not all ready done so.

Thanks Paul,

But before you go ahead you should check that all of your enabled repositories are for leap 15,

I hope the below means it is ok?

 by79@linux-3ztp:~> zypper lr
Repository priorities are without effect. All enabled repositories share the same priority.


#  | Alias                     | Name                                    | Enabled | GPG Check | Refresh
---+---------------------------+-----------------------------------------+---------+-----------+--------
 1 | NVIDIA                    | NVIDIA                                  | Yes     | (r ) Yes  | Yes    
 2 | google-chrome             | google-chrome                           | Yes     | (r ) Yes  | Yes    
 3 | libdvdcss                 | libdvdcss                               | Yes     | (r ) Yes  | Yes    
 4 | openSUSE-Leap-15.0-0      | openSUSE-Leap-15.0-0                    | No      | ----      | ----   
 5 | packman                   | packman                                 | Yes     | (r ) Yes  | Yes    
 6 | repo-debug                | openSUSE-Leap-15.0-Debug                | No      | ----      | ----   
 7 | repo-debug-non-oss        | openSUSE-Leap-15.0-Debug-Non-Oss        | No      | ----      | ----   
 8 | repo-debug-update         | openSUSE-Leap-15.0-Update-Debug         | No      | ----      | ----   
 9 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | No      | ----      | ----   
10 | repo-non-oss              | openSUSE-Leap-15.0-Non-Oss              | Yes     | (r ) Yes  | Yes    
11 | repo-oss                  | openSUSE-Leap-15.0-Oss                  | Yes     | (r ) Yes  | Yes    
12 | repo-source               | openSUSE-Leap-15.0-Source               | No      | ----      | ----   
13 | repo-source-non-oss       | openSUSE-Leap-15.0-Source-Non-Oss       | No      | ----      | ----   
14 | repo-update               | openSUSE-Leap-15.0-Update               | Yes     | (r ) Yes  | Yes    
15 | repo-update-non-oss       | openSUSE-Leap-15.0-Update-Non-Oss       | Yes     | (r ) Yes  | Yes    
by79@linux-3ztp:~>  

I just follow the instructions:

https://en.opensuse.org/SDB:System_upgrade

Need to see the URL to be certain of #1, 2, 3, and 5 - the rest are just as they need to be.

Use

zypper lr -d

Personally I’d uninstall the nvidia proprietary driver, reboot the system to ensure all is ok, then disable that repository also, adding it back after the update has completed.

Hi Paul,

Sorry to trouble you. Are they ok as below? How about #2?

Thanks again.

by79@linux-3ztp:~> zypper lr -dRepository priorities are without effect. All enabled repositories share the same priority.


#  | Alias                     | Name                                    | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                                | Service
---+---------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+------------------------------------------------------------------------------------+--------
 1 | NVIDIA                    | NVIDIA                                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://http.download.nvidia.com/opensuse/leap/15.0                                 |        
 2 | google-chrome             | google-chrome                           | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                                |        
 3 | libdvdcss                 | libdvdcss                               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/openSUSE_Leap_15.0/                                 |        
 4 | openSUSE-Leap-15.0-0      | openSUSE-Leap-15.0-0                    | No      | ----      | ----    |   99     | yast2  | hd:///?device=/dev/disk/by-id/usb-SanDisk_Ultra_Fit_4C531001560725109115-0:0-part1 |        
 5 | packman                   | packman                                 | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://packman.inode.at/suse/openSUSE_Leap_15.0/                                   |        
 6 | repo-debug                | openSUSE-Leap-15.0-Debug                | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/15.0/repo/oss/                |        
 7 | repo-debug-non-oss        | openSUSE-Leap-15.0-Debug-Non-Oss        | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/15.0/repo/non-oss/            |        
 8 | repo-debug-update         | openSUSE-Leap-15.0-Update-Debug         | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.0/oss/                           |        
 9 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.0/non-oss/                       |        
10 | repo-non-oss              | openSUSE-Leap-15.0-Non-Oss              | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/                  |        
11 | repo-oss                  | openSUSE-Leap-15.0-Oss                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/oss/                      |        
12 | repo-source               | openSUSE-Leap-15.0-Source               | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/distribution/leap/15.0/repo/oss/               |        
13 | repo-source-non-oss       | openSUSE-Leap-15.0-Source-Non-Oss       | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/distribution/leap/15.0/repo/non-oss/           |        
14 | repo-update               | openSUSE-Leap-15.0-Update               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.0/oss/                                 |        
15 | repo-update-non-oss       | openSUSE-Leap-15.0-Update-Non-Oss       | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.0/non-oss/                             |        
by79@linux-3ztp:~> 



Without checking actual versions,
The original files appear to be coming from “WSystem,” likely a DVD.
But, yes…
Since the old file is reported to be from @System, there should not be any problems. If the files before upgrade came from somewhere else, then you’d have to do further investigation of the source.

To properly upgrade,
You should follow the appropriate SDB instructions
https://en.opensuse.org/SDB:System_upgrade
https://en.opensuse.org/SDB:Offline_upgrade

TSU

Looks OK, all repositories are pointing to leap 15.0

How about #2?

I’m not familiar with google-chrome, but guess that’s a generic package built for pretty much any x86_64 system.

If you want to play safe you could temporarily remove the google-chrome package(s) prior to the distribution upgrade, then add them back afterwards.

Thanks Guys, appreciate your comments!