In order to implement [RFC40](https://rfc.archlinux.page/0040-license-package-sources/) and [RFC52](https://rfc.archlinux.page/0052-reuse/), we automatically ran `pkgctl license setup` on our repo packages.

See also the blog post introducing the tool: https://devblog.archlinux.page/2025/pkgctl-license/

This command has some simple heuristics to automatically generate a valid `REUSE.toml` for most of the repositories. However, in some cases (roughly 10%), it failed to do so automatically for various reasons.

There are some common scenarios:
1. Non-standard Arch-specific packaging files are included in the repo. In this case, they should just be added in the annotations array for `0BSD`.
2. The package has multiple licenses and there are patches in the repo. In that case, `pkgctl license setup` can't automatically determine the correct license to be used by upstream for the patches and a dummy license is added as a place holder. In that case, figure out the right license to use for the patches and change the `SPDX-License-Identifier` line accordingly.
3. The package isn't using an [SPDX compliant license format](https://spdx.org/licenses/). In that case, figure out what the right license is and provide it in the correct license format, then run `pkgctl license setup -f`.

To check whether a package repo is compliant, run `pkgctl license check`.

Most of the failures should be easy to fix.