On Sunday, 17 April 2016 5:25:55 PM AEST Sergei Golovan wrote:
> Well, I guess you understand that removing the susceptible files from
> the yaws package will not fix the bug you reported.

One have to begin somwhere...


> So, if you're not really interested in fixing this just tell me,

I'll file those bugs, it'll just take time...


> and I'll just close it.

This is not the option. DFSG compliance is not optional. You really have a 
choice between moving package to non-free or removing non-free files.

Situation is quite straightforward so I don't see why would you wait for 
feedback from other maintainers before fixing the problem.
Though it would be interesting to get their feedback. :)


> > I'm quite sceptical about this as I don't see many options here as
> > I doubt we would be able to find compromise between DFSG and non-free
> > licensing terms...
> 
> Maybe, maybe not. The authors' intention is what matters.

Than I suggest you to consider reporting the problem upstream. :)

-- 
All the best,
 Dmitry Smirnov.

---

What is the truth, but a lie agreed upon.
        -- Friedrich Nietzsche

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to