【22.03-LTS-SP2 round2】hive在22.03-LTS-SP2的版本低于22.03-LTS-SP1，导致从22.03-LTS-SP1向22.03-LTS-SP2升级失败

【环境信息】
软件信息：
1） OS版本及分支:openEuler 22.03 (LTS-SP1)
2） 内核信息:openEuler 5.10.0-136.12.0.86.oe2203sp1

【操作步骤】
1、yum provides hive
![输入图片说明](https://foruda.gitee.com/images/1685699495598597040/808144d5_8572434.png "屏幕截图")

【预期结果】22.03-LTS-SP2的版本高于22.03-LTS-SP1
【实际结果】22.03-LTS-SP2的版本低于22.03-LTS-SP1

【附件信息】
repo：
[SP1_everything]
name=SP1_everything
baseurl=https://repo.openeuler.org/openEuler-22.03-LTS-SP1/everything/$basearch
enabled=1
gpgcheck=1
gpgkey=https://repo.openeuler.org/openEuler-22.03-LTS-SP1/everything/$basearch/RPM-GPG-KEY-openEuler

[SP1_EPOL]
name=SP1_EPOL
baseurl=https://repo.openeuler.org/openEuler-22.03-LTS-SP1/EPOL/main/$basearch/
enabled=1
gpgcheck=1
gpgkey=https://repo.openeuler.org/openEuler-22.03-LTS-SP1/OS/$basearch/RPM-GPG-KEY-openEuler

[SP1_update]
name=SP1_update
baseurl=https://repo.openeuler.org/openEuler-22.03-LTS-SP1/update/$basearch/
enabled=1
gpgcheck=1
gpgkey=https://repo.openeuler.org/openEuler-22.03-LTS-SP1/OS/$basearch/RPM-GPG-KEY-openEuler

[SP1_EPOL_update]
name=SP1_EPOL_update
baseurl=https://repo.openeuler.org/openEuler-22.03-LTS-SP1/EPOL/update/main/$basearch/
enabled=1
gpgcheck=1
gpgkey=https://repo.openeuler.org/openEuler-22.03-LTS-SP1/OS/$basearch/RPM-GPG-KEY-openEuler

[SP2_everything]
name=SP2_everything
baseurl=http://121.36.84.172/dailybuild/EBS-openEuler-22.03-LTS-SP2/rc2_openeuler-2023-05-25-18-39-41/everything/$basearch/
enabled=1
gpgcheck=1
gpgkey=http://121.36.84.172/dailybuild/EBS-openEuler-22.03-LTS-SP2/rc2_openeuler-2023-05-25-18-39-41/everything/$basearch/RPM-GPG-KEY-openEuler

[SP2_EPOL]
name=SP2_EPOL
baseurl=http://121.36.84.172/dailybuild/EBS-openEuler-22.03-LTS-SP2/rc2_openeuler-2023-05-25-18-39-41/EPOL/main/$basearch/
enabled=1
gpgcheck=1
gpgkey=http://121.36.84.172/dailybuild/EBS-openEuler-22.03-LTS-SP2/rc2_openeuler-2023-05-25-18-39-41/OS/$basearch/RPM-GPG-KEY-openEuler

src-openEuler/hive

Content Risk Flag

Comments (4)

src-openEuler/hive .gitee-modal { width: 500px !important; }

Content Risk Flag