Bug#571635: Fragile API
On Sunday 28 February 2010 00:21:43 you wrote: Development doesn't need to happen inside the Samba tree, but for distribution as part of Debian, yes. Thus, when i said about the Samba Team point of view (if not about it's official policy), i was practically right. To summarize your and JV's advises, there is no way to add a Samba VFS module package to Debian except having the module's source in the upstream Samba itself. If so, the bug should be resolved and i'd move to Samba devel lists. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571635: Fragile API
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
Bug#571635: Fragile API
On Sat, Feb 27, 2010 at 10:53:36PM +0300, Al Nikolov wrote: 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? Er, this bug report only mentioned that you wanted the headers to be available in a binary package in the archive, not that you intended to get separate Samba VFS module packages included in Debian. I don't think the latter is supportable, for all the stated reasons, and would work with the ftp team to keep such packages out of testing/stable. 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. Development doesn't need to happen inside the Samba tree, but for distribution as part of Debian, yes. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
