Bug #5776
closed
We should not build Fusion with SSL support as we do not use it and it breaks Bundled OpenSSL builds
Added by Matthieu CERDA about 10 years ago.
Updated over 9 years ago.
Description
We build Perl / Fusion with SSLeay support, which is completely useless as we only do local inventories.
It breaks Bundled OpenSSL builds on machines without openssl-devel/libssl-dev.
We should not build this SSLeay module.
- Project changed from Rudder to 34
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-packages/pull/522
- Pull Request changed from https://github.com/Normation/rudder-packages/pull/522 to https://github.com/Normation/rudder-techniques/pull/560
[Comment removed by original author with reason: comment in wrong ticket]
- Pull Request changed from https://github.com/Normation/rudder-techniques/pull/560 to https://github.com/Normation/rudder-packages/pull/522
Can you please clarify this ticket? What breaks ? How does it not work? What are the symptoms, error messages?
Since we introduced bundled OpenSSL recently, this ticket MUST be related to the ticket that introduced that. Please clarify.
This is related to #5147, where we introduced bundled OpenSSL builds for old/unsupported OSes.
Since as a result, we stopped requiring OpenSSL development headers, Fusion stopped building correctly as by default it tries building the SSLeay module. This module is used during fusion agent / server communication to establish a SSL / TLS channel (the SSLeay modules requires OpenSSL headers)
Since we do not use Fusion like this (only local report generation, handled by Rudder agent afterwards), this module is useless.
Therefore, this PR stops perl-prepare.sh from building this module.
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|commit:73fa65fa0a04252d3b1ddb2c54fea82444929029.
Applied in changeset rudder-packages|commit:3133a3f3cc5f66b5919979df691df498b1e924c1.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.5, which was released today (16/12/14)
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF