After digging for a while i found https://bugs.launchpad.net/ubuntu/+source/samba/+bug/302004
I see that in a case of Samba security update wich breaks API the module's wanna-build may fail, a strict versionned dependency of the installed module can block the upgrade, while too loose dependency can tumble down the whole upgraded Samba instance since ABI changed. Do you think, guys, we should really expect these problems? Also, i don't see how it could be resolved if i just import the headers set into my module as you've suggested. I'd still be able to freeze any Samba security upgrade or tumble user's server even without samba-headers in Debian, right? If you consider the vulnerability window between publishing a Samba security upgrade and following (uncontrolled by you) module upgrade, then merging the module in the Samba tree probably would be the only way to develop such module package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
