Hi, I tried some local package build for Leap 15.3 and was quite surprised where packages are coming from: fetching packages for 'SUSE:SLE-15:Update': | Elapsed Time: 0:00:09 fetching packages for 'SUSE:SLE-15-SP2:Update': | Elapsed Time: 0:00:04 fetching packages for 'SUSE:SLE-15-SP3:GA': | Elapsed Time: 0:00:26 fetching packages for 'SUSE:SLE-15-SP2:GA': | Elapsed Time: 0:00:02 fetching packages for 'SUSE:SLE-15:GA': | Elapsed Time: 0:00:01 fetching packages for 'SUSE:SLE-15-SP1:Update': | Elapsed Time: 0:00:02 fetching packages for 'openSUSE:Leap:15.3': | Elapsed Time: 0:00:00 -> Is this due to the current state of development, or will we continue to ses the different package sources? Next surprise when it comes to package verification: Verifying integrity of cached packages using keys from SUSE:SLE-15:Update, SUSE:SLE-15:GA, SUSE:SLE-15-SP3:GA, SUSE:SLE-15-SP2:Update, SUSE:SLE-15-SP2:GA, SUSE:SLE-15-SP1:Update, SUSE:SLE-15-SP1:GA, openSUSE:Leap, Application:ERP, openSUSE warning: /var/tmp/osbuild-packagecache/openSUSE:Backports:SLE-15-SP3/standard/ noarch/python3-simpleeval-0.9.10-bp153.1.24.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 65176565: NOKEY /var/tmp/osbuild-packagecache/openSUSE:Backports:SLE-15-SP3/standard/noarch/ python3-simpleeval-0.9.10-bp153.1.24.noarch.rpm : public key not available (and some 12-15 more packages w/o public key) -> The keys for Backports seem to be missing. I guess they need to be added in pkgconfig of Leap 15.3? (and use --no-verify for the time being) Cheers Axel