File conflicts happen when two packages attempt to install files with the same name but different contents.
This document (000021431) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server for SAP Application 15
SUSE Linux Enterprise Server for SAP Application 15
Situation
For example, the offline upgrade from SLES12 SP5 to SLES15 SP5 was successful. However, when trying to update the OS patching, the following conflict messages appear.
# zypper up ... File /sbin/unix2_chkpwd from install of pam-1.3.0-150000.6.66.1.x86_64 (SLE-Module-Basesystem15-SP5-Updates) conflicts with file from package pam-modules-12.1-25.4.5.x86_64 (@System) File /usr/bin/easy_install-3.6 from install of python3-setuptools-44.1.1-150400.9.6.1.noarch (SLE-Module-Basesystem15-SP5-Updates) conflicts with file from package python36-setuptools-44.1.1-8.6.1.noarch (@System) File /usr/bin/pydoc3.6 from install of python3-base-3.6.15-150300.10.60.1.x86_64 (SLE-Module-Basesystem15-SP5-Updates) conflicts with file from package python36-base-3.6.15-55.1.x86_64 (@System) File /usr/bin/python3.6 from install of python3-base-3.6.15-150300.10.60.1.x86_64 (SLE-Module-Basesystem15-SP5-Updates) conflicts with file from package python36-base-3.6.15-55.1.x86_64 (@System) File /usr/bin/python3.6m from install of^M python3-base-3.6.15-150300.10.60.1.x86_64 (SLE-Module-Basesystem15-SP5-Updates) conflicts with file from package python36-base-3.6.15-55.1.x86_64 (@System) File /usr/bin/pyvenv-3.6 from install of python3-base-3.6.15-150300.10.60.1.x86_64 (SLE-Module-Basesystem15-SP5-Updates) conflicts with file from package python36-base-3.6.15-55.1.x86_64 (@System) ... File /usr/share/man/man1/python3.6.1.gz from install of python3-base-3.6.15-150300.10.60.1.x86_64 (SLE-Module-Basesystem15-SP5-Updates) conflicts with file from package python36-base-3.6.15-55.1.x86_64 (@System) File /usr/share/man/man8/unix2_chkpwd.8.gz from install of pam-1.3.0-150000.6.66.1.x86_64 (SLE-Module-Basesystem15-SP5-Updates) conflicts with file from package pam-modules-12.1-25.4.5.x86_64 (@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): Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. History: - ABORT request: Please see the above error message for a hint.
Resolution
In SLES12 SP5, the python36 packages and the pam-modules come from the SLES12-SP5-Updates repository. After upgrading to SLES15 SP5, they are no longer included in any of the repositories for SLES15 SP5, so the conflict message displays '@System' for these packages.
# zypper se -s python36 ... S | Name | Type | Version | Arch | Repository --+---------------------+---------+---------------+--------+------------------ i | python36 | package | 3.6.15-55.1 | x86_64 | (System Packages) i | python36-base | package | 3.6.15-55.1 | x86_64 | (System Packages) i | python36-pip | package | 20.2.4-8.15.1 | noarch | (System Packages) i | python36-setuptools | package | 44.1.1-8.6.1 | noarch | (System Packages) # zypper se -s pam-modules ... S | Name | Type | Version | Arch | Repository --+-------------------+---------+-------------+--------+------------------ i | pam-modules | package | 12.1-25.4.5 | x86_64 | (System Packages) i | pam-modules-32bit | package | 12.1-25.4.5 | x86_64 | (System Packages)These orphaned packages might be able to be removed, but it might be safer to go with the other option, '--replacefiles'.
# zypper up --replacefiles
Cause
The conflict messages appear when trying to update after installing packages from the DVD using the boot option media_upgrade=1. It would be important to check where the conflicting package is coming from. In this example, the python36 packages and the pam-modules are reported to come from '@System'. Consequently, the conflict messages appear.
Additional Information
Note: ist is recommended to use "zypper patch" instead of "zypper up", as patch is able to handle situation with conflicting versions better than "up". Still "patch" will complain about replacing the files mentioned, but all the while will show a dialog to replace the duplicates.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000021431
- Creation Date: 17-Apr-2024
- Modified Date:01-Aug-2024
-
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
