nothing provides 'libopenssl1_0_0' needed by the to be installed dotnet-runtime-deps-8.0-8.0.17-1.x86_64

[dirkmueller]

Description

this is a continuation of #113346

with the release of runtime-deps 8.0.17 the previous "libopenssl1_0_0" issue is back. it should require libopenssl3 or libopenssl1_1, but not 1_0_0.

Reproduction Steps

$ podman  run -it registry.suse.com/bci/bci-base:15.6
# zypper ar -f https://packages.microsoft.com/sles/15/prod/ dotnet
# zypper in dotnet-runtime-8.0

Expected behavior

it succeeds installing

Actual behavior

Problem: 1: nothing provides 'libopenssl1_0_0' needed by the to be installed dotnet-runtime-deps-8.0-8.0.17-1.x86_64
 Solution 1: do not install dotnet-runtime-8.0-8.0.17-1.x86_64
 Solution 2: break dotnet-runtime-deps-8.0-8.0.17-1.x86_64 by ignoring some of its dependencies

Regression?

yes, this worked in 8.0.16.

Known Workarounds

No response

Configuration

No response

Other information

No response

[dirkmueller]

@NikolaMilosavljevic or @jkoritzinsky - this was fixed via a runtime-deps update in 8.0.16 but 8.0.17 is going back to 1.0.0 openssl which is unavailable in standard distributions. any chance to get this addressed? we have users asking for the 8.0.17 update and we can not ship it in this state.

[jkoritzinsky]

@NikolaMilosavljevic any ideas how this regressed between 8.0.16 and 8.0.17?

[NikolaMilosavljevic]

@NikolaMilosavljevic any ideas how this regressed between 8.0.16 and 8.0.17?

That's very odd - let me check.

[dirkmueller]

over night a new runtime deps package has been published which flips from libopenss3 back to libopenss1_1:

Problem: 1: nothing provides 'libopenssl1_1' needed by the to be installed dotnet-runtime-deps-9.0-9.0.6-1.x86_64

is this an intentional change? previously it was requiring libopenssl3 which worked fine. it is not as bad as requiring openssl1_0 but libopenss3 is the recommended openssl version for sle15 and openSUSE platforms because it provides FIPS-140-3

[NikolaMilosavljevic]

Thanks @dirkmueller - the team is working on resolving these issues with publishing to PMC.

[NikolaMilosavljevic]

@dirkmueller regarding 9.0.6 - openSUSE package was incorrectly published to SLES feed. That was corrected last night. We have only updated the openSUSE libopenssl dependency with new version, with f488c54

[dirkmueller]

@NikolaMilosavljevic ah, that's very confusing. so you're saying sle15 should be using openssl 1.1 even though openssl 3 is the default and 1.1 is only in legacy?

see https://www.suse.com/support/kb/doc/?id=000019582 for an overview

[NikolaMilosavljevic]

@dirkmueller I concur that this is not very clear, and I don't have the full understanding of the reasons behind these decisions. @leecow @richlander @jkoritzinsky do we know if we could update sles DEPS package to use libopenssl3 instead of libopenssl1_1? This is for .NET 9.