Hi,
On Mon, Aug 21, 2017 at 12:07:40AM +0200, Jonas Smedegaard wrote:
> Hi Sam,
>
> Quoting Sam Hartman (2017-08-20 23:24:25)
> > The asterisk package in unstable provides
> > asterisk-1fb7f5c06d7a2052e38d021b3d8ca151
> >
> > but asterisk-opus depends on asterisk-fa819827cbff2ea35341af5458859233
> >
> > It looks like this is a system that is very locked to the specific
> > build of asterisk.
Asterisk calculates a checksum of some of its build properties at build
time. This checksum is built into the module loader and normally modules
fail to load if the version of Asterisk at run-time is different than
the one used to build it.
Normally the checksum does not change. In fact, the rules file of the
Debian packaging includes a copy of it and checks that it didn't change.
Some time in the 13 cycle the calculation of the checksum changed to
avoid including some irrelevant functions, and thus the checksum is
different from the Stable version.
> The tight dependency is build-time only: Generally a BinNMU is adequate.
Right.
--
Tzafrir Cohen
+972-50-7952406 mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com
