But if I guard against sle_version < 160000 then a user that upgrades from SLE 15 that has not run "zypper up", granted this is not really a supported case, will probably run into an upgrade problem. The Python upgrade that would happen in such a scenario would try to remove the python3.6 sitelib but the boto3|botocore|s3-transfer packages would have stuff there that they don't want to let go off. The user would, I think not be provided with a good alternative. I'd expect some weird behavior. Anyway, I agree we have to keep an eye on this when version 16 gets created but I'd rathre not speculate at this time. Between here and there we'll have a few more version updates and possibly other changes. If it turns out we are going for a different behavior with 16 or upgrade works fine without the Obsoletes: the additional guard can be added then.