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. I wonder whether merging the asterisk and > asterisk-opus package using the 3.0 package format's features for > additional source component tarballs might not be a more appropriate > packaging strategy. Meanwhile, this is clearly broken as it cannot be > installed.
Thanks for reporting! The tight dependency is build-time only: Generally a BinNMU is adequate. I disagree that this is a suitable use of the multi-source feature of the dpkg source format: The two sources have independent release rhythms, and updating the smaller part (asterisk-opus) should not require rebuilding the bigger one (asterisk). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
