10000 Generate debian/copyright files · Issue #926 · fsfe/reuse-tool · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Generate debian/copyright files #926

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

Closed
koalo opened this issue Feb 29, 2024 · 5 comments
Closed

Generate debian/copyright files #926

koalo opened this issue Feb 29, 2024 · 5 comments

Comments

@koalo
Copy link
koalo commented Feb 29, 2024

Hi,
is there any easy way to reuse ( ;-) ) the copyright information processed by reuse to generate debian/copyright files (https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/) so we do not have to maintain that file manually?

Thanks,
Florian

@BigBlueHat
Copy link
Contributor

I use the "missing license" output from the console and then make one by hand. Certainly the data's there. Harder problem would be managing it long term (and finding unused paths, etc.).

Would definitely be handy, though!

@koalo
Copy link
Author
koalo commented Mar 1, 2024

What do you mean with "managing it long term"? I would expect you could just regenerate the copyright file for every release and avoid making manual changes to that file. Or do I overlook something?

@carmenbianca
Copy link
Member

I'm not sure this will be built in, but you could very easily run reuse lint --json to get all the data needed to generate a debian/copyright file. It will be very terse (without any globs), but complete.

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 Mar 21, 2025
Copy link

Since there hasn't been any recent activity after the last message, we're going to go ahead and close this issue. Feel free to reopen this and remove the labels stale and unresolved if it's urgent.

We truly appreciate your contributions and engagement!

Thank you and happy hacking!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
0