Skip to content
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

Error from reuse 0.11.0 consuming a .rtf file #253

Closed
oddhack opened this issue Aug 17, 2020 · 2 comments
Closed

Error from reuse 0.11.0 consuming a .rtf file #253

oddhack opened this issue Aug 17, 2020 · 2 comments

Comments

@oddhack
Copy link

oddhack commented Aug 17, 2020

I have a .rtf file that's causing 'reuse lint' to throw an error attempting to parse it. However, the license information is entered in the file, and looks correct when viewing it in e.g. Libreoffice. While it's understandable that the REUSE tool would not read every possible documentation format, having it throw an error attempting to read .rtf suggests an underlying problem in whatever component consumes this type of file.

For ease of reproduction, I've created a minimal case repo here: https://github.com/oddhack/reuse-error . More information is in the repository README.md.

@oddhack
Copy link
Author

oddhack commented Aug 17, 2020

Also, it's apparently impossible to work around this with the .reuse/dep5 file - even if the license information is duplicated there, REUSE still tries and fails to read the .rtf file, and will not pass lint as a result. It is possible to put the license information into a .license file, so apparently the order of processing is .license -> file itself, if failed -> dep5, if not found in file. Is that true, and intentional?

@mxmehl
Copy link
Member

mxmehl commented Oct 23, 2020

Yes, this is an ongoing issue. I'd close as duplicate of #246 however, where we discuss the problem of precedence. I do hope we can fix this soon.

@mxmehl mxmehl closed this as completed Oct 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants