Skip to content

Update system perl #45

Merged
merged 8 commits into from
Jan 31, 2019
Merged

Update system perl #45

merged 8 commits into from
Jan 31, 2019

Conversation

donald
Copy link
Contributor

@donald donald commented Jan 31, 2019

Add LWP::Protocol::https to system perl, so nachtwaechter can check https hosts.
All other updates are by the way.

Already installed on distmaster

Create build file with

    cp perl-5.24.1-1.build.sh perl-5.28.1-0.build.sh
This patch no longer applies and doesn't seem to be needed. Remove it.
Update package Donald from 1.04 to 1.05 and update download url. I'm not
proud of it, but clusterd depends on it.
LWP::Protocol::https is what we needed in the first place, so add it. It
requires Net::SSLeay. One test of Net::SSLeay hangs forver with openssl
1.1.1a (which is propably a error int the test not in openssl), so
install it explicitly without tests.
net-snmp needs to be updated, because version 5.7.4 doesn't compile with
openssl1.1.1a.

Do it.
Support test build into /dev/shm.
Parallel build seems to fail sometimes. Avoid that. Use -j 1 to override
MAKEFLAGS.
@pmenzel pmenzel merged commit 7f14b16 into master Jan 31, 2019
@thomas
Copy link
Contributor

thomas commented Feb 1, 2019

Hi Donald,
My observation was that Net::SSLeay-1.85 failed to build (not only the tests) correctly against the updated libopenssl, There is already a devel version 1.86 on cpan that copes with it.

This is why there was already a Perl 5.28.1-0 Build, that I've postponed to create 'caus I dont wanted to have a libopenssl 1.02something in the package (as with the hapless perl 5.18 package, where I went this way)

@donald
Copy link
Contributor Author

donald commented Feb 1, 2019

Strange. I've removed the one blocking test ( discussions by other people suggest, that this test was badly written and just happened by chance to work on previous versions ) and all other tests pass. And nachtwaechter is in fact actually using it.

@thomas
Copy link
Contributor

thomas commented Feb 1, 2019

Sounds pretty convincing, so I guess the troubles with the 'vintage' 5.18 build had additional reasons, I'll take a look next week.

Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants