darktable-org / darktable-org/darktable

License Issue

Open
#19,954 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

no-issue-activity
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Is there an existing issue for this?
  • I checked and did not find my issue in the already reported ones
Describe the bug

ashift_lsd.c lists its license as both AGPL and GPL. Can we get the incorrect license removed?

Steps to reproduce

Go to https://github.com/darktable-org/darktable/blob/release-4.8.1/src/iop/ashift_lsd
See that there are 2 licenses in the file.

Expected behavior

No response

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

4.8.1

What OS are you using?

Linux

What is the version of your OS?

Linux

Describe your system

No response

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open src/iop/ashift_lsd.c from the release-4.8.1 source and inspect its license header. Remove the incorrect license designation so the file lists only the intended license, then verify that no conflicting license remains.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
documentation
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.