net/corosync: Update to 2.4.2

[joneum]

Summary

net/corosyn: Update from 2.3.5 to 2.4.2

Changelog: https://github.com/corosync/corosync/wiki/Corosync-2.4.2-Release-Notes

PR: 219543
Submitted by: David Shane Holden (maintainer)
Approved by: xxx (mentor)
#Differential Revision: https://reviews.freebsd.org/Dxxxxx

Test Plan

net/corosync % portlint -AC
WARN: Makefile: for new port, make $FreeBSD$ tag in comment section empty, to make SVN happy.
WARN: /usr/home/joneum/dev/ports/net/corosync/distinfo: [1]: TIMESTAMP is over 30 days old
0 fatal errors and 2 warnings found.

poudriere testport:

10amd64
10i386
11amd64
11i386
12.0-CURRENT r318899 amd64
12.0-CURRENT r318400 i386

[rene]

Can you add the following dependencies? (from the poudriere log):

> Running Q/A tests (stage-qa)

Error: /usr/local/lib/libtotem_pg.so.5.0.0 is linked to /usr/local/lib/libplds4.so from devel/nspr but it is not declared as a dependency
Warning: you need LIB_DEPENDS+=libplds4.so:devel/nspr
Error: /usr/local/lib/libtotem_pg.so.5.0.0 is linked to /usr/local/lib/libplc4.so from devel/nspr but it is not declared as a dependency
Warning: you need LIB_DEPENDS+=libplc4.so:devel/nspr
Error: /usr/local/lib/libtotem_pg.so.5.0.0 is linked to /usr/local/lib/libnspr4.so from devel/nspr but it is not declared as a dependency
Warning: you need LIB_DEPENDS+=libnspr4.so:devel/nspr

[joneum]

Fix dependencies from Maintainer

[joneum]

Expamle, here a new log: http://joneumbox.org/data/12i386-ports/2017-05-29_09h42m28s/logs/corosync-2.4.2.log

[tz]

Did you check if net/pacemaker still works?

[tz]

pacemaker doesn't build after applying the patch. But i didn't check if it builds without. Please have a look at it Jochen!

It is always a good idea to check if ports depending at the one your working on are still building. Especially if you see files ending with .so. This often requires a bump of PORTREVISION.

[joneum]

Yoe mean, testing all updates in VB, when updating LIB_DEPENDS?

[tz]

In D10971#227267, @joneum wrote:

Yoe mean, testing all updates in VB, when updating LIB_DEPENDS?

No. For an easy explanation look at:
http://www.freshports.org/net/corosync

There is a section "This port is required by:". You should test if all ports listed there still build.

[joneum]

In D10971#227272, @tz wrote:

In D10971#227267, @joneum wrote:

Yoe mean, testing all updates in VB, when updating LIB_DEPENDS?

No. For an easy explanation look at:
http://www.freshports.org/net/corosync

There is a section "This port is required by:". You should test if all ports listed there still build.

Hi Thorsten,

Thanks for this. This is very helpful for me. I will remember it, and also these in poudriere test. Such tips are welcome. Thank you for your help

[joneum]

I will wait to test this update. This port needs net/pacemaker, and thre os an update too. But the Maintainer have Problemes with it, see PR 219544. When this update works too, i will test it again.