-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Includes possible non-free content #27
Comments
So just to make sure, this is in reference to the web content used for test cases that we have? Would something like moving the tests out of the actual package help/hurt the cause? We could try to 'make up' content that fits the test case, but it's obviously important that once we hit a bug it's easy/best to get that content and make sure we parse it correctly. |
On Sat, Apr 12, 2014 at 10:36:24AM -0700, Rick Harding wrote:
Making up contents would be ideal (because it means I can still run Cheers, Jelmer |
Ok cool, I'll try to pull the tests out as that'll be fast and unblock you and then can see if we can mimic the issue the site gave us and replicate it in a 'generic' way as follow ups. |
I've uploaded 0.1.20 that does not include the tests in the source build. We'll keep that as a pure development tool for now and use in CI while we try to find a better way to generate test files that aren't copyrighted material. |
Thanks! |
breadability ships a number of documents for testing that are possibly restricted because they are copyrighted and not BSD-licensed.
Would it be possible to use alternatives, or possibly fetch them during the test process so they don't have to be distributed?
This makes it harder to package breadability for Debian.
The text was updated successfully, but these errors were encountered: