8000 Failure to parse files with mac line endings (CR line terminator) · Issue #742 · fsfe/reuse-tool · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Failure to parse files with mac line endings (CR line terminator) #742

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.

Sign up for GitHub

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

Jump to bottom
Open
tenzap opened this issue May 16, 2023 · 3 comments
Open

Failure to parse files with mac line endings (CR line terminator) #742

tenzap opened this issue May 16, 2023 · 3 comments
Labels
bug Something isn't working stale

Comments

@tenzap
Copy link
tenzap commented May 16, 2023

This file has mac line endings (CR line terminator)

https://raw.githubusercontent.com/qt/qtbase/dev/tests/auto/tools/moc/os9-newlines.h

$ file os9-newlines.h 
os9-newlines.h: ASCII text, with CR line terminators

reuse fails parsing it

$ reuse spdx                
reuse.project - WARNING - could not find supported VCS
};' inline void testSlot() {}bjectrse 'LicenseRef-Qt-Commercial OR GPL-3.0-only WITH Qt-GPL-exception-1.0
reuse.project - ERROR - 'os9-newlines.h' holds an SPDX expression that cannot be parsed, skipping the file

If I run mac2unix on it, then afterwards reuse will work correctly.
@mxmehl mxmehl added the bug Something isn't working label May 16, 2023
@kkoehne
Copy link
kkoehne commented Feb 2, 2024

As the name suggests, the file is intentionally using non-native file endings.

Note that even adding the path to .gitignore doesn't block reuse from parsing it (and showing above warning). Is this worth a separate bug?

@github-actions GitHub Actions
Copy link

Thank you for your time and contributions! Unfortunately, this issue has been inactive for quite a while which means we probably can't manage the time to deal with it. That's why we're marking it as stale. We want to keep things tidy and focus on active discussions, but we’re always happy to revisit if this is still relevant!

If you’d like to keep this open, please add a comment to let us know and remove the label stale. Otherwise, this issue will most likely be automatically closed soon.

@github-actions github-actions bot added the stale label May 18, 2025
@tenzap
Copy link
Author
tenzap commented May 18, 2025

Keep open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kkoehne @mxmehl @tenzap
0