You are not logged in.
Hi everyone,
I need dotnet-sdk on my system, but unfortunately, it has a dependency on openssl-3. I do however already have openssl installed as a dependency of a lot of other packages. I noticed that the versions of openssl in the openssl and openssl-3 packages are similar. I also noticed that some packages instead depend on libssl, allowing me to pick either, but most depend on openssl. Is this possibly an error? If not, how can I solve this?
I also noticed that openssl-3 does not conflict openssl. I think at least this is an error.
Offline
Yes, seems like it: https://gitlab.archlinux.org/archlinux/ … 89624b7e78
Presumably dotnet doesn't support openssl 4.1.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I also noticed that openssl-3 does not conflict openssl. I think at least this is an error.
Why do you think that is an error. openssl-3 is the compat package for the v3 libs only. It does not provide the openssl version 4 API/ABI and conflicting would trigger `pacman` to either fail the transaction or remove `openssl` which would break your installation. The openssl maintainer rejected my provided patches to use dotnet with openssl 4 like their rejections of all my other proposals.
Offline
Konzertheld wrote:I also noticed that openssl-3 does not conflict openssl. I think at least this is an error.
Why do you think that is an error.
Because the packages can't be installed in parallel anyway, since some files are written to the same path. So they do conflict anyway - not marking them as conflicting just prevents pacman from handling the conflict properly.
Offline
Because the packages can't be installed in parallel anyway, since some files are written to the same path. So they do conflict anyway - not marking them as conflicting just prevents pacman from handling the conflict properly.
That would have prevented dotnet-sdk from being built against openssl-3 as `makepkg` would have been unable to uninstall openssl-3 needed for the rebuild. So I suspect you are doing a partial update or have untracked files causing the issue. If you can demonstrate the two versions do conflict report that on Arch's gitlab as a packaging issue.
Offline
$ yay -Qs openssl
local/lib32-openssl 1:4.1.0-2
The Open Source toolkit for Secure Sockets Layer and
Transport Layer Security (32-bit)
local/libevent 2.1.13-3
Event notification library
local/openssl 4.1.0-1
The Open Source toolkit for cryptography and Transport
Layer Security
local/openssl-3 3.5.9-2
The Open Source toolkit for cryptography and Transport
Layer Security; Version 3.5 LTS
local/pkcs11-helper 1.31.0-2
A library that simplifies the interaction with PKCS11
providers for end-user applications using a simple API and
optional OpenSSL engine
local/pkcs11-provider 1.3.0-2
A pkcs#11 provider for OpenSSL 3.0+
local/xmlsec 1.3.13-2
XML Security Library is a C library based on LibXML2
[main@main ~]$you were saying?
Offline
Because the packages can't be installed in parallel anyway, since some files are written to the same path.
The openssl-3 PKGBUILD moves some files to ensure it doesn't conflict with openssl 4 .
This is standard practice for arch packages if multiple versions need to coexist.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline