OctopusDeploy / OctopusTentacle

| Public | The secure, lightweight, cross-platform agent for Octopus Server which turns any computer into a worker or deployment target for automated deployments and operations runbooks.
https://octopus.com
Apache License 2.0
11 stars 16 forks source link

libcrypto.so.3 broken tentacle updates #1023

Closed tivanov-qb closed 1 month ago

tivanov-qb commented 1 month ago

Team

What happened?

this PR: https://github.com/OctopusDeploy/OctopusTentacle/pull/1021/files has caused issues while trying to update tentacle package to latest version using yum update for example

Reproduction

try running yum update with having Package tentacle.x86_64 0:8.2.2297-1 or try installing latest tentacle package

Error: Package: tentacle-8.2.2319-1.x86_64 (tentacle) Requires: libcrypto.so.3()(64bit)

Error and Stacktrace

No response

More Information

No response

Workaround

using --skip-broken

tivanov-qb commented 1 month ago

@benPearce1 tagging you as i see the pr was opened and merged by you. could you please advise how we fix this on amazon linux 2 machines ? also @hnrkndrssn

tivanov-qb commented 1 month ago

@benPearce1 i see there is a workaround, but i hope there would be "final fix" implemented ?

benPearce1 commented 1 month ago

@tivanov-qb thanks for letting me know. I will take a look at this as soon as possible.

benPearce1 commented 1 month ago

@tivanov-qb I have confirmed that this is broken on Amazon Linux 2, which only provides libcrypto.so.10()(64bit) out of the box.

tivanov-qb commented 1 month ago

@benPearce1 is there a plan to fix this or workaround needs to be used ?

benPearce1 commented 1 month ago

@tivanov-qb Yes there will be a fix for it. There are two possible solutions I am investigating, boolean operators and macros.

The boolean operators require RPM 4.13, Amazon Linux 2 only has 4.11 installed out of the box.

The macro solution is awkward to implement because we are currently using fpm to build the RPM and DEB packages and it doesn't support macros directly.

benPearce1 commented 1 month ago

@tivanov-qb I have rolled back the previous change, which will fix this, available in version 8.2.2337

tivanov-qb commented 1 month ago

thank you, Ben