diff --git a/docs/en/docs/Administration/faqs.md b/docs/en/docs/Administration/faqs.md index dfac5e48eade773ff0e2a47211aaabed12250281..e6c30f59eea49f1fa4e7cd7a7feb9417317955c1 100644 --- a/docs/en/docs/Administration/faqs.md +++ b/docs/en/docs/Administration/faqs.md @@ -110,10 +110,10 @@ Modify the **/etc/sysconfig/sntp** file and add the domain name of the NTP ser Software package conflict, file conflict, or missing software packages may occur during software package installation. As a result, the upgrade is interrupted and the installation fails. The error information about software package conflict, file conflict, and missing software packages is as follows: -The following is an example of software package conflict error information \(the conflict between **libev-libevent-devel-4.24-11.oe1.aarch64** and **libevent-devel-2.1.11-2.oe1.aarch64** is used as an example\): +The following is an example of software package conflict error information \(the conflict between **libev-libevent-devel-4.33-4.oe2203SP4.aarch64** and **libevent-devel-2.1.12-5.oe2203SP4.aarch64** is used as an example\): ```text -package libev-libevent-devel-4.33-4.oe2203sp3.aarch64 conflicts with libevent-devel provided by libevent-devel-2.1.12-5.oe2203sp3.aarch64 +package libev-libevent-devel-4.33-4.oe2203SP4.aarch64 conflicts with libevent-devel provided by libevent-devel-2.1.12-5.oe2203SP4.aarch64 - cannot install the best candidate for the job - conflicting requests ``` @@ -122,18 +122,18 @@ The following is an example of file conflict error information \(the **/usr/bin ```text Error: Transaction test error: - file /usr/bin/containerd from install of containerd-1.2.0-309.oe2203sp3.aarch64 conflicts with file from package docker-engine-18.09.0-325.oe2203sp3.aarch64 - file /usr/bin/containerd-shim from install of containerd-1.2.0-309.oe2203sp3.aarch64 conflicts with file from package docker-engine-18.09.0-325.oe2203sp3.aarch64 + file /usr/bin/containerd from install of containerd-1.2.0-309.oe2203SP4.aarch64 conflicts with file from package docker-engine-18.09.0-325.oe2203SP4.aarch64 + file /usr/bin/containerd-shim from install of containerd-1.2.0-309.oe2203SP4.aarch64 conflicts with file from package docker-engine-18.09.0-325.oe2203SP4.aarch64 ``` The following is an example of the error message indicating that the **blivet-data** software package is missing: ```text Error: - Problem: cannot install both blivet-data-3.4.2-7.oe2203sp3.noarch and blivet-data-1:3.1.1-5.noarch - - package python3-blivet-3.4.2-7.oe2203sp3.noarch requires blivet-data = 1:3.1.1-5, but none of the providers can be installed + Problem: cannot install both blivet-data-3.4.2-7.oe2203SP4.noarch and blivet-data-1:3.1.1-5.noarch + - package python3-blivet-3.4.2-7.oe2203SP4.noarch requires blivet-data = 1:3.1.1-5, but none of the providers can be installed - cannot install the best update candidate for package blivet-data-1:3.1.1-5.noarch - - problem with installed package python3-blivet-3.4.2-7.oe2203sp3.noarch(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) + - problem with installed package python3-blivet-3.4.2-7.oe2203SP4.noarch(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) ``` ### Possible Cause @@ -146,41 +146,41 @@ Error: If a software package conflict occurs, perform the following steps \(the software package conflict in "Symptom" is used as an example\): -1. According to the error message displayed during the installation, the software package that conflicts with the to-be-installed software package **libev-libevent-devel-4.24-11.oe1.aarch64** is **libevent-devel-2.1.11-2.oe1.aarch64**. +1. According to the error message displayed during the installation, the software package that conflicts with the to-be-installed software package **libev-libevent-devel-4.33-4.oe2203SP4.aarch64** is **libevent-devel-2.1.12-5.oe2203SP4.aarch64**. 2. Run the **dnf remove** command to uninstall the software package that conflicts with the software package to be installed. ```shell - dnf remove libevent-devel-2.1.12-5.oe2203sp3.aarch64 + dnf remove libevent-devel-2.1.12-5.oe2203SP4.aarch64 ``` 3. Perform the installation again. If a file conflict occurs, perform the following steps \(the file conflict in "Symptom" is used as an example\): -1. According to the error message displayed during the installation, the names of the software packages that cause the file conflict are **containerd-1.2.0-101.oe1.aarch64** and **docker-engine-18.09.0-100.aarch64**. -2. Record the names of the software packages that do not need to be installed. The following uses **docker-engine-18.09.0-100.aarch64** as an example. +1. According to the error message displayed during the installation, the names of the software packages that cause the file conflict are **containerd-1.2.0-309.oe2203SP4.aarch64** and **docker-engine-18.09.0-325.oe2203SP4.aarch64**. +2. Record the names of the software packages that do not need to be installed. The following uses **docker-engine-18.09.0-325.oe2203SP4.aarch64** as an example. 3. Run the **dnf remove** command to uninstall the software package that does not need to be installed. ```shell - dnf remove libevent-devel-2.1.12-5.oe2203sp3.aarch64 + dnf remove libevent-devel-2.1.12-5.oe2203SP4.aarch64 ``` 4. Perform the installation again. If a software package is missing, perform the following steps \(the missed software package in "Symptom" is used as an example\): -1. Determine the name of the software package to be upgraded \(**blivet-data-1:3.1.1-5.noarch**\) and the name of the dependent software package \(**python2-blivet-1:3.1.1-5.noarch**\) based on the error information displayed during the upgrade. +1. Determine the name of the software package to be upgraded \(**blivet-data-3.4.2-7.oe2203SP4.noarch**\) and the name of the dependent software package \(**python3-blivet-3.4.2-7.oe2203SP4.noarch**\) based on the error information displayed during the upgrade. 2. Run the **dnf remove** command to uninstall the software package that depends on the upgrade package or add the **\-\-allowerasing** parameter when upgrading the software package. - Run the **dnf remove** command to uninstall the software package that depends on the **blivet-data-1:3.1.1-5.noarch** software package. ```shell - dnf remove python3-blivet-3.4.2-7.oe2203sp3.noarch + dnf remove python3-blivet-3.4.2-7.oe2203SP4.noarch ``` - Add the **\-\-allowerasing** parameter when upgrading the software package. ```shell - yum update blivet-data-3.4.2-7.oe2203sp3.noarch -y --allowerasing + yum update blivet-data-3.4.2-7.oe2203SP4.noarch -y --allowerasing ``` 3. Perform the upgrade again. @@ -192,10 +192,10 @@ If a software package is missing, perform the following steps \(the missed softw The **python3-edk2-devel.noarch** file conflicts with the **build.noarch** file due to duplicate file names. ```shell - $ yum install python3-edk2-devel.noarch build.noarch + # yum install python3-edk2-devel.noarch build.noarch ... Error: Transaction test error: - file /usr/bin/build conflicts between attempted installs of python3-edk2-devel-202011-11.oe2203sp3.noarch and build-20220429-1.oe2203sp3.noarch + file /usr/bin/build conflicts between attempted installs of python3-edk2-devel-202011-11.oe2203SP4.noarch and build-20220429-1.oe2203SP4.noarch ``` ## Failed to Downgrade libiscsi @@ -206,10 +206,10 @@ libiscsi-1.19.0-10 or later fails to be downgraded to libiscsi-1.19.0-3 or earli ```text Error: -Problem: problem with installed package libiscsi-utils-1.19.0-10.oe2203sp3.x86_64 -- package libiscsi-utils-1.19.0-10.oe2203sp3.x86_64 requires libiscsi(x86-64) = 1.19.0-10.oe2203sp3, but none of the providers can be installed -- cannot install both libiscsi-1.19.0-3.oe1.x86_64 and libiscsi-1.19.0-10.oe2203sp3.x86_64 -- cannot install both libiscsi-1.19.0-10.oe2203sp3.x86_64 and libiscsi-1.19.0-3.oe1.x86_64 +Problem: problem with installed package libiscsi-utils-1.19.0-10.oe2203SP4.x86_64 +- package libiscsi-utils-1.19.0-10.oe2203SP4.x86_64 requires libiscsi(x86-64) = 1.19.0-10.oe2203SP4, but none of the providers can be installed +- cannot install both libiscsi-1.19.0-3.oe1.x86_64 and libiscsi-1.19.0-10.oe2203SP4.x86_64 +- cannot install both libiscsi-1.19.0-10.oe2203SP4.x86_64 and libiscsi-1.19.0-3.oe1.x86_64 - conflicting requests (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) ``` @@ -235,10 +235,10 @@ xfsprogs-5.6.0-2 or later fails to be downgraded to xfsprogs-5.6.0-1 or earlier. ```text Error: -Problem: problem with installed package xfsprogs-xfs_scrub-5.14.1-10.oe2203sp3.x86_64 -- package xfsprogs-xfs_scrub-5.14.1-10.oe2203sp3.x86_64 requires xfsprogs = 5.14.1-10.oe2203sp3, but none of the providers can be installed -- cannot install both xfsprogs-5.6.0-1.oe1.x86_64 and xfsprogs-5.14.1-10.oe2203sp3.x86_64 -- cannot install both xfsprogs-5.14.1-10.oe2203sp3.x86_64 and xfsprogs-5.6.0-1.oe1.x86_64 +Problem: problem with installed package xfsprogs-xfs_scrub-5.14.1-10.oe2203SP4.x86_64 +- package xfsprogs-xfs_scrub-5.14.1-10.oe2203SP4.x86_64 requires xfsprogs = 5.14.1-10.oe2203SP4, but none of the providers can be installed +- cannot install both xfsprogs-5.6.0-1.oe1.x86_64 and xfsprogs-5.14.1-10.oe2203SP4.x86_64 +- cannot install both xfsprogs-5.14.1-10.oe2203SP4.x86_64 and xfsprogs-5.6.0-1.oe1.x86_64 - conflicting requests ``` @@ -394,8 +394,8 @@ To add the boot parameters, open the following file: Add **rd.md=1 rd.auto=1** to the end of the line where **vmlinuz** is located. ```shell -echo 'Loading Linux 5.10.0-153.12.0.89.oe2203sp3.aarch64 ...' - linux /vmlinuz-5.10.0-153.12.0.89.oe2203sp3.aarch64 root=/dev/mapper/openeuler_openeuler-root ro rd.lvm.lv=openeuler_openeuler/root rd.lvm.lv=openeuler_openeuler/swap cgroup_disable=files apparmor=0 crashkernel=1024M,high smmu.bypassdev=0x1000:0x17 smmu.bypassdev=0x1000:0x15 rd.md=1 rd.auto=1 +echo 'Loading Linux 5.10.0-153.12.0.89.oe2203SP4.aarch64 ...' + linux /vmlinuz-5.10.0-153.12.0.89.oe2203SP4.aarch64 root=/dev/mapper/openeuler_openeuler-root ro rd.lvm.lv=openeuler_openeuler/root rd.lvm.lv=openeuler_openeuler/swap cgroup_disable=files apparmor=0 crashkernel=1024M,high smmu.bypassdev=0x1000:0x17 smmu.bypassdev=0x1000:0x15 rd.md=1 rd.auto=1 echo 'Loading initial ramdisk ...' ```