Bug 1221036

Summary: Leap15.6 migration sles15sp6 got package conflict error: Package-hub-release conflict with openSUSE -build-key
Product: [openSUSE] openSUSE Distribution Reporter: yutao wang <yuwang>
Component: Upgrade ProblemsAssignee: Lubos Kocman <lubos.kocman>
Status: CONFIRMED --- QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: lubos.kocman, meissner, mlin, wolfgang.engel
Version: Leap 15.6Flags: wolfgang.engel: needinfo? (lubos.kocman)
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Leap 15.5   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: yast 2 log file.

Description yutao wang 2024-03-06 09:13:27 UTC 
Created attachment 873251 [details]
yast 2 log file.

Hardware: x86_64
Software: opensuse-15.6-x86_64-623.2-textmode@64bit.qcow2 migration to SLE-15-SP6-Online-x86_64-Build62.1-Media1.iso
*****************************************************************
Test steps:
1. Install leap15.6 with opensuse-15.6-x86_64-623.2-textmode@64bit.qcow2
2. Did zypper patch
3. zypper in yast-migration-sle
4. Command 'yast2 migration_sle'
During migration got error message:
Refer: https://openqa.suse.de/tests/13724387#step/yast2_migration/10
PackageHub-Release conflict with openSUSE-build-key
Comment 1 Wolfgang Engel 2024-03-19 12:57:25 UTC 
This issue also occurs on migration from Leap 15.5 to SLE-15-SP5

Could we just add obsoletes openSUSE-build-key in PackageHub-release package ?
Are the additional keys provided in the openSUSE-build-key package wanted on SLE-15-SP5 ?
Comment 2 Lubos Kocman 2024-03-19 13:09:12 UTC 
I think that makes sense since you provide it already.

Keep in mind that it should probably work the other way too.

So if you'd migrate openSUSE-> SLES -> openSUSE (System AG does it as a sort of a cleanup) I guess it would work but person couldn't install any future update of openSUSE-build-key, nor PH release as the PH channel is not avialable.

We could document that one or we could e.g. obsolete the previous relate of PacakgeHub-release from the build-key. Something like that.