Sebastian Schuberth

Again see the [docs](https://oss-review-toolkit.org/ort/docs/configuration/ort-yml#curations), it's in the big "NOTE" box at the top: You need to enable the `enableRepositoryPackageCurations` setting in `config.yml`. In the GitHub action content, it's more convenient...

No, sorry, I'm not aware of anyone actively working on this. However, we might be able to raise the priority for this, depending on how some discussions go.

I'm still getting the exact same error on Windows 11, directly after starting the app from the start menu. And yes, and older version of the app was present before....

> Installing 2.4.1 a 2nd time (installing over existing 2.4.1) solved the issue. I can confirm that this also worked for me 👍🏻

As [noted on Slack](https://oss-review-toolkit.slack.com/archives/C9NNJ54B1/p1750095064900069?thread_ts=1749308584.419699&cid=C9NNJ54B1), third-party tools are provided to ORT via its Docker image. Either download the scanner binary during Docker build time, or build it from source and copy...

Yes, that looks useful from the output perspective, but on the input side it seems to only accept concrete GAV coordinates for a single artifact. What I'd be interested in...

I see, thanks. So I guess requesting such an example as I did is out of scope, as it would probably need to contain more "glue code" than code for...

> @sschuberth failing tests seem unrelated. The "Unable to create proxy for sealed class" failures in `org.ossreviewtoolkit.scanner.ScannerTest` are real. I guess the problem is that nothing currently implements the `LocalProvenance`...

> Most of which are for `KnownProvenance` input, so I can not default to `UnknownProvenance` behavior. Can't you "cheat" a bit by first limiting some / all `KnownProvenance` cases to...

Commit message: > It is defined by its local directory path only. We should probably say "absolute" / "canonical" / "real" path, and do the implementation accordingly. > it the...