Maximilian Huber

in https://datatracker.ietf.org/doc/html/rfc3986#section-3.4 I read: > However, as query components are often used to carry identifying information in the form of "key=value" pairs and one frequently used value is a reference...

the specification references rfc3986 and not rfc3296: https://github.com/package-url/purl-spec/blob/master/PURL-SPECIFICATION.rst#a-purl-is-a-url and that contains an example with an unescaped `/` in the query parameters: ``` ftp://cnn.example.com&[email protected]/top_story.htm ``` EDIT: i misread that example :smile:

> Signed-off-by: vagrant [[email protected]](mailto:[email protected]) That is not a valid sign-off, please fix that and use your name

other patches start with numbers in the beginning, to make the sorting clear

I can either drop the requirement for signed commits or drop "Require linear history". Or you could rebase manually and sign it yourself.

The goal is to have direct SPDX JSON import, yes. But that is also indirectly already possible via https://github.com/opossum-tool/opossum.lib.hs, which allows you to convert SPDX 2.2 JSON to Opossum input...

~~And there is also https://github.com/tern-tools/tern/issues/1064~~

No, not yet, sorry. Still the same problems with the nixos+cabal setup due to the usage of the homedir by another OS.

### Testing `nix-shell`: $ nix-shell [nix-shell:~vgrep]$ stack build dlist-0.7.1.2: using precompiled package data-default-class-0.0.1: using precompiled package [...] Registering vgrep-0.2.0.0... Completed 60 action(s). [nix-shell:~vgrep]$ stack exec vgrep test ./ works for...

I have modified the README and removed the nix files