On Thu, Oct 22, 2015 at 12:45:49AM +0200, Jonas Smedegaard wrote: > Source: asterisk > Severity: normal > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Asterisk supports linkage against Corosync, but that seems deliberately > avoided in the Debian packaging. > > I wonder why it was avoided - changelog entry for 1:13.0.0~dfsg-3 says > "Remove corosync support: doesn't work" but doesn't really explain what > didn't work. > > If it was bug#771432 then that bug seems to only suggest disabling the > module by default, not avoiding building the module altogether (might > work fine when properly configured). Also, if it is that issue, then > that bugreport should probably be closed, referencing that release. > > Perhaps the seemingly major cleanup changes to Corosync 2.3.5-2 solves > the reviously experienced issues?
"Doesn't work" is #771432 which I didn't have time to properly check. But also the fact that it is now disabled by default in the upstream configuration. Do you use it? If there's a need for it, I'll try to take the time to research it. -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il | | a Mutt's tzaf...@cohens.org.il | | best tzaf...@debian.org | | friend
