Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#74120 - [mingw-w64-gcc][aarch64-linux-gnu-gcc] Possibly wrong license
Attached to Project:
Community Packages
Opened by Marius (Martchus) - Tuesday, 15 March 2022, 00:19 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 03 May 2023, 05:36 GMT
Opened by Marius (Martchus) - Tuesday, 15 March 2022, 00:19 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 03 May 2023, 05:36 GMT
|
DetailsDescription:
Shouldn't the license of `gcc` and `mingw-w64-gcc` be `GPL3` according to https://gcc.gnu.org/onlinedocs/libstdc++/manual/license.html. The Wiki (https://wiki.archlinux.org/title/PKGBUILD#license) explicitly distinguishes between "GPLv2 or any later version" and "GPLv3 or any later version" and I suppose the latter would be more accurate. |
This task depends upon

- Field changed: Percent Complete (100% → 0%)
Thanks for the update, I found the changes in Git. (It makes sense not to rebuild the package just for a change like this.) However, I suppose other variants such as `mingw-w64-gcc` and `aarch64-linux-gnu-gcc` should be updated as well. Likely it makes no sense to create an individual ticket for each of them.

Reassigned to the maintainer of those pkgs