On 17:07 Sun 01 Apr , Paul Wise wrote: <snipped> > Do the usual things for embedded code copies: Umm.. not clear. By saying package in the usual way do you mean that I include modified library code inside packages? Policy 4.13 says we shouldn't include convenience copies unless its intended to use this way (As in gnu build tools). > > Take a look at policy and this wiki page: > > http://wiki.debian.org/EmbeddedCodeCopies > > Notify the security team so they can fix any duplicate security issues > caused by the duplicated code. How this should be done? I mean the way to communicate with security team is there a standard procedure like filing a bug against some package or just mailing list communication. Is there a page describing the method. (Above page only gives some information on which package already does this) > > Work with the relevant upstreams to unfork things. As I said in reply to Russ's mail either upstream doesn't exists or the modification done by friendica developers isn't a generic so that we can provide patch to upstream (As in case of tinymce) So I'm really not sure how can I get this unforked. Best Regards -- Vasudev Kamath
Attachment:
signature.asc
Description: Digital signature